Skip to content

Capabilities

Documentation source v0.4.1. Published releases

11. Capability status (normative source for the docs matrix)

Each capability is Shipped (in cmd/loopexec with tests), In progress (on a feature branch), or Planned (specified here, not yet built). The docs site MUST render this distinction and MUST NOT present Planned capability as Shipped.

CapabilityStatus
CLI contract: --json, stable exit codes, deterministic outputShipped
init / status / check / step stubsShipped
run as a real iterating loop (section 4)Shipped
Computed halt reasons (section 5) replacing --halt-reasonShipped
Typed JSONL receipt + durable state (section 8)Shipped
probe-check confidence bound (O2)Shipped (core; adversarial perturbation + in-loop sequential monitor Planned)
doctor precondition gate (O3-O5, section 7)Shipped (determinism + isolation preflight + adequacy via mutation canary --mutate-cmd; hermeticity and the coverage-delta tier reported as planned)
Set-based progress + no-regression ratchet: oscillation / no-progress / regression halts (section 3.2)Shipped (legacy --failures-cmd; opt-in manifest snapshots and best-candidate restoration via --workflow)
explain-halt: raise-the-limit vs do-not-retry (feasibility)Shipped
Metric-integrity gate: guards dominate success (section 6)Shipped (fail-closed collected-set monotonicity and configured protected-file hashes; assertion-count / coverage-floor Planned)
doctor isolation preflight: credential-mount + exec-network fail-closed (section 7)Shipped
Receipt pinning: model-identity tuple + sampling + context manifest (sha256) + cost + check fingerprint (section 8)Shipped (legacy flags record metadata; workflow usage hooks support exact in-loop strict/observed/unmetered accounting)
replay: verify a receipt offline by re-running the check and matching the fingerprint (section 8)Shipped
attest: HMAC-sign a receipt and --verify it (section 8)Shipped
reexecute: live re-run of the recorded config N times, halt-reason distribution (section 8)Shipped
escalate / watch / ack + comprehension gate (section 9)Shipped (file/stdout channels, heartbeat + staleness detection, comprehension --comprehension-every; github/slack channels + kill-the-PID actuator Planned)
build-context: budgeted relevant-file slice with workdir-confined, symlink-safe file resolution (section 4)Shipped (stacktrace + last-diff + untracked relevance; import_closure / dep_graph tiers Planned)
Two-zone isolation orchestration (isolate): detached-clone sandbox + per-run minted/revoked credential (0600 env-file, never on the argv) + rendered/launched exec-zone (network:none) and agent-zone (egress-allowlist) (section 7)Shipped (orchestration; the container engine, the auditing egress proxy, and the provider key API are operator-provided hooks: --runtime, --egress-proxy, --mint-cmd/--revoke-cmd)
Shared command lifecycle: total/per-command deadlines, process-group cancellation, bounded outputShipped (macOS/Linux groups; other platforms direct child only)
Numeric score/patience and candidate-bound acceptance guardsShipped (opt-in workflow policy)
Shared scoped model-call budgetShipped (opt-in call-count gate across run IDs; independent of monetary metering)
Offline one-attempt Go creative adapter with signed synthetic review evidenceShipped (fixtures only; live engines/models are operator integrations)

This table is the contract between the binary and the site. When a capability moves status, update it here first; the binary tests and the docs matrix both reference this section.

Every row above now has a Shipped core. The remaining work is named, inline sub-parts (the operator-provided infra hooks, provider-specific metering wrappers, the deeper metric-integrity layers, the import_closure/dep_graph context tiers, github/slack escalation channels, the kill-the-PID watchdog actuator) — not whole capabilities.