Current execution index — 2026-09-26
The fixed model is addressless Wire.send(message) / Data.read(), full WireTree = DeixisNode<Wire> / DataTree = DeixisNode<Data>, and explicitly opaque AddressedWire carrier access. bitwire owns contracts and independent expectations; bitruntime implements them in Go/TypeScript. All source components use two-letter language directories.
Delivered and first consumer gate
v0.1.0 delivered the structural core; v0.2.0, from PR9, adds local pairs, transports, engine and dispatch. #1 remains open for independent released Go/TS conformance (bitwire PR52) and actual bitsystem3 #7 adoption. Source merge/release is not those downstream gates.
Bounded successor work
| Owner packet |
Depends on / closes with |
| #10: stdio/TCP/Unix streams |
bitwire #54 framing/closure contract and portable vectors |
| #11: scoped tunnels |
bitwire #53, #54, relevant #55 authority decisions; historical nightseam #721/#723 |
| #12: live references |
explicit profile/lifetime plus bitlink #1 bindings; historical nightseam #724 |
| #13: remaining lifecycle integration |
bitwire #20; exact local/physical/generated/live/tunnel rows |
| #14: public received-context/observation hooks |
accepted bitwire #55 design and version disposition |
| #15: full-tree/carrier composition |
bitwire #29 disposition of current and historical observations |
| #16: reusable auth integration |
public hooks/profile decisions; authority policy remains consumer/provider-owned |
No later module is an automatic prerequisite for bounded #1/#7. Implement only the contract-dependent portions after their decisions; independent development and candidate tests can run in parallel. Each packet requires released artifacts, independent evidence and its named consumer disposition before closure.
Consumer handoffs and release order
- bitsystem3 #7: first transport migration; #11: separate full space/WireTree mapping.
- bittree #53 and bitlink #1: declared/model bindings and access.
- repo-tool #17: streams and reusable auth integration.
- nightforge #3: runner live references, plus a separately bounded concur carrier lane.
- nighthall #1: generated session/reverse-call/tunnel migration.
- Generic service deixis-svc #1 has separate service acceptance and is not required for the direct bitsystem3 migration.
Historical nightseam #658 is resolved in successor v0.2.0; #722's queued-refusal fix is released, while root-overflow disposition belongs to the carrier contract. Preserve exact historical baselines. The six additional runtime-language ports from nightseam #702 are not committed successor scope; Go/TS are the current charter. A future scope decision and dedicated acceptance must precede any port claim.
This coordination issue closes when its committed child packets have released evidence and consumer dispositions. Optional future language/telemetry work must be explicitly scoped rather than silently added. Reciprocal coordinators: bitwire #47, bitsystem3 #8, nightseam #725, family index.
Historical issue record (preserved; current execution instructions are above)
Purpose
This epic coordinates bitruntime's share of moving the carrier stack out of nightseam, recorded in bitwire decisions 0007 to 0010.
bitwire specifies interaction contracts, the protocol bitwire/1, carrier contracts and independent conformance. bitruntime implements them in Go and TypeScript:
- operators, transports, carriers and the protocol engine;
- invocation lifecycle, dispatch and request/response helpers;
- live references and tunnels;
- optional telemetry and wire-authentication integration.
Adopted contract names (2026-09-26)
Wire.send(message) is addressless, symmetric with Data.read() -> Bytes. Full WireTree = DeixisNode<Wire> and DataTree = DeixisNode<Data> expose own values, complete byte-keyed children, partial selection, decomposition and recomposition. Operations are derived by selecting a node and invoking its own primitive.
The old opaque pathful sending API becomes an explicit AddressedWire bridge, not a tree with an invented enumeration guarantee. Historical bitwire v0.2.0 / nightseam v0.6.0 APIs keep their released meanings until consumer migration. Runtime implementation and public library releases must identify their actual supported contract versions.
This naming migration does not change bitwire/1 frames or establish that received-context redesign, negotiation, or protocol revision 2 has shipped. Track those capabilities with their own contract and conformance evidence.
Released
Issues in this repository
Recorded nightseam defects to fix rather than port
These are historical nightseam issues whose implementation owners now live in bitruntime:
Coordinating epics elsewhere
This epic closes when its sub-issues close with released implementation and adoption evidence.
Explicitly uncommitted historical design questions
nightseam #664's child-process host helper and #665's durable WireLog are preserved as future scope/design questions, not approved successor mechanisms or blanket migration blockers. Their A/B/C choices need a concrete consumer need and an ownership/compatibility decision before a new implementation packet. Existing stream transport work is #10 and does not silently choose a process manager or durable replay log.
Current execution index — 2026-09-26
The fixed model is addressless
Wire.send(message)/Data.read(), fullWireTree = DeixisNode<Wire>/DataTree = DeixisNode<Data>, and explicitly opaqueAddressedWirecarrier access. bitwire owns contracts and independent expectations; bitruntime implements them in Go/TypeScript. All source components use two-letter language directories.Delivered and first consumer gate
v0.1.0 delivered the structural core; v0.2.0, from PR9, adds local pairs, transports, engine and dispatch. #1 remains open for independent released Go/TS conformance (bitwire PR52) and actual bitsystem3 #7 adoption. Source merge/release is not those downstream gates.
Bounded successor work
No later module is an automatic prerequisite for bounded #1/#7. Implement only the contract-dependent portions after their decisions; independent development and candidate tests can run in parallel. Each packet requires released artifacts, independent evidence and its named consumer disposition before closure.
Consumer handoffs and release order
Historical nightseam #658 is resolved in successor v0.2.0; #722's queued-refusal fix is released, while root-overflow disposition belongs to the carrier contract. Preserve exact historical baselines. The six additional runtime-language ports from nightseam #702 are not committed successor scope; Go/TS are the current charter. A future scope decision and dedicated acceptance must precede any port claim.
This coordination issue closes when its committed child packets have released evidence and consumer dispositions. Optional future language/telemetry work must be explicitly scoped rather than silently added. Reciprocal coordinators: bitwire #47, bitsystem3 #8, nightseam #725, family index.
Historical issue record (preserved; current execution instructions are above)
Purpose
This epic coordinates bitruntime's share of moving the carrier stack out of nightseam, recorded in bitwire decisions 0007 to 0010.
bitwire specifies interaction contracts, the protocol
bitwire/1, carrier contracts and independent conformance. bitruntime implements them in Go and TypeScript:Adopted contract names (2026-09-26)
Wire.send(message)is addressless, symmetric withData.read() -> Bytes. FullWireTree = DeixisNode<Wire>andDataTree = DeixisNode<Data>expose own values, complete byte-keyed children, partial selection, decomposition and recomposition. Operations are derived by selecting a node and invoking its own primitive.The old opaque pathful sending API becomes an explicit
AddressedWirebridge, not a tree with an invented enumeration guarantee. Historical bitwire v0.2.0 / nightseam v0.6.0 APIs keep their released meanings until consumer migration. Runtime implementation and public library releases must identify their actual supported contract versions.This naming migration does not change
bitwire/1frames or establish that received-context redesign, negotiation, or protocol revision 2 has shipped. Track those capabilities with their own contract and conformance evidence.Released
(PR core: implement symmetric Data and Wire tree operations #8): the structural core over bitwire 0.3.0. Transports, the protocol
engine, dispatch and the lifecycle remain under runtime: deliver the path hand-written adapters use, so bitsystem3 can leave Nightseam. #1.
Issues in this repository
Recorded nightseam defects to fix rather than port
These are historical nightseam issues whose implementation owners now live in bitruntime:
live.releaseas an event, but the built-in declaration calls it a method.Coordinating epics elsewhere
Data/DataTree: bitstore #3This epic closes when its sub-issues close with released implementation and adoption evidence.
Explicitly uncommitted historical design questions
nightseam #664's child-process host helper and #665's durable WireLog are preserved as future scope/design questions, not approved successor mechanisms or blanket migration blockers. Their A/B/C choices need a concrete consumer need and an ownership/compatibility decision before a new implementation packet. Existing stream transport work is #10 and does not silently choose a process manager or durable replay log.