OwnFramework Loop v0.6.0 — Durable Supervisor Architecture
OwnFramework Loop v0.6.0
OwnFramework Loop v0.6.0 moves unattended engineering from session-scoped
polling to a durable execution supervisor while preserving a deterministic,
agent-neutral engineering core.
What changed
Durable unattended execution
OwnFramework Loop now has a durable supervisor capable of driving a bounded
engineering mission through BUILD, REVIEW, repair rounds, and PROGRAM
checkpoints without keeping an interactive agent session alive.
The supervisor owns only operational concerns such as process lifetime, queue
state, retry/backoff, quarantine, observed cost, and runtime ceilings.
Repository artifacts remain authoritative for engineering state, candidate
identity, review identity, repair lifecycle, and terminal verdicts.
Atomic dispatch
The deterministic core exposes one typed work-order boundary:
- BUILD
- REVIEW
- WAIT
- TERMINAL
The supervisor does not implement a second engineering state machine.
Human-originated specification, no execution ceremony
SPEC remains human-originated.
Once a legitimate bounded work packet exists, normal execution does not
require:
- a confirmation token;
- a mandatory approval command;
- manual PROGRAM initialization;
- approval between builder/reviewer passes;
- approval between PROGRAM checkpoints.
The first legitimate execution start creates the immutable execution binding.
Semantic builder and reviewer passes are mandatory
A deterministic build finalizer can no longer substitute for a semantic
builder.
A deterministic review finalizer can no longer manufacture APPROVED without a
semantic reviewer assessment.
Review remains tied to the exact candidate SHA.
Crash/restart recovery
Supervisor commissioning proves:
- worker PID/process ownership;
- no duplicate worker while a live orphan exists;
- same-pass replay after supervisor restart;
- no duplicate engineering-pass consumption;
- zero-model finalization of an already-completed semantic artifact;
- exact-once observed cost accounting.
Hermetic exact-SHA review
Python bytecode, pytest cache, temporary files, and XDG cache state are kept
outside exact-SHA builder/reviewer worktrees.
The dirty-worktree invariant remains strict: real unexpected tracked or
untracked mutation is still refused.
Operational limits
The supervisor supports bounded:
- infrastructure retries;
- exponential backoff;
- operational quarantine;
- model-cost ceilings;
- wall-clock ceilings;
- explicit operational resume.
Infrastructure failure does not fabricate semantic BLOCKED state.
Claude Code reference runner
Claude Code is the first live, commissioned semantic runner and remains the
reference adapter.
Existing interactive Claude UX remains useful:
/loop /of-loop:build <run-id>
/loop /of-loop:review <run-id>
/loop is no longer the canonical overnight execution clock.
Portable host model
The protocol remains host/agent-neutral.
Codex distribution and protocol compatibility continue to be tested, while
Codex should not be described as having the same live commissioning or
hardening maturity as the Claude reference runner unless separately proven.
Promotion stays outside Loop
APPROVED means eligible for operator promotion.
OwnFramework Loop does not autonomously:
- push;
- merge;
- deploy;
- publish;
- send messages;
- make payments;
- perform unrelated external actions.
Current executable packets require human-controlled promotion.
Validation
v0.6.0 was commissioned with:
- real Claude builder/reviewer execution;
- a real repair cycle;
- multi-checkpoint PROGRAM execution;
- supervisor kill/restart recovery;
- launchd supervision on macOS;
- hermetic exact-SHA reviewer validation;
- 32 canonical tests;
- Linux/macOS CI;
- Python 3.12/3.13 release gates;
- Claude adapter validation;
- Codex static adapter validation;
- adapter conformance;
- security scanning.
Maturity
OwnFramework Loop remains an early public release.
Protocol compatibility does not imply equal host hardening, authenticated
runtime maturity, or operating-system sandbox containment across adapters.