Skip to content
PETROVA

2026-08-03 — Edit registry for mary-wiki

rank: decision outranks: []

Section titled “rank: decision outranks: []”

2026-08-03 — Edit registry for mary-wiki

Section titled “2026-08-03 — Edit registry for mary-wiki”

Date: 2026-08-03 Status: ratified Verb: petrova_act_registry_edit Slug: mary-wiki MR-compliance: MR-4, MR-7, MR-12

Rationale

Section titled “Rationale”

mary-wiki/mary now exists on GitHub (created 2026-08-03, private, default branch main, 22 corpus files) so the placeholder state admitted in PR #199 no longer describes reality. Set url and promote role placeholder -> scaffold. Repo name is ‘mary’, slug remains ‘mary-wiki’: slug is immutable post-admission (registry-edit.ts:209-214) and slug-differs-from-repo-name is the established pattern (slug eva-hq -> repo eva-hq/eva, registry.yaml:284-285). scaffold, not experimental: no discipline track record yet, mirroring the eva-hq and traceo-mcp-server admission pattern. profile stays strict and fleets_allowed stays [] per FR-009 — governance of the governors never earns auto-merge.

Change summary

Section titled “Change summary”

registry.yaml > repos[mary-wiki] after this verb:

- slug: mary-wiki
  url: https://github.com/mary-wiki/mary
  role: scaffold
  profile: strict
  fleets_allowed: []
  added: '2026-08-03'
  integrations_applicability:
    ares: not_applicable
    traceo: not_applicable
    crumb: not_applicable
    rocky: not_applicable
    eva: not_applicable
  notes: |
    MARY facility governance corpus (APEX-MAP rank 0, MARY-CONOPS,
    FLIGHT-RULES, DECK-REGISTER, ICD-001 envelope schema). Org mary-wiki
    created 2026-08-02; zero repos at 2026-08-03 discovery, so url is
    omitted and role=placeholder per the schema's own definition of that
    role. Matches the thrustr-io / downlink-hq / pwplz precedent
    (registry.yaml:705-740).


    profile=strict encodes FR-009 (human merge is the anti-echo damper):
    this repo carries FLIGHT-RULES itself, and governance of the governors
    never earns auto-merge. The requested "HUMAN-MERGE" is not an
    expressible profile value (enum: strict|standard|permissive) and
    profile is one repo-level scalar, not per-verb; strict +
    fleets_allowed:[] is its faithful encoding. See the admission ADR.


    fleets_allowed=[]: control-plane lockdown. Humans only, and only with
    explicit PETROVA_ALLOW_HUMAN_OVERRIDE=1.


    All five integrations not_applicable pending petrova_onboard.
    contract_sha is absent by design until the onboard PR merges and
    .petrova/contract.yaml exists to hash.


    Admission is deliberately corpus-fact-free: the MARY corpus carries 18
    open internal contradictions that are FLIGHT's to resolve, and none of
    them touch any field in this entry.

Envelope

Section titled “Envelope”
idempotency_key: 55b1de33875fb0b35e583456a0d56ee108764d2d791a1439c0ff89959969c0e1
schema_fingerprint: 527e83bf1a3b
actor: human:alex@devarno.com
triggered_by:
  kind: human_request
  ref: onboarding:mary-wiki
applied_at_iso: '2026-08-03T12:28:07.324Z'

Sign-off

Section titled “Sign-off”

Human merge required per MR-12 — this PR is opened with the awaiting-human-merge label and does not auto-merge.