DUNIN7 · LOOMWORKS · RECORD
record.dunin7.com
Status Current
Path change-requests/cr-2026-212-loomworks-findings-visible-and-answerable-v0_2.md

DUNIN7-M4 — INFRASTRUCTURE CHANGE REQUEST

CR-2026-212 — The finding becomes visible and answerable: B-98 faces 1+3, one honest posture (v0.2 — the candidate-context path)

Version. 0.2 · Date. 2026-08-14 · Supersedes. v0.1 (kept), whose §1.A assumed a context that does not exist — rewritten per the Operator's ruling at the Step-1 halt (session-handoffs/cr-2026-212-step1-halt-v0_1). Everything else in v0.1 stands, wrinkle B with its precedent STRENGTHENED (one marker covers seed and findings lineages); face 3 builds as drafted. Target. BOTH repos. Baselines. Engine f011c80, surface a1deb86. Charter. Autonomous regime. Status. APPROVED IN EXECUTION — the v0.1 approval carries; build, test, halt at Checkpoint A.


0. Settled — the Operator's rulings (v0.1's §0.1–0.5 stand; these are added). Do not re-raise.

  1. The halt's actual finding, recorded above the fix: the scoping read the pipeline for what it carries and never asked whether it runs at all for the state in question. Probe the failure — and probe the precondition. The fourth read-produced wrong mechanism of this arc, and the first caught before build, at zero cost, by the discipline the first three taught. The arc's method paying for itself.
  1. Consequence 1 is CHOSEN, deliberately, in its own clause: candidates gain full seed context in conversation for the first time — arriving inside a findings CR, ruled rather than absorbed. Why it is right, plainly: a Companion that can discuss the project it is standing in is the behavior anyone would expect, and its absence was invisible only because nothing had asked. Sourced here so whoever finds the new behavior later can trace the ruling. Both alternatives were rejected knowingly: a findings-only context gives the Companion a gate without the thing it gates; dropping face 1 breaks the bundle for a reason unrelated to why it was ruled.
  1. What the halt makes true of the walk, recorded: E0128's "I don't have that context in front of me" was LITERALLY accurate — the entire conversation ran on persona and intent instruction alone; no seed, no title. The Companion was more honest than any of us credited, twice over.

1.A (rewritten) — the candidate-context path

For a candidate-state engagement, load_engagement_context stops raising and builds a context of its own: the seed resolved via the row's candidate_seed_id (latest version from the administrative log — not via the Engagement memory object, which does not exist until instantiate), assembled as the seed block plus an open-findings block (per finding: location_in_seed, the suggestion sentence) plus the capability-honest posture line (the Companion states findings when asked what blocks commit and points at the page's panel; it does not offer to close them — face 2 is unbuilt). converse.py's no-context catch stays for genuinely pre-seed candidates (door 3's seedless window). Active engagements are byte-identical in behavior.

The cache (wrinkle B, the ruled precedent, widened): the context stamps engagement_state and a candidate marker covering BOTH admin-log lineages — the seed's current version and the finding lineage's (count, max object_version) for the seed_id. On a cache hit for a candidate entry, re-query the marker (the B-77 shape: ask the seed's own log); mismatch → rebuild. Commit invalidates naturally (the working version bumps at instantiate). Halt clause unchanged if the shape fights back.

1.C–D, 2–7

As v0.1, unchanged — the panel (face 3), the amend→induct flow fact, the consequences, tests (face 1's now asserting the candidate path: seed text present, findings block verbatim, posture line, active untouched, cache invalidation on BOTH lineages), build steps, acceptance gate (the named criterion unchanged: the suggestion sentence on E0128's page), and the kickoff prompt with v0.2's mechanism. One test addition from the probes: location_in_seed is not always a field name (observed: "initial_contributors and initial_agents") — the panel's answer affordance maps only the text seed fields; non-mappable findings render without an inline answer, honestly.


DUNIN7 — Done In Seven LLC — Miami, Florida — CR-2026-212 — v0.2 — 2026-08-14 Probe the failure — and probe the precondition. The candidate gets a context; the context gets the gate; the gate gets a door.