Skip to main content

Autonomous workflow

Covenant treats autonomous maintenance as an operating-layer surface. Work is represented as task records, transition events, validation evidence, and handoff summaries rather than private chat state.

Lifecycle

proposed -> triaged -> planned -> in_progress -> self_review -> validation -> ready -> integrated

Security-sensitive or broad changes can add cross_review or move through repair. A task enters blocked only when a human-only input is actually required.

Control surface

The workflow is driven by a machine-readable lifecycle definition, scoped task records with explicit gates and verification, an append-only transition log, and a durable seed queue that refills when no active task is ready. The concrete files and runner scripts live in engineering-loop tooling rather than the public scripts directory; the recursive engineering model in BUILT.md describes the contract that those tools implement.

Summary contract

Sprint and handoff summaries are derived from tracked task state and the transition log. They report scoped task counts, state counts, active work, blocked work, recently integrated tasks, and recent transition events: deterministic outputs that a fresh session can consume without private context.

Validation

  • Commit evidence is checked by provenance.mjs verify-all.
  • Landing documentation must build with pnpm --dir landing build.

Related