CovenDocs

Canonical Coven runtime manual

From install to evidence.

Start with one recorded coding-agent session, then move outward into the CLI, daemon, harness, memory, and local API contracts that make the work durable.

Local

Sessions run on this machine, inside the project root you choose. Clients reach the daemon over same-user local IPC, and provider credentials stay with each harness.

Security posture

Durable

Every session becomes a record with its own event log. Archive and summon only change what you see; an explicit coven sacrifice is the one way to delete it.

Session records

Auditable

Each session keeps an ordered stream of output, input, status, and exit events, so you can replay what the harness did after it finishes.

Observability
  • 9 governed sections
  • Hourly production checks
  • Daily source-drift checks

First-session path

Four moves from readiness to recovery

The primary journey stays narrow. Advanced runtime and integration material only appears after the first useful loop is complete.

Contract map

Choose the surface you need

Every section declares its stability and links to the repository that owns the underlying facts.

Release evidence

The public manual ships with the product contract.

Generated API pages, browser routes, machine-readable exports, deployment commit attribution, and upstream source watches are verified independently of the hosting provider.

Was this page helpful?No

Last updated on