mosaicstack/stack
21
0
Fork 1
Code Issues 337 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

WI-0: R4 Gate0 runtime-evidence probe — BUILD-ADMISSION GATE (do FIRST) #827

New Issue
Closed
opened 2026-07-17 23:54:31 +00:00 by jason.woltje · 2 comments
jason.woltje commented 2026-07-17 23:54:31 +00:00
Owner
Copy Link
Copy Source

R4 Gate0 is the BUILD-ADMISSION gate — this WI runs FIRST and NO feature WI (WI-1..WI-7) is admitted until every probe here produces POSITIVE RUNTIME EVIDENCE (not a design assertion). A FAILED Gate0 item RETURNS the design to planner review — it is NOT waived by the GO.

Structure like gitwatch: a runtime-evidence probe pack. Probes (BUILD-BRIEF §5 / SPEC-v5 §Precision + Gate0):

  1. Launcher exec/parent topology + supported-hook ancestry (D1); broker authenticates the launcher chain and REJECTS sibling-substitution.
  2. Pi lifecycle: last-position invariant (last-or-closed); per-tool nonce → tool-call-id map (D5).
  3. Same-PID runtime_generation bump on reload/resume/fork REVOKES the prior lease (D4).
  4. Broker socket authenticity posture (protected / distinct-principal); SO_PEERCRED returns the true (pid, starttime).
  5. Source-invalidation fail-closed (missing / oversize / hash-mismatch fragment → NO promotion).
  6. Claude additionalContext + Pi context inject ATOMICALLY (A-v5-1) — the T27 transport assumption; verify, or CLASS the gap as T-C.

Deliverable: a Gate0 evidence pack (captured runtime output per probe) + verdict per item. Any FAIL → escalate to planner, do NOT paper over.

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.

**R4 Gate0 is the BUILD-ADMISSION gate — this WI runs FIRST and NO feature WI (WI-1..WI-7) is admitted until every probe here produces POSITIVE RUNTIME EVIDENCE (not a design assertion). A FAILED Gate0 item RETURNS the design to planner review — it is NOT waived by the GO.** Structure like gitwatch: a runtime-evidence probe pack. Probes (BUILD-BRIEF §5 / SPEC-v5 §Precision + Gate0): 1. Launcher `exec`/parent topology + supported-hook ancestry (D1); broker authenticates the launcher chain and REJECTS sibling-substitution. 2. Pi lifecycle: last-position invariant (last-or-closed); per-tool nonce → tool-call-id map (D5). 3. Same-PID `runtime_generation` bump on reload/resume/fork REVOKES the prior lease (D4). 4. Broker socket authenticity posture (protected / distinct-principal); `SO_PEERCRED` returns the true `(pid, starttime)`. 5. Source-invalidation fail-closed (missing / oversize / hash-mismatch fragment → NO promotion). 6. Claude `additionalContext` + Pi `context` inject ATOMICALLY (A-v5-1) — the T27 transport assumption; verify, or CLASS the gap as T-C. **Deliverable:** a Gate0 evidence pack (captured runtime output per probe) + verdict per item. Any FAIL → escalate to planner, do NOT paper over. **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 changed title from __scope probe (delete me) to WI-0: R4 Gate0 runtime-evidence probe — BUILD-ADMISSION GATE (do FIRST) 2026-07-17 23:55:06 +00:00
jason.woltje added this to the Compaction-Refresh Mechanism (M1: Claude+Pi) milestone 2026-07-17 23:55:06 +00:00
jason.woltje commented 2026-07-19 19:50:23 +00:00
Author
Owner
Copy Link
Copy Source

Mos authority classification — probe-3 Gate0-mechanism = 3/3 FIRE PASS (attempt-3).

Reviewed harness (immutable): ca7b522e / sha256(p3_d4_focused_run.py)=92ff11bd35a72c3bda8f9722837cd9058a711f688cc75bf5e5df106645f81553. Fire ran the reviewed bytes (at-fire reviewed==run re-hash == 92ff11bd, fail-closed). External python3 -I -S -B runner, 3 isolation runs, PY_EXIT=0.

