Skip to content
Coven Threads Docs

Automation Authority Profile

Operation-specific automation authority, approvals, proposal-only downgrade, replay/TOCTOU, privacy, and portable vectors.

2 min read

The Automation Authority Profile answers one narrow question immediately before an automation operation: may this exact familiar operation act now?

Threads returns permit, requires_approval, degrade_to_proposal, or reject. It binds the answer to the principal, familiar embodiment, automation revision, occurrence/run/attempt/fence, action, capabilities/scopes, project/workspace/runtime, and policy/manifest snapshot. Final dispatch recomputes the canonical policy result from the policy snapshot pinned in its trusted immutable input. A valid Threads signature cannot make a semantically widened or forged decision authoritative.

The profile deliberately does not schedule or run anything. Coven owns durable scheduler state, final revalidation, consumption, launch, and effects.

Delivery: #35 ships profile version 1.0.0 as a portable reference bundle, separately from Rust package version 0.2.0. Its four automation outcomes are not additions to the Rust gate's three verdicts. Local CI exercises the bundle; it does not establish daemon or consumer adoption. See the delivery strategy for those separate obligations.

Final revalidation consumes the raw signed approval-event chain plus a Threads-signed, revision-bound consumption snapshot. A client-authored approved summary is never authority. Human approval requires the authorized principal's key; R4 protected-owner approval requires a protected-owner key. Recurring R2 approval remains narrowly reusable only through exact per-run signed consumption evidence and a bounded usage counter. Request, decision, and current runtime capability snapshots must match exactly. Evidence with missing or unknown sensitivity/retention metadata fails closed, and impossible UTC calendar timestamps are rejected rather than normalized. Principal, protected-owner, and auditor keys always bind an exact principal ID. Generic evidence.read scopes can name only the authenticated request principal; cross-principal reads use the dedicated signed auditor flow. Dedicated self-read tokens require a principal key, while cross-principal tokens require an auditor key. Threads-authority and protected-owner keys cannot substitute for evidence-access roles.

Why proposal-only matters

A familiar may still reason and prepare when it lacks authority to act. A proposal is cryptographically tied to the original action and target, visibly states that it was not executed, performs no protected effect, and requires a new adoption decision before execution.

Portable artifacts

The versioned schemas, validator, public conformance keyring, exact manifest, and 132 vectors are under profiles/automation-authority/v1/. The normative contract is specs/AUTOMATION-AUTHORITY-PROFILE-v1.md.

Run the dependency-free reference checks:

node --test profiles/automation-authority/v1/tests/*.test.mjs
node profiles/automation-authority/v1/run-vectors.mjs

The differential evidence guide describes pinned tools, seeded multifaults, ordered keyring comparisons, exact replay/output checks, retained failures, error-code reachability, and the required debug/release feature matrix.

Esc