Skip to content
PETROVA

Register hermes slug into petrova-codes registry

Date: 2026-05-24 Status: open Supersedes: none Superseded-by: none — current

Context

Section titled “Context”

The Hermes system (devarno GitHub Actions runner estate + operator panel) completed PETROVA Phase 1 sub-phases 1a-1e on 2026-05-24, producing docs/north-star/intent.md, AGENTS.xml, MILESTONES.md, CLAUDE.md, and .petrova/contract.yaml in github.com/devarno-cloud/hermes. Phase 1f acceptance item #4 (per hermes/docs/decisions/2026-05-24-petrova-bootstrap.md) requires the slug hermes to appear in petrova-codes/registry.yaml so that downstream verbs (petrova validate, petrova doctor, petrova_act_registry_edit) can address it. The slug is not currently registered: petrova validate /home/devarno/code/workspace/devarno-cloud/hermes fails with REPO_NOT_IN_REGISTRY. CAIRNET emit kit cairnet-emit-v2 at lock_commit 9dbece4 was wired on 2026-05-24 (.petrova/contract.yaml integrations.cairnet_emission.evidence). The repo is hosted at github.com/devarno-cloud/hermes with default branch main.

Decision

Section titled “Decision”

Add a new entry under repos[] in petrova-codes/registry.yaml with: slug=hermes, github_owner=devarno-cloud, github_repo=hermes, default_branch=main, role=experimental (matching .petrova/contract.yaml), profile=strict, fleets_allowed=[devarno-internal]. Once merged, the next operator action is node cli/dist/index.js validate hermes to surface MR/convention findings, then node cli/dist/index.js doctor hermes --commit-state to write state/hermes.yaml. Registry edits are governed by direct PR (the petrova_act_registry_edit verb explicitly cannot add slugs per its SLUG_NOT_IN_REGISTRY constraint); this decision doc is the MR-7 paper trail authorising the follow-up registry.yaml PR.

Alternatives considered

Section titled “Alternatives considered”
  • Skip registration; treat hermes as a standalone PETROVA-bootstrapped repo without a registry entry — Without a registry entry, none of the substrate verbs (validate, doctor, sweep-state, dashboard) can address hermes, and the Phase 1f acceptance gate cannot close. Hermes already has .petrova/contract.yaml + AGENTS.xml + MILESTONES.md following the PETROVA grammar — opting out of the registry would amount to forking the substrate, not skipping ceremony.
  • Direct PR on petrova-codes/registry.yaml without filing this decision doc first — MR-7 (append-only decision ledger) requires governance-affecting changes to land with a paper trail. The registry is governance-affecting (it determines which repos the substrate addresses). A registry-only PR without a co-located decision doc would set the precedent that registry mutations bypass the decision ledger, which is exactly the discipline PETROVA exists to enforce.
  • Use petrova_act_registry_edit verb to add the slug — That verb’s SLUG_NOT_IN_REGISTRY constraint explicitly rejects adding new slugs — it can only edit fields under existing repos[].*. Slug additions are an intentionally hand-merged operation; this decision doc plus follow-up registry.yaml PR is the documented path.

Consequences

Section titled “Consequences”

(no consequences enumerated — explicit none)

Sign-off

Section titled “Sign-off”
  • Subagent: <>
  • Human: <<pending — countersign here to close>>