Result: all 3 runs machine_assertions=PASS; mechanism EXECUTED (same_pid_starttime + reload_revoke_verified + generations 1→12 monotonic — active gen/revoke, not passive); security invariants held (MUTATOR_UNVERIFIED / STALE_GENERATION); R1 clean (state_file_in_fixture_root, evidence in-fixture only). No assertion softened, no Case-C tell.

Pinned closure re-hashed fail-closed at fire: launcher e950e422 / helper 061625402f / broker 4db4fef1 (y/y/y). WI-3 head f400830738998db105107a2a4c69c7f2a2a6fd5d unmoved at fire + at merge.

3-of-3 harness review (byte-clear v12): terra §3 (0643ea3) + Mos co-attest + homelab (c742079), all binding immutable ca7b522e.

Immutable fire provenance (content-addressed log + full sha manifest) published for independent re-verification: mos-comms bus mos-comms-live → comms/20260719T194956Z__from-mos__184597625.md (embedded log sha256 428f20a7cec5fa448a6a2893481b7055fe74b76f4c6ab95a41051125360eb77c).

WI-3 (#830) merged: PR #842 squash → main e4d7d4502de99d3faaf1839990cf607a1830c194. — Mos (fire-classification authority, Gate 13/16)

**Mos authority classification — probe-3 Gate0-mechanism = 3/3 FIRE PASS (attempt-3).** Reviewed harness (immutable): `ca7b522e` / sha256(p3_d4_focused_run.py)=`92ff11bd35a72c3bda8f9722837cd9058a711f688cc75bf5e5df106645f81553`. Fire ran the reviewed bytes (at-fire reviewed==run re-hash == 92ff11bd, fail-closed). External `python3 -I -S -B` runner, 3 isolation runs, PY_EXIT=0. Result: all 3 runs `machine_assertions=PASS`; mechanism EXECUTED (same_pid_starttime + reload_revoke_verified + generations 1→12 monotonic — active gen/revoke, not passive); security invariants held (MUTATOR_UNVERIFIED / STALE_GENERATION); R1 clean (state_file_in_fixture_root, evidence in-fixture only). No assertion softened, no Case-C tell. Pinned closure re-hashed fail-closed at fire: launcher `e950e422` / helper `061625402f` / broker `4db4fef1` (y/y/y). WI-3 head `f400830738998db105107a2a4c69c7f2a2a6fd5d` unmoved at fire + at merge. 3-of-3 harness review (byte-clear v12): terra §3 (`0643ea3`) + Mos co-attest + homelab (`c742079`), all binding immutable `ca7b522e`. Immutable fire provenance (content-addressed log + full sha manifest) published for independent re-verification: mos-comms bus `mos-comms-live` → `comms/20260719T194956Z__from-mos__184597625.md` (embedded log sha256 `428f20a7cec5fa448a6a2893481b7055fe74b76f4c6ab95a41051125360eb77c`). WI-3 (#830) merged: PR #842 squash → main `e4d7d4502de99d3faaf1839990cf607a1830c194`. — Mos (fire-classification authority, Gate 13/16)
jason.woltje commented 2026-07-20 04:24:57 +00:00
Author
Owner
Copy Link
Copy Source

Gate0 administrative closure — Milestone-188 complete.

WI-0 Gate0 build-admission = GO-with-disclosed-T-C-M (recorded on board LIVE). Runtime-evidence verdict stands: probe-3/D4 revoke-mechanism = 3/3 FIRE PASS (reviewed harness ca7b522e, external python3 -I -S -B, generations 1→12 monotonic active-revoke, security invariants MUTATOR_UNVERIFIED/STALE_GENERATION held, no assertion softened, no Case-C tell). Immutable content-addressed provenance published to mos-comms bus.

All admitted feature WIs merged on that Gate0 basis:

  • WI-1 #828 MERGED · WI-2 #829/#838 completion-clean (push/ci #1919)
  • WI-3 #830 → PR #842 → main e4d7d4502de99d3faaf1839990cf607a1830c194
  • WI-4 #831 → PR #844 → main e522b22fa4492861b0fcd4a956a8795c54eb9bfe
  • WI-5 #832 MERGED (receipt-challenge protocol)
  • WI-6 #833 → PR #846 → merge_commit 2509eb762... (constrained recovery + refresh skill)
  • WI-7 #834 → PR #847 → merge_commit 0582a8912b133a86849bea99903ea7431db28595

The disclosed T-C residual (server-side branch-protection posture: main push-blocked / PR-only-merge MANDATORY vs. RECOMMENDED status-check + approval enforcement) is documented in WI-7 (docs/architecture/compaction-revocation.md) with the R1 receipt-boundary honesty amendment (docs/architecture/lease-broker-protocol.md). No probe returned a FAIL requiring planner-return.

Gate0 deliverable satisfied; all admitted work landed. Closing. — Mos (fire-classification authority, Gate 13/16)

**Gate0 administrative closure — Milestone-188 complete.** WI-0 Gate0 build-admission = **GO-with-disclosed-T-C-M** (recorded on board LIVE). Runtime-evidence verdict stands: probe-3/D4 revoke-mechanism = **3/3 FIRE PASS** (reviewed harness `ca7b522e`, external `python3 -I -S -B`, generations 1→12 monotonic active-revoke, security invariants MUTATOR_UNVERIFIED/STALE_GENERATION held, no assertion softened, no Case-C tell). Immutable content-addressed provenance published to mos-comms bus. All admitted feature WIs merged on that Gate0 basis: - WI-1 #828 MERGED · WI-2 #829/#838 completion-clean (push/ci #1919) - WI-3 #830 → PR #842 → main `e4d7d4502de99d3faaf1839990cf607a1830c194` - WI-4 #831 → PR #844 → main `e522b22fa4492861b0fcd4a956a8795c54eb9bfe` - WI-5 #832 MERGED (receipt-challenge protocol) - WI-6 #833 → PR #846 → merge_commit `2509eb762...` (constrained recovery + refresh skill) - WI-7 #834 → PR #847 → merge_commit `0582a8912b133a86849bea99903ea7431db28595` The **disclosed T-C residual** (server-side branch-protection posture: `main` push-blocked / PR-only-merge MANDATORY vs. RECOMMENDED status-check + approval enforcement) is documented in WI-7 (`docs/architecture/compaction-revocation.md`) with the R1 receipt-boundary honesty amendment (`docs/architecture/lease-broker-protocol.md`). No probe returned a FAIL requiring planner-return. Gate0 deliverable satisfied; all admitted work landed. Closing. — Mos (fire-classification authority, Gate 13/16)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone Compaction-Refresh Mechanism (M1: Claude+Pi)
Projects
Clear projects
No projects
Assignees
Clear assignees
code-be-01 (Mosaic fleet seat code-be-01) code-be-02 (Mosaic fleet seat code-be-02) code-dogfood-01 (Mosaic fleet seat code-dogfood-01) code-infra-01 (Mosaic fleet seat code-infra-01) fargo fred gate-merge-01 (Mosaic fleet seat gate-merge-01) happy jason.woltje (Jason Woltje) marcie merge-gate ops-01 (Mosaic fleet seat ops-01) ops-02 (Mosaic fleet seat ops-02) ops-03 (Mosaic fleet seat ops-03) ops-ci-01 (Mosaic fleet seat ops-ci-01) ops-deploy-01 (Mosaic fleet seat ops-deploy-01) orch-01 (Mosaic fleet seat orch-01) pepper resume rev-code-01 rev-code-02 rev-security-01 rev-security-02 rev-security-03 (Mosaic fleet seat rev-security-03) sanity scooby (Scooby) scrappy shaggy tiny topher (Mosaic fleet seat topher) velma veronica (Mosaic fleet seat veronica) vision woodpecker
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#827