shared/ namespace

---

rank: shared outranks: []

shared/ — cross-project methodology

Methodology content that applies identically to every petrova-line repo. Lives here once, referenced by CLAUDE.md.tmpl and consumer CLAUDE.mds via <<INCLUDE: @shared/<file>.md>> placeholders.

What lives here

• meta-rules.md — pointer to the canonical META-RULES.md. The twelve MR-N invariants stay at their canonical path (core/templates/META-RULES.md) because seven other files reference that location; this file is a one-line redirect for future readers.
• documentation-hierarchy.md — the docs/<rank>/ taxonomy and rank semantics. Identical across all petrova-line repos.
• phase-discipline.md — phase-open / phase-close / verification- round mechanics. The “friction becomes next phase’s input, never a retrofit” rule and its corollaries.
• agent-fleet-methodology.md — narrative rules about how subagents are delegated to. Pairs with AGENTS.xml.tmpl (which is the schema; this is the grammar).
• north-star-methodology.md — how to write and maintain a north-star doc. The how, never the what — project intent never lives here.
• conventions.md — universal conventions: ISO dates, sibling files, PR-vs-direct-push boundaries, mandatory verification rounds.
• navigation-index.md — the “Where to look when stuck” cheat sheet.

What does NOT live here

• Project intent of any kind — that grounds in each repo’s docs/north-star/ and stays there (MR-12).
• Stack-specific commands — build, test, run lives in each consumer’s CLAUDE.md.
• Project invariants I-N — those are local to each repo’s spec.
• Architecture descriptions — each repo describes its own shape.

How consumers see this

Two viable mechanisms (the choice belongs to TASKSETs 5–6 when the petrova CLI is implemented):

1. Inline at bootstrap. 00-bootstrap.md reads shared/*.md and stitches the contents into the consumer’s CLAUDE.md at copy time. Consumer files are self-contained; updates require re-running bootstrap or a targeted refresh verb.
2. Link via submodule / managed dependency. Consumers reference @petrova/shared/<file>.md paths that resolve to a vendored copy of core/templates/shared/. Updates to petrova-hq propagate by bumping the submodule pointer.

For now, write content as if either mechanism may be chosen — keep each file standalone, no inter-file <<INCLUDE>> chains.

Discipline

If you find yourself adding project-specific content here, stop. The purpose of this directory is to be the durable answer to “the same files keep appearing in every repo.” Project content has a different home.