Skip to content

2026-10-03 — Reconcile kahn-hq and rocky-hq contract_sha after operator contract rulings


2026-10-03 — Reconcile kahn-hq and rocky-hq contract_sha after operator contract rulings

Section titled “2026-10-03 — Reconcile kahn-hq and rocky-hq contract_sha after operator contract rulings”

Date: 2026-10-03 Status: ratified Verb: petrova_act_registry_edit Slug: kahn-hq, rocky-hq MR-compliance: MR-7, MR-12, MR-14

Both consumers changed .petrova/contract.yaml on 2026-10-03, by operator direction, from evidence gathered 2026-10-02:

slugrepochangelandedregistrylive blob
kahn-hqkahn-tools/kahntraceo mermaid_validated_at refreshed (run 37035811304); crumb review_by → 2027-01-01; rocky and eva not_applicable → pending (both original reasons no longer hold)kahn-tools/kahn#126 (bcee7fcd)942df4f43884394278303c7b
rocky-hqerid-tech/rockyares pending → not_applicable (never wired; ARES deprecated 2026-09-22; registry optional); traceo stays pending with a dated note; crumb review_by refreshederid-tech/rocky#137 (cd0c08f1)8273e815e91360063baedf9e

Both live values are the git-blob-sha1 (12 hex) of .petrova/contract.yaml on each default branch, the one contract hash family (2026-10-01-one-contract-hash-family.md).

Only the two contract_sha: lines in registry.yaml. No applicability or notes change: the registry already records kahn rocky: optional, eva: optional and rocky ares: optional, which these contracts now match.

rocky’s docs/decisions/2026-10-02-ares-not-applicable-rocky-hq.md is Proposed and awaits the operator’s own sign-off in that repo.

After merge, the State sweep should report contract_drift: false for kahn-hq and rocky-hq.

  • Human: flight@arno.host, 2026-10-03 — that both contract_sha values move to the live blobs above.