Skip to content
PETROVA

Neverland — a fleet integration tier above per-repo north stars

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

Context

Section titled “Context”

Each consumer repo carries its own docs/north-star/ (≤3 docs, terminal authority for that repo, MR-1). Those govern each system in isolation. Nothing in the control plane governs how the systems compose.

A cross-repo audit on 2026-07-07 (four parallel investigations across stratt-hq, so1-io, kahn-hq, rocky-hq, petrova-codes) mapped the ten core edges of the STRATT / SO1 / KAHN / ROCKY / PETROVA loop and found 3 LIVE, 2 PARTIAL, 5 MISSING. The pattern: the execution substrate is real (STRATT compiles chains to n8n; ROCKY→KAHN telemetry is production-grade and SHA-pinned; STRATT CI is on the Scope board; KAHN is federated), but the connective tissue is absent — two edges are built on both ends with no cable (STRATT→SO1 chain import; STRATT federation), the council pipeline is entirely unwired, and the control plane cannot read what it governs (STRATT, ROCKY queue, and the real SO1 automation are governed-but-not-federated, or mis-registered).

The trigger insight: a per-repo north star can be fully satisfied while the fleet remains four disconnected tabs. There was no doc that owned the seams. The 2026-06 n8n-key outage was the same failure class one layer down — an untracked cross-boundary dependency breaking silently.

Decision

Section titled “Decision”

Introduce neverland — a governance tier in petrova-codes/docs/neverland/ that owns the fleet’s interaction surface: the connector edges, the shared cross-repo contracts, and the implementation cycle that closes the gaps. It ranks above docs/integrations/ (which codifies one external system ↔ petrova) and above each repo’s docs/north-star/ (which governs one system alone) on the interaction surface, while deferring to each repo on internal design.

Neverland lives in petrova-codes because PETROVA is the only actor that already sees every repo (registry.yaml) and every cross-boundary read (Fleet MCP host). Governance of how systems connect belongs where governance of each system already sits.

Initial doc set: README.md (tier + fleet + loop + vocabulary), 01-connector-map.md (living status matrix with file:line evidence), 02-shared-contracts.md (ownership + versioning), 03-implementation-cycle.md (phases N0–N4, acceptance-gated).

Alternatives considered

Section titled “Alternatives considered”
  • A per-repo docs/integrations/ file in each consumer — rejected: no single repo can hold a map of edges it is only one end of; the map would fork and drift (the exact anti-pattern neverland forbids).
  • Extend docs/integrations/ in petrova with more <system>.md files — rejected as insufficient alone: those are per-system instances; the fleet needs a tier that says how all instances compose. Neverland names the need; integration docs remain the per-system codification.
  • A new rank: north-star doc in petrova — rejected: north star is capped at ≤3 and scoped to a single system’s intent; the fleet interaction layer is a distinct concern deserving its own rank.

Consequences

Section titled “Consequences”

For code:

  • No code change in this decision. Neverland is a documentation + governance surface. Code lands per 03-implementation-cycle.md phases.

For docs:

  • New directory docs/neverland/ with four docs (README + 01/02/03).
  • Future cross-repo contracts each add a docs/integrations/<system>.md instance referenced from the connector map.

For in-flight phases:

  • Supplies the input scope for the N0–N4 cycle. N0 (registry honesty for the SO1 automation product) and N1 (STRATT→SO1 chain-import bridge) are the first actionable phases.
  • Surfaces that rocky-hq Phase 3b journal work is already implemented while PETROVA’s consumption contract still marks ralph.queue unstable (E8) — a federation-trails-reality gap to reconcile.

For invariants:

  • No new MR invented (MR-9). Neverland records existing seams and future ones; a fleet-level MR earns its number only after a verification round proves it load-bearing. The ownership rule and “federation trails, never leads” are stated as contract discipline, candidates for MR promotion after N2/N4.

References

Section titled “References”
  • docs/neverland/01-connector-map.md — the ten-edge status matrix.
  • docs/neverland/02-shared-contracts.md — contract ownership inventory.
  • docs/neverland/03-implementation-cycle.md — phases N0–N4.
  • contracts/petrova.host.consumption.v0.yaml — current federation pins (kahn LIVE, ralph omitted, no stratt/so1).
  • registry.yaml:60 (stratt-hq governed, not federated), :494 (so1-io slug → veritas, not the Rover automation).
  • spec/verbs/wire_integration.schema.json — the admission mechanism for each new seam.
  • docs/integrations/README.md — the “open a decision doc first” rule this doc satisfies.

Sign-off

Section titled “Sign-off”
  • Subagent: neverland connector audit (4 parallel investigators, 2026-07-07 run)
  • Human: <<pending — Alex confirm>>