Repository navigation
Conversation
… replay checker Loop 1 of the statechart-then-verify layer. The lifecycle Proposed -> Claimed -> Implementing -> Verifying -> DraftPR -> Integrated -> Deployed -> OwnerAccepted -> Merged (+ Blocked/Interrupted/Abandoned) with roles from docs/roles-v0.md and an owner_availability input. - bend/work_item_fsm: fsm.bend, LAWS.bend (L1-L7, 15 claims), PROOF.bend; hermes bend verify PASS (kernel recheck), 10/10 law-breaking mutants rejected - src/z0int/fsm: Python twin (parity with Bend on 400 seeded tapes), read-only replay checker over gh PRs, running services and delegation logs, Mermaid and Company OS overlay export - docs/fsm: diagram (mmd + svg), findings on real data, next loops
…read-only supervise CLI
Loop 2 of the statechart-then-verify layer. Dispatched -> Running (heartbeats)
-> {Completed | Interrupted | Stalled} -> Resumed | Abandoned | Integrated,
plus Overdue (interrupted past the limit: needs Kevin), a Lease (one owner
per worktree/branch, also the phone install lock) and the S25 as a Device.
- bend/worker_supervision_fsm: fsm.bend, LAWS.bend (W1-W6, 19 claims),
PROOF.bend; hermes bend verify PASS (receipt c1de0af0, kernel recheck),
17/17 law-breaking mutants rejected
- src/z0int/fsm/worker_supervision.py: Python twin, equal to Bend on 400
worker + 100 lease + 100 device seeded tapes (ws_parity.py)
- src/z0int/fsm/supervise.py: read-only replay over delegation logs, state.db
(delegate_task lists, tool calls, Child-left notices), processes.json, git
worktrees and fleet run logs; groot-vs-fleet heavy.lock wait stats;
needs-Kevin batch with resume/abandon/already-integrated recommendations;
dispatch check (--worktree/--heavy) for Hermes before new workers.
Heavy commands on groot outside fleet-build count as law-4 violations
unless GPU work or Bend/Lean.
- docs/fsm/worker-supervision.{md,mmd,svg}, skills/worker-supervision-fsm-verify
…port mode runs and records
# Conflicts: # pyproject.toml
kvnloo
added
the
integration
github-actions
Bot
added
area:docs
This branch has not been deployed
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
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.
Integration branch only. Normal dependency-ordered merges of #211, #213 and #212, including final synthetic containment and endpoint identity follow-ups. Head cd7ee75. One additive pyproject.toml dependency conflict retained both aodl-contract and PyYAML. Real 2473-label evidence remains stage none and routes to Jev. Synthetic-only tmp mechanism reaches canary and calls the exact z0-farm qwen3-0.6b-q8 endpoint. O11 rejects synthetic evidence outside /tmp and rejects model/build/path mismatch. Evidence: workspace/zer0/data/operations/policy-pipeline/SMOKE-20261024.md and smoke.json in the operations workspace. No test suites or code compiles ran on groot. This PR is a Draft integration branch, not production policy promotion.