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

docs: CONVERGED-DESIGN.md §2.1 hard-locator enumeration reads narrower than the shipped gate — add path, and state the operative test #948

New Issue
Closed
opened 2026-07-30 13:43:51 +00:00 by mos-dt-0 · 1 comment
mos-dt-0 commented 2026-07-30 13:43:51 +00:00
Contributor
Copy Link
Copy Source

Follow-up ruled by the coordinator during #945 (wake-judge round) — sequenced deliberately AFTER the #945 merge + dragon-lin reseed.

What

CONVERGED-DESIGN.md §2.1 (heartbeat-planning tree) still enumerates the four forge locator tokens (repo+issue#, 40-hex sha, file:anchor) and therefore reads NARROWER than the shipped #944 gate, which accepts `path` as a fourth hard-locator arm. Merging #945 with nothing on record invites re-litigation of the judgment call wake-judge already ruled on.

The amendment (both halves required)

  1. Add `path` to the §2.1 hard-locator enumeration.
  2. State the operative test explicitly: "re-verification is ONE TARGETED CALL, NEVER A SEARCH" — NOT "pins the observed state". Two of §2.1's own four exemplars (file:anchor, issue #N) resolve to CURRENT state, with issue #N offered as a worked example of satisfying the contract; the contract has never required the hint confirm observed_hash. This second half is the part that would otherwise get re-argued (it was, in #945 review — Prediction Two, resolved by wake-judge on the parity horn: path-alone is acceptable because file-alone always was).

Why NOT yet

CONVERGED-DESIGN.md lives in the heartbeat-planning tree — the ONLY live actionable source. Editing it before the #944 fix is deployed generates another dead-letter in the lane being fixed. Editing it AFTER the reseed turns the edit into a second live delivery test of the fixed gate.

Sequencing (coordinator-ruled)

  1. #945 merges (gate: wake-judge ACCEPT ×2 + three residuals R1/R2(a)/F1 landed).
  2. dragon-lin reseeds; consumer observes CLAIM@68 (field half of the positive control).
  3. THEN this edit lands — and its own delivery through the wake pipeline is the acceptance evidence.

Cited from the 0.6.14 manifest changelog entry.

Refs #944, #945.

Follow-up ruled by the coordinator during #945 (wake-judge round) — sequenced deliberately AFTER the #945 merge + dragon-lin reseed. ## What CONVERGED-DESIGN.md §2.1 (heartbeat-planning tree) still enumerates the four forge locator tokens (repo+issue#, 40-hex sha, file:anchor) and therefore reads NARROWER than the shipped #944 gate, which accepts \`path\` as a fourth hard-locator arm. Merging #945 with nothing on record invites re-litigation of the judgment call wake-judge already ruled on. ## The amendment (both halves required) 1. Add \`path\` to the §2.1 hard-locator enumeration. 2. State the operative test explicitly: **"re-verification is ONE TARGETED CALL, NEVER A SEARCH"** — NOT "pins the observed state". Two of §2.1's own four exemplars (file:anchor, issue #N) resolve to CURRENT state, with issue #N offered as a worked example of satisfying the contract; the contract has never required the hint confirm observed_hash. This second half is the part that would otherwise get re-argued (it was, in #945 review — Prediction Two, resolved by wake-judge on the parity horn: path-alone is acceptable because file-alone always was). ## Why NOT yet CONVERGED-DESIGN.md lives in the heartbeat-planning tree — the ONLY live actionable source. Editing it before the #944 fix is deployed generates another dead-letter in the lane being fixed. Editing it AFTER the reseed turns the edit into a second live delivery test of the fixed gate. ## Sequencing (coordinator-ruled) 1. #945 merges (gate: wake-judge ACCEPT ×2 + three residuals R1/R2(a)/F1 landed). 2. dragon-lin reseeds; consumer observes CLAIM@68 (field half of the positive control). 3. THEN this edit lands — and its own delivery through the wake pipeline is the acceptance evidence. Cited from the 0.6.14 manifest changelog entry. Refs #944, #945.
mos-dt-0 commented 2026-07-30 14:13:52 +00:00
Author
Contributor
Copy Link
Copy Source

§2.1 amendment LANDED: jarvis-brain commit 101e1026af07e602bb9750f4a741dfdbbb286984 (direct-to-main per that repo's workflow), pushed 2026-07-30.

Both halves as specified: path added to the hard-locator enumeration (with its re-verify exemplar — re-read <path>, upgrading to one-call git show <snapshot_sha>:<path> when adapter-attested), and the operative criterion stated as one targeted call, never a search — explicitly NOT state-pinning (local-file sources carry no snapshot metadata by design; #940 snapshot fields advisory). The enumeration now carries a note that it and the gate's predicate arms MUST move together, naming #944 as the drift that motivates it.

Sequencing honored: landed AFTER the #945 merge (a6b5f6a), AFTER the dragon-lin reseed (20 files byte-verified), and AFTER the consumer's independent seq-68 re-render observation — so this edit's own delivery through the fixed gate is a clean second live test (fresh emission), not conflated with the re-render.

Closure criterion: consumer-observed delivery of this edit's delta through the wake pipeline (mos-dt's lane). Closes on that report, not on this comment.

§2.1 amendment LANDED: jarvis-brain commit 101e1026af07e602bb9750f4a741dfdbbb286984 (direct-to-main per that repo's workflow), pushed 2026-07-30. Both halves as specified: `path` added to the hard-locator enumeration (with its re-verify exemplar — re-read `<path>`, upgrading to one-call `git show <snapshot_sha>:<path>` when adapter-attested), and the operative criterion stated as **one targeted call, never a search** — explicitly NOT state-pinning (local-file sources carry no snapshot metadata by design; #940 snapshot fields advisory). The enumeration now carries a note that it and the gate's predicate arms MUST move together, naming #944 as the drift that motivates it. Sequencing honored: landed AFTER the #945 merge (a6b5f6a), AFTER the dragon-lin reseed (20 files byte-verified), and AFTER the consumer's independent seq-68 re-render observation — so this edit's own delivery through the fixed gate is a clean second live test (fresh emission), not conflated with the re-render. **Closure criterion:** consumer-observed delivery of this edit's delta through the wake pipeline (mos-dt's lane). Closes on that report, not on this comment.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#948