← Ledger

title: Phase 7a close — agent-registration.v1 contract published date: 2026-06-29 status: Accepted phase: 7a predecessor: docs/decisions/2026-06-29-agentic-layer-projection.md spec: docs/specs/2026-06-29-agent-registration-v1.md

Phase 7a close

Shipped

Carry-forwards

1. Phase 7 admitted as the home of the agentic-layer cross-cut

The Phase 7 row in MILESTONES.md was previously titled "Polar.sh entitlements" with state not-started. The predecessor decision (docs/decisions/2026-06-29-agentic-layer-projection.md) folded the agentic-layer cross-cut into Phase 7 rather than inventing Phase 8. This close-out promotes Phase 7 to open and retitles it "Agentic layer + Polar.sh" because the agentic layer and Polar entitlement enforcement now share a single phase: the registration carries rate.tier_floor + rate.seats_required, which become the Polar check input at invocation time. The Polar wiring remains queued under 7c.

2. COUNCIL personas register as agents — precedent locked

The spec resolved the open question from the predecessor decision: COUNCIL personas DO register, with scope: "council", owner.subsystem: "SS-04", capabilities: ["council.respond"], approval.required: false. This sets the project-wide precedent for what counts as an agent: anything that produces work an operator might want to audit, gate, or rate-limit. Static fixtures qualify; dispatched workers qualify; ephemeral one-shots do not. Phase 7b PRs against COUNCIL must emit agent.registered events at persona-creation time and agent.invoked/agent.completed pairs around each response.

3. Closed scope enum — no scope: other

AgentScope is the closed enum council|sniffer|stratt|ralph|relay|driver. Adding a value is a v2 change, never an additive v1 extension. This is the structural enforcement of drift-watch #1 from docs/north-star/intent.md (Rocky is not a generic agent ledger): every agent in the projection must trace back to an existing rocky-hq subsystem. New subsystems can earn a scope entry by clearing the SS-NN bar first.

4. Build-pipeline generalisations are reusable for future subpaths

The quicktype codegen path is now ready to accept additional subpaths without script edits beyond extending GO_SUBPATHS. The fixpoint dedupeStructs catches the duplication pattern that emerges when a top-level schema name matches a parent field name (the Registration / AgentRegistration collision in the agent set); the prior <Name>Class regex only caught quicktype's class-suffix pattern. Future subpaths that introduce similar shapes inherit the fix. hoistImports is similarly defensive against quicktype's occasional out-of-order import emission. Both helpers are reused by go/hearth regen — one cosmetic side effect: go/hearth/types.go flips its import "time" line from single-line to block form. Predictable from the new pipeline; future hearth schema bumps will continue to land in block form.

5. Forward-only projection invariant intact

Per the predecessor decision §consequences, the agentic-layer projection is forward-only — no back-fill of pre-7b agents. Phase 7a only ships the contract; existing COUNCIL/SNIFFER/STRATT/RALPH/RELAY entries do not retroactively appear in the hatch view. The contract is in place for Phase 7b producer wiring; until that ships per subsystem, hatch.devarno.cloud/agents remains empty as expected.

6. Dual-tag convention preserved

v0.3.0 (npm publish driver) and go/v0.3.0 (Go module proxy resolver) were cut from the same merge commit per the convention established in Phase 5b §1. Future contracts bumps must continue to push both tags together; without the go/v* prefix tag, hearth's go get github.com/rocky-hq/contracts/go@<tag> fails with unknown revision.

Phase 7a acceptance verified at merge

Out of scope (Phase 7b / 7c)

Sources