Conversation
…us (CLUS-54) CLUS-53 — proto/README.md named `devicenix/core` as message-kit's home. That is doubly wrong: DeviceNix was retired into BenixOS/SlashBuilder on 2026-08-22, and message-kit is its own repo at slash-builder/message-kit. Also states plainly that this repo is the canonical home of the schema as of 2026-08-22 (moved from quickring/quickring.me, whose main no longer has a proto/ directory), fixes the ADR-0002 path to slash-builder/fabric-kit, and adds a Naming section recording that the quickring.v1 package and the WebSocket subprotocol id are unchanged pending the coordinated QR-33 rename. CLUS-54 — docs/encryption.md's header claimed "NOTHING IN THIS DOCUMENT IS IMPLEMENTED ... no X25519 key, no AEAD, no HPKE, no ciphertext on the wire." Written 2026-08-16; overtaken by the QR-136 programme on 2026-08-20 and carried forward unchanged through the extraction to this repo. Corrected in three places that all asserted it: the status header, the §1.2 status table (E0/E1 rows), and §12 "What is NOT implemented" (rewritten; the obsolete 2026-08-16 list is preserved as a collapsed historical record). Deliberately not papered over: fabric-kit's current E0 path is live but not yet byte-conformant to §7. That is recorded in the header, in the §7 row, and in §12, with this document normative and the code the thing that moves. Tracked as QR-228/QR-229 and being fixed in parallel. Doc-only. No wire change, no schema change, no code touched. chore(agents): messaging-architect — CLUS-53/CLUS-54 doc staleness sweep
… (CLUS-54) §2.4's may-we-say-this table gated two sentences on "when E1 ships." E1 shipped 2026-08-20 (QR-136), so the table read as more restrictive than reality while §12 read as less. The gates are left as written — the gate, not the verdict, is the durable part — with a dated status note recording that the E1 gates are met, that they are met only for content actually published through the encrypting path (§11.2), that the bootstrap-gated rows are still gated because device0_seed_hex has not been deleted, and that whether a met gate is published is quickring-pm's call, not this document's. chore(agents): messaging-architect — CLUS-54 doc staleness sweep
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doc-only. No wire change, no schema change, no code touched.
CLUS-53 — canonical-schema pointers
proto/README.mdnameddevicenix/coreas message-kit's home. That is doubly wrong: DeviceNix was retired into BenixOS / SlashBuilder on 2026-08-22, and message-kit is its own repo atslash-builder/message-kit.Also in
proto/README.md:quickring/quickring.me(quickring.me@53bf891), whosemainno longer contains aproto/directory at all.slash-builder/fabric-kit, with a note that ADR-0002's own body predates the move (that ADR is amended in the companion fabric-kit PR).quickring.v1package and the WebSocket subprotocol id are deliberately unchanged pending the coordinated wire break under QR-33.CLUS-54 — encryption.md status
docs/encryption.md's header claimed "SPECIFIED. NOTHING IN THIS DOCUMENT IS IMPLEMENTED ... no X25519 key, no AEAD, no HPKE, and no ciphertext on the wire." Written 2026-08-16; overtaken by the QR-136 programme four days later (executed and countersigned 2026-08-20) and carried forward unchanged through the extraction into this repo, which flagged it in the README as known, unfixed staleness.Three places asserted it; all three corrected:
mode_baseDHKEM(X25519, HKDF-SHA256)/HKDF-SHA256/ChaCha20-Poly1305, XChaCha20-Poly1305 content encryption), with the doc-lag itself recorded rather than silently overwritten.Deliberately not papered over
fabric-kit's current E0 path is live but not yet byte-conformant to §7. That is stated in the header, in the §7 row, and in §12, with this document normative and the code the thing that moves. Tracked as QR-228 / QR-229, being fixed in parallel — no fabric-kit code is touched by this PR.README.mdis updated to retire its "known staleness" flag and to record thatmessage-kitis now repointed at this repo (pinned to935712a) whilefabric-kit/hub/gateway/courierare not.🤖 Generated with Claude Code