Skip to content

2026-05-10 — Govern smo1-io at the org level only; deregister 8 sub-repos

Date: 2026-05-10 Status: closed Supersedes: docs/decisions/2026-05-08-smo1-io-onboarding.md (partial — the meta-repo entry stands; the 8 sub-repo entries are revoked) Superseded-by: none — current

The 2026-05-08 onboarding sweep enrolled smo1-io plus eight sub-repos (smo1-io-purr-api, smo1-io-meow-web, smo1-io-whiskers-landing, smo1-io-zoomies-edge, smo1-io-catnip-packages, smo1-io-litter-box, smo1-io-terraform-infrastructure, smo1-io-service-template) as nine independent registry entries. Reviewing the resulting fleet view (/console) made the redundancy obvious: PETROVA’s diagnosis unit is the org / control-plane meta-repo, not every leaf repo underneath it. The eight sub-repo cards add noise without surfacing information the meta-repo doesn’t already carry, and they were created by an agent sweep without operator confirmation that per-repo governance was the right granularity.

Govern smo1-io at the meta-repo level only. Remove the eight sub-repo entries from registry.yaml. The meta-repo entry remains unchanged and continues to carry the org-level contract + profile. Sub-repo invariants (I-2 latency on zoomies-edge, I-4 scoring DTO on purr-api/catnip-packages, etc.) stay documented in the smo1-io meta-repo’s own decision history; PETROVA does not enforce them per-repo from this control plane.

  • Keep all 9 entries — preserves per-repo visibility but duplicates governance state PETROVA can’t act on (no per-repo fleets_allowed wiring, no per-repo verb dispatch). Rejected: redundant for the diagnosis surface we actually need.
  • Tag sub-repos under the meta with a parent: field — preserves data while collapsing the UI. Rejected for now: registry schema change is bigger than the problem; revisit if multi-org diagnosis later needs per-leaf signals.

For code:

  • 8 entries removed from registry.yaml.
  • No state/smo1-io-*.yaml files exist, so nothing to delete there.

For docs:

  • This doc supersedes the sub-repo portion of docs/decisions/2026-05-08-smo1-io-onboarding.md. The 2026-05-08 doc remains in place (MR-7: append-only) but is now partially superseded.

For in-flight phases:

  • None active for the deregistered sub-repos in this control plane.

For invariants:

  • No MR-N changes. MR-7 (append-only decisions) is honoured by superseding rather than editing the prior doc.
  • docs/decisions/2026-05-08-smo1-io-onboarding.md (original onboarding)
  • registry.yaml (smo1-io meta entry retained)
  • Subagent: Claude Code (chore/smo1-io-org-only branch)
  • Human: alex@devarno.com — 2026-05-10