docs(design): worker-lease survey + draft laws (coupling-core Phase E1)#465
Merged
Conversation
…ispositions (coupling-core Phase B) B3 (partial): Monitor.StopRun previously killed the session via the LOCAL multiplexer and appended a canceled status client-side — both wrong for worker-hosted runs (the session lives on another host) and a violation of the daemon-as-SSOT boundary. It now calls the daemon StopRun verb, which owns the host-aware session kill (worker lease) and the user-sourced canceled append. One frozen client writer removed (whitelist 46 -> 45). B2: every frozen status writer now has a recorded disposition in docs/design/run-state-machine.md §6 — integrate into step() (W2-W8) or quarantine as a law boundary (W9 projections, W10 external append with orch repair as its sanctioned client). The B3 ResolveRun consolidation is specified as an equation for a follow-up issue. Also records two open-law decisions in §7: D-C1 (restart transparency via fold-derivable fields + ephemeral-by-law counters, L7 — no new persistence mechanism) and D-C3 (never-alive verdict asymmetry resolved: both planes conclude unknown after grace, L3'). Verified: go build/vet, semgrep write-surface scan 0 findings. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Mirror of run-state-machine.md for the second coupling core: enumerates the lease write surface (LW1-LW5), ownership/lifecycle across master and worker restarts, heartbeat semantics (incl. 7bfbcf8's dedicated-goroutine heartbeats and fail-fast lease waits), the coupling to the run state machine (leases reach step() only as observations - to be preserved), the memory-only store-of-record rationale, tripwire observations (stored Active flag mirrors a derivable value; copy-vs-pointer manual sync; no single-holder-per-run invariant), and five DRAFT law candidates (LL1-LL5) for E2 verification. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #464. Phase E1 of the coupling-core roadmap: the survey document for the worker-lease core (
docs/design/worker-lease.md), structured as a mirror ofrun-state-machine.md— write surface LW1–LW5, ownership/lifecycle, heartbeat semantics, run-state-machine coupling (leases reachstep()only as observations), store-of-record rationale, tripwire observations, and DRAFT laws LL1–LL5 for E2.🤖 Generated with Claude Code