DUNIN7-M4 — INFRASTRUCTURE CHANGE REQUEST

CR-2026-189 — B-32: re-derive a stale Manifestation (v0.1)

Version. 0.1 · Date. 2026-08-08 · Author. Claude.ai (drafting) / Marvin Percival (approving). Target. /Users/dunin7/loomworks (+ engine only if Step 1 finds a gap — see §2). Baseline. Engine ad83960, surface 0dd7dd9. CC confirms both at Step 0. Companion to. inspection-briefs/loomworks-b32-findings-v0_1.md (Wave 0.2); CR-2026-177, which made this CR's premise true. Charter. Autonomous regime. Status. Ready for CC execution, with a read-first Step 1.

1. Summary

When Memory has moved past what a Manifestation reflects, there is no way to rebuild it. The engine's re-derive step exists. The surface never wired anything in front of it, because doing so requires asking the Operator to authorize a spend.

Why this is buildable now and was not before. Wave 0.2's investigation of this item found that preview_manifestation accepted a spend context and dropped it — the call was unmetered and the 402 handler unreachable. A consent screen in front of that would have asked permission for a spend that never happened. CR-2026-177 fixed it. The gate now fires, so consent is now a true question.

2. Step 1 — read before building

CC establishes and reports:

Does a spend-consent pattern exist anywhere in the surface? Wave 0.2 asked this; the answer is not in Claude.ai's hands. If one exists, name it and reuse it — do not build a second. If none exists, say so plainly rather than describing something adjacent as if it qualifies.
What the re-derive route requires and returns, including how cost is expressed before the spend and confirmed after.
How the surface knows a Manifestation is stale today. The staleness block already exists (CR-2026-172 fixed its wording). Confirm whether it already has what a re-derive control needs, or whether that state comes from somewhere else.
Whether the Operator's available credit is readable before the call. If the surface cannot say what a re-derive costs or whether it is affordable, the consent screen can only say "this will cost something" — which is worse than useful. Report this rather than working around it.

Halt if Step 1 finds re-deriving requires an engine change beyond wiring — that is a different CR.

3. Scope

The consent step. Before a re-derive runs, the Operator sees what it will cost and confirms. Not a generic "are you sure" — the point is the spend, and the spend should be named.

Operator authority. Re-deriving is an Operator act. Nothing re-derives automatically on staleness being detected — the system surfaces and signals; the Operator approves. Automatic re-derivation on a staleness signal is a category error and is explicitly not in scope.

Only-show-what-is-available. If a Manifestation is not stale, no re-derive control appears. If credit is insufficient, CC reports what it chose to show — this is a real design point and should be reported, not silently decided.

Failure. A re-derive that fails must not leave the Operator watching something that will never finish. B-37 established the pattern for this: the failure appears where the person was looking. Follow it.

4. Out of scope

Any change to what a re-derive costs, or to the metering itself. CR-2026-177 settled that; this CR asks permission for it.
Automatic re-derivation on any signal. See §3.
B-51's focus-loss finding. Separate item, separate CR.

5. Seed-mutability impact

B-69's standing instruction applies and this CR is likely to hit it. A Manifestation is Memory organized at a moment in time; the seed governs what Memory is and what organization means. If anything in the re-derive path reads the seed, caches it, or assumes it fixed, record the contact point under a seed-mutability impact heading in the completion record. Do not design for it, do not build around it.

Specifically worth checking: does re-deriving read the engagement's seed, and if the seed changed since the last derivation, would the re-derived Manifestation differ for that reason rather than because Memory moved?

6. Build steps

| Step | What | Mode | |---|---|---| | 0 | Pre-flight, both repos. | Auto | | 1 | Read per §2. Report all four. Halt if engine work is needed. | Auto, conditional halt | | 2 | Consent step + tests. | Auto | | 3 | Re-derive control, shown only when stale + tests. | Auto | | 4 | Failure path per §3 + test. | Auto | | 5 | Surface sweep (+ engine suite if touched); gates clean. | Auto | | A | Checkpoint. | Checkpoint | | 6 | Tag cr-2026-189-b32-rederive-manifestation. Push. | Auto |

7. Acceptance gate

A stale Manifestation can be re-derived, and only by an Operator act.
The cost is named before the spend, not after — or, if Step 1 finds cost is not readable, that limitation is reported rather than papered over.
No control appears when there is nothing to re-derive.
A failed re-derive is visible where the Operator was looking.
Seed-mutability contact points recorded per §5.
Suites green, both gates clean.

8. Kickoff prompt


Execute CR-2026-189 v0.1 at ~/Downloads/cr-2026-189-loomworks-b32-
rederive-manifestation-v0_1.md. Confirm the CR number against the
ledger first.

B-32: no way to rebuild a Manifestation when Memory has moved past it.
The engine step exists; the surface never wired consent in front of it.

This is buildable now specifically because CR-2026-177 landed. Before
that, the call was unmetered and the 402 unreachable — a consent screen
would have asked permission for a spend that never happened.

Step 1 reads four things and reports all of them, especially #4: if the
surface cannot say what a re-derive costs or whether it's affordable,
report that rather than working around it. A consent screen that says
"this will cost something" is worse than useful and I'd rather amend
the CR than have you build one.

HALT if re-deriving needs engine work beyond wiring.

§3's Operator-authority point is not negotiable: nothing re-derives
automatically on a staleness signal. The system surfaces and signals;
the Operator approves.

§5 — B-69's seed-mutability instruction applies and this CR is likely
to hit it. Check specifically whether re-deriving reads the engagement's
seed, and whether a changed seed would alter the result for reasons
unrelated to Memory moving. Record contact points; do not design for
them.

DUNIN7 — Done In Seven LLC — Miami, Florida CR-2026-189 — B-32 re-derive a stale Manifestation — v0.1 — 2026-08-08