Skip to content
PETROVA

Register the SO1 Rover automation product (so1-console)

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

Context

Section titled “Context”

The neverland connector audit (docs/neverland/01-connector-map.md, edge E10) found that the registry’s so1-io slug points at github.com/so1-io/veritas (the prompt repo), not at the SO1 Rover automation product — the Next.js control plane (rover.so1.io), the BFF (Hono/Bun), and the n8n orchestration (hab.so1.io) that actually execute the fleet’s real-world work. The hands of the loop were invisible to the control plane: PETROVA could neither audit nor govern the product that runs FORGE, TOMMY, Scribe, ZOID, and now the STRATT→SO1 chain-import bridge (E1). Neverland phase N0 requires registry honesty before any further wiring, so that everything built in later phases is audited from birth.

Decision

Section titled “Decision”

Add a new consumer slug so1-console → github.com/so1-io/so1-console, role: experimental, profile: standard, fleets_allowed: [], all integrations not_applicable for now, contract_committers: [humans]. No contract_sha yet — this is a registry-entry-first onboarding (per docs/decisions/2026-05-13-petrova-onboarding-flow-v2.md); the sha lands after petrova_onboard generates the target’s .petrova/contract.yaml. Leave the existing so1-io→veritas slug untouched.

Alternatives considered

Section titled “Alternatives considered”
  • Repoint the existing so1-io slug at so1-console — rejected: the so1-io slug legitimately governs the veritas prompt repo; repointing would lose that governance and conflate two distinct repos.
  • Set role: production — rejected for now: the product is deployed, but from a governance-maturity view it carries no .petrova contract, no CODEOWNERS on governed paths, and no fleet enablement. experimental is the honest state until onboard completes.
  • Enable fleets_allowed — rejected: no agent-fleet automation until the contract + CODEOWNERS exist. Empty by design.

Consequences

Section titled “Consequences”

For code:

  • None. Registry-only change.

For docs:

  • registry.yaml: new so1-console entry; updated → 2026-07-07.
  • Unblocks flipping neverland E10 from MISSING once onboard completes.

For in-flight phases:

  • Completes neverland N0. Next: petrova_onboard so1-console to generate .petrova/contract.yaml + populate contract_sha (a follow-up), then N2 (federate ROCKY) and N3 (council pipeline).

For invariants:

  • None. No MR added (MR-9).

References

Section titled “References”
  • docs/neverland/01-connector-map.md — E10 (governance gap).
  • docs/neverland/03-implementation-cycle.md — phase N0.
  • docs/decisions/2026-05-13-petrova-onboarding-flow-v2.md — registry entry may precede contract_sha.
  • docs/decisions/2026-05-24-register-hermes-slug.md — prior slug registration precedent.

Sign-off

Section titled “Sign-off”
  • Subagent: neverland N0 (registry honesty), 2026-07-07 run
  • Human: <<pending — Alex confirm>>