Adoption plan

One sprint: three mechanisms and a receipt schema

A one-sprint adoption plan: three mechanisms with owners and effort estimates, a receipt schema, a worked example, and a release-gate binding. It is for a team that has already decided to adopt. For an introduction, read the method or start from a situation.

ETHOTECHNICS PATHWAYS Engineer Policy Auditor Clinical

Mechanisms

Pick three mechanisms

Each has a named owner and an effort estimate of two days or less.

Kill switch

Stops runaway automation in seconds.

  • Owner: Ops / Reliability
  • Effort: 1 day
Open mechanism

Decision log with dissent

Records rationale and dissent, so governance cannot drift silently.

  • Owner: Product / Policy
  • Effort: 2 days
Open mechanism

In-product appeal path

Prevents contestability regressions and shortens recovery time.

  • Owner: Support / Trust
  • Effort: 2 days
Open mechanism

Receipt schema

Ship one canonical receipt payload

This payload is the minimum proof that a decision happened and can be contested.

{
  "schema_version": "1.0.0",
  "receipt_id": "RCP-2026-0842",
  "issued_at": "2026-04-11T18:12:09Z",
  "owner": { "name": "Risk Operations", "role": "System owner" },
  "action": { "class": "WRITE", "description": "Eligibility update", "reversible": true },
  "clocks": { "ack": { "hours": 2 }, "review": { "hours": 24 }, "remedy": { "hours": 72 } },
  "appeal_path": { "url": "/appeals/eligibility", "channel": "in-product form" }
}

Validate against the canonical receipt schema so tooling can parse your receipts automatically.

Sprint deliverables

Ship one receipt, one example, one binding

The receipt, example, and binding are the minimum. The object model makes the controls machine-readable.

Receipt schema

Implement the canonical receipt payload and validate it in CI.

Receipt schema

Worked example

Ship at least one end-to-end scenario with receipts, clocks, and remedies.

See example

Release gate binding

Copy the release gate checklist into your deployment template.

Open binding

Agent Safety Object Model

Publish the machine-readable governance profile for CI validation.

Open spec

Effort

Effort, owner, risk reduced

The three mechanisms as a table, for assigning the first sprint's work.

Mechanism Owner Effort Risk reduced
Kill switch Ops / Reliability 1 day Stops runaway automation in seconds.
Decision log with dissent Product / Policy 2 days Records rationale and dissent, so governance cannot drift silently.
In-product appeal path Support / Trust 2 days Prevents contestability regressions and shortens recovery time.

Next steps

Attach evidence + bindings

Evidence packs and binding vectors make the sprint's work auditable.

Referenced by

Where the fast path is enforced

The examples, bindings, and evidence packs that depend on these artifacts.

Used in examples

Required by bindings

Verified by evidence packs

Search IDs: STD-01 v1.0, STD-02 v1.2, STD-01.1.1, STD-02.2.1, MEC-01, MEC-05, MEC-06, VAL-01, VAL-02, VAL-03.