2.3 KiB
Local immutable launch and remote mapping
Claude1794906657 removes the remote-upload prerequisite for the unchanged contracts E1b de4196e1, B14 d544b6cc and B15 998bcabe. The original 18d1cb raw publication and its shared writer lock remain untouched. The old remote-only waiter604069 was retired with no launched science or children. One replacement606413 launched E1b606462, then B15606787, then B14606883 after local commits, hash/source/duplicate/budget checks and B15 free-space check. Each root records actual workers; no old queue was restarted.
A separate serialized local Git evidence store at /tmp/meltmind-phase2-local-fixed-20261117 allows the original feature/model/prediction barriers to proceed without the network-held writer lock. phase2_local_coordinator.py explicitly replaces only its coordinator module's imported freeze reference. Original scientific files, three contract hashes, worker entry points, resource guards and phase2_fixed_io.verify are unchanged. The local backend preserves proof/auth format, verifies each committed blob, records its local Git repository/commit and adds the separately pinned engineering sources to every proof. Children still run the original pinned entry and original verifier. This is an explicit storage-backend adaptation, not an assertion that identical source hashes alone prove identical orchestration.
Engineering contract6792dc949b03a7e57be1ef1c6e3ca5970d654a003bdcf9e4cbef857c2eff9273 records the change and launch order. Two CPU synthetic checks passed: original verifier accepts local proofs and rejects a changed source; subsequent barriers preserve the earlier immutable commit. No synthetic scientific work or metric recomputation was added. Local barrier Git child CPU remains included in the existing coordinator accounting.
Local launch commits: E1b29673c81ec06da5abfd8d4782c096b13b6ee6da4; B154b07cb6e9231e479b780e12d93f0b84ec1114319; B14ee980b0829b0c1a0d039aaf9148790979ac55629. Three existing remote publishers remain queued. The sole replacement now monitors contract identity and writes local-remote-mapping.json after each remote publication. A changed contract stops its root and records a mismatch; it is never silently adopted as the same contract. Remote completion remains pending until those receipts exist. No duplicate upload or network change.