← Ledger

0010 — adopt eva.consumption.v1 for rocky-hq

Date: 2026-05-08 Status: ratified Supersedes: none — first eva consumption declaration for this slug Superseded-by: none — current

Context

eva-hq ratified the eva.consumption.v1 contract on 2026-05-08 (eva-hq:docs/decisions/2026-05-08-eva-consumption-contract.md, schema at eva-hq:contracts/consumption.v1.json). The contract publishes three independently-gated EVA surfaces — events, control, prompts — and the consumption envelope every consumer slug must populate in .petrova/contract.yaml#integrations.eva to be wired.

rocky-hq's registry entry in petrova-hq:registry.yaml was authored 2026-05-06 with integrations_applicability.eva: not_applicable and a review_by 2026-08-06 clause, pending eva-hq surface publication. That precondition is now satisfied. Two further signals point at adoption today rather than at the August review:

  1. 8646bf3 feat(contract): declare eva.consumption.v1, status pending already authored the per-surface block in .petrova/contract.yaml#integrations.eva with all three surfaces in state: pending. The declaration is live; the registry must catch up or the petrova doctor sweep will reject any subsequent flip (per petrova-hq:core/prompts/10-eva-wire.md Phase 0).
  2. 2026-05-08-agentic-emission-v1.md (ratified 2026-05-08) shipped the producer contract for CAIRNET stones with eva-hq listed as a first-class producer. Wiring the consumption side closes the producer↔consumer loop on the same day.

The precedent is petrova-hq:135cdae (2026-05-08) which performed the identical flip for stratt-hq against the same contract.

Decision

Authorise the registry flip in petrova-hq:registry.yaml for rocky-hq:

Per-surface state in rocky-hq:.petrova/contract.yaml#integrations.eva remains as already declared at 8646bf3:

Surface State Rationale
events pending rocky-hq has no .github/workflows/ yet; once CI lands, eva-emit will be wired per 10-eva-wire Taskset 3.
control pending A control client is not yet authored; will be added via 10-eva-wire Taskset 4 when a use-case lands.
prompts pending eva-prompts.lock.json not yet authored; will land via 10-eva-wire Taskset 5 once a prompt ID is referenced.

The actual surface-by-surface wiring is not in scope for this ADR. This ADR only authorises the registry flip and the corresponding integrations_applicability change. Surface wiring is gated through petrova-hq:core/prompts/10-eva-wire.md and lands per-surface as each one becomes load-bearing.

Consequences

Rollback

Revert the petrova-hq registry edit (single-file diff on registry.yaml); the .petrova/contract.yaml block can stay as authored — a pending block under not_applicable applicability is benign (it carries no evidence and triggers no probe action).