WI-7: T-C server-side branch-protection line + R1 honesty doc amendment #834

Closed
opened 2026-07-17 23:55:09 +00:00 by jason.woltje · 1 comment
Owner

Deliverable 7 (BUILD-BRIEF §3.7). The T-C server-side line = branch protection is the irreducible guarantee; the client gate is window-narrowing ONLY. If this is ops-config rather than code, DOCUMENT the required posture explicitly (push/merge to main protected regardless of client-gate state).

R1 doc amendment: state honestly that the receipt detects ABSENT/PREFIX-TRUNCATED terminal token, but a MIDDLE-DROP preserving the tail is a T-C contract violation (server-side covers, receipt does not). No over-claim. Fold as a doc amendment.

Functional/doc surface — may take GPT review (NOT a peercred/gate/receipt security surface).

Authority (build AGAINST these, do not re-derive): BUILD-BRIEF 89fdbc27, SPEC-v5 a6d07ade, RATIFICATION bac58319, sol red-team 3da326a4. Coder MUST re-verify sha256 before build. Target: framework-native packages/mosaic/ in mosaicstack/stack (NOT jarvis-brain, NOT ~/.config/mosaic/ directly). M1 = Claude + Pi only.

Review discipline: red-first TDD; author≠reviewer; no self-merge; exact-head RoR (reviewed-SHA=merged-SHA); closes #<this>; full 40-char head; never edit tests to pass / never force-merge red / never --no-verify. Mos merges after review + green suite + (for security surfaces) Opus-SECREV.

Deliverable 7 (BUILD-BRIEF §3.7). The **T-C server-side line = branch protection** is the irreducible guarantee; the client gate is window-narrowing ONLY. If this is ops-config rather than code, DOCUMENT the required posture explicitly (push/merge to `main` protected regardless of client-gate state). **R1 doc amendment:** state honestly that the receipt detects ABSENT/PREFIX-TRUNCATED terminal token, but a MIDDLE-DROP preserving the tail is a T-C contract violation (server-side covers, receipt does not). No over-claim. Fold as a doc amendment. Functional/doc surface — may take GPT review (NOT a peercred/gate/receipt security surface). **Authority (build AGAINST these, do not re-derive):** BUILD-BRIEF `89fdbc27`, SPEC-v5 `a6d07ade`, RATIFICATION `bac58319`, sol red-team `3da326a4`. Coder MUST re-verify sha256 before build. Target: framework-native `packages/mosaic/` in `mosaicstack/stack` (NOT jarvis-brain, NOT `~/.config/mosaic/` directly). M1 = Claude + Pi only. **Review discipline:** red-first TDD; author≠reviewer; no self-merge; exact-head RoR (reviewed-SHA=merged-SHA); `closes #<this>`; full 40-char head; never edit tests to pass / never force-merge red / never `--no-verify`. **Mos merges** after review + green suite + (for security surfaces) Opus-SECREV.
jason.woltje added this to the Compaction-Refresh Mechanism (M1: Claude+Pi) milestone 2026-07-17 23:55:09 +00:00
Author
Owner

Mos tripwire (ratification): GPT-OK holds ONLY while this WI stays DOCUMENTATION of the required branch-protection POSTURE + R1 honesty doc amendment (ops-config/prose). IF it grows any ENFORCEMENT CODE (a gate/hook/policy that server-side blocks a mutation), it FLIPS to a security surface = Opus-SECREV, no GPT sub. Scope-check at build; report which it turned out to be.

**Mos tripwire (ratification):** GPT-OK holds ONLY while this WI stays DOCUMENTATION of the required branch-protection POSTURE + R1 honesty doc amendment (ops-config/prose). IF it grows any ENFORCEMENT CODE (a gate/hook/policy that server-side blocks a mutation), it FLIPS to a security surface = Opus-SECREV, no GPT sub. Scope-check at build; report which it turned out to be.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#834