Skip to content

docs: crap RFC 0002 — CRAP attach protocol (draft) #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
friedenberg wants to merge 8 commits into
base: master
Choose a base branch
from
Open

docs: crap RFC 0002 — CRAP attach protocol (draft) #30

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
fbf0ed7
docs: crap RFC 0002 — CRAP attach protocol (draft)
claude Jun 11, 2026
34ae17e
docs: RFC 0002 — crap/garbage partition, data-consumption withdraw
claude Jun 11, 2026
fa1f543
chore: drop stray smoke-test binaries from the tree
claude Jun 11, 2026
a8fcb17
docs: rewrite RFC 0002 around the client/birthed-server model
claude Jun 12, 2026
2827eee
docs: RFC 0002 — connect-before-spawn MUST, determinism analysis
claude Jun 12, 2026
477aa5c
docs: RFC 0002 — scoped attachment (tree is the unit)
claude Jun 12, 2026
f62ab77
docs: RFC 0002 — terminal servers, leader election by atomic bind
claude Jun 12, 2026
c79ece2
docs: RFC 0002 — prototype implemented in just-us
claude Jun 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/ndjson-crap-schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,20 @@ normative spec (records, driver mapping, and the producer reporter API).
| ------- | ----------------------------------------- |
| `crap` | optional stream header; MUST be first when present |

### Attachment (crap RFC 0002, draft)

The CRAP attach protocol
([`docs/rfcs/0002-attach-protocol.md`](rfcs/0002-attach-protocol.md))
lets a harness advertise — via a single `CRAP=2` environment variable —
that it consumes this format. Attached nodes are clients of a sink
server (a unix socket birthed by the tree's root) that grants each
connection a disjoint node-id base and splices record lines into one
merged stream, so a process tree nests via the existing
`tp`/`parent` lineage. It amends this schema additively:
result-family records gain an OPTIONAL `parent` for lineage under an
execution node, and node ids may start from a granted base (this
schema requires only stream-uniqueness).

## Record schemas

### `crap` (header)
Expand Down
Loading
Loading