You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d7f1a8e
Browse filesBrowse the repository at this point in the historyBrowse files
docs(codex): another process can retarget the home symlink, so adjacency was never the mechanism
Round 8. Three things, the first proven by probe rather than argued.
I had written that the fresh in-loop ambient read 'closes F2' and that
parameterizing the residue guard was the eventual real fix. Both wrong. The
adjacent read closes JavaScript task interleaving and nothing else — two
realpath calls are two filesystem observations, and a third party owns the
selector between them:
check saw: clean-A
<another process retargets current -> routed-B>
guard saw: routed-B
SAME SYNCHRONOUS STACK, DIFFERENT DIRECTORY: true
The lock would have held coordinator A while the guard cleared B. So passing
the canonical target into classifyNativeRoutedResidue is required for
correctness in this phase; the adjacent read is demoted to defense-in-depth
and says so.
Second, instance #17: I declared that every accept criterion carries a
mutation that turns it red, then wrote criteria whose mutation falsifies only
part of the claim. The N->C criterion passed if the call edge stayed while any
single seam escaped it. F1 passed if the refusal became a throw. F2 passed for
the very implementation the probe above defeats. Two criteria had no mutation
at all. The presence of a 'Red when' sentence was treated as proof it
falsified the whole criterion — the same move, one level up.
Third, the merge is now real everywhere rather than only where I looked:
000_plan's phase table, 005's OUT list, 040's CONSUME row (now NEW/IMPLEMENT),
and 030's own opening line that still called WP11 independently landable. The
merged wp11 shell no longer duplicates c5/c6/c7/c18, wp12 is in_progress, and
F4 is a separate commit inside wp12 rather than an independent merge with no
phase auditing it.
Copy file name to clipboardExpand all lines: devlog/_plan/260804_codex_write_substrate/000_plan.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,11 +43,11 @@ it rather than inventing their share.
43
43
| WP8b |`005_contract.md`| The shared surfaces: record schema + owner, `/api/sync` response contract, the single convergence entry point, generation counters, module names, and the config-snapshot admission result | — |
|~~WP11~~|`030_lock_protocol.md`|**merged into WP12** — the lock has exactly one consumer, and the `AdmissionSnapshot` producer plus the `inject.ts` split that its API needs both live there | —|
47
+
| WP12 |`040_ownership_convergence.md`+ `030_lock_protocol.md`| the async per-home lock and per-USER namespace **with its first production caller**, plus tri-state authority, admission order, absence restoration |WP8b, WP9, WP10|
48
48
| WP13 |`050_composed_acceptance.md`| one acceptance suite against real production entry points | all |
49
49
50
-
WP9 and WP10 remain independent of each other and both precede WP11: a lock
50
+
WP9 and WP10 remain independent of each other and both precede the lock: a lock
51
51
around an unsplittable gather-and-write, or around a ten-second blocking history
52
52
call, is the failure the last unit already proved. WP12 stays last of the four
53
53
because its admission must run before the lock module creates anything.
Copy file name to clipboardExpand all lines: devlog/_plan/260804_codex_write_substrate/040_ownership_convergence.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ IN:
57
57
|`src/codex/convergence-types.ts`| IMPORT ONLY | Consume `AdmissionSnapshot`, `CodexObservedState`, `ConvergeOutcome`, `CodexProvenanceLedger`, and section types; no WP12 union. |
58
58
|`src/codex/integration-record.ts`| USE/MODIFY THROUGH OWNER API | Read/update provenance and extension keys through the contract owner; no transition pair, history state/schedule, path/schema/parser, or parallel merge here. |
59
59
|`src/codex/transition-state.ts`| CONSUME | Use `readCodexTransitionState`, `beginCodexTransition`, and `updateCodexHistoryTransition` for the canonical-CODEX_HOME pair and history state/schedule. |
60
-
|`src/codex/codex-write-lock.ts`|CONSUME | Correct WP11 module name; no lock redesign. |
60
+
|`src/codex/codex-write-lock.ts`|**NEW / IMPLEMENT**| This phase CREATES the module; `030_lock_protocol.md` is its design specification. It was WP11's until round 7 merged the phases. |
0 commit comments