2026-05-16 — Playbook prompts resolve siblings via Fleet MCP, not filesystem paths

date: 2026-05-16 status: accepted outranks: [] supersedes: docs/decisions/2026-05-14-meta-rules-eva-hq-migration.md (extends, does not repeal)

2026-05-16 — Playbook prompts resolve siblings via Fleet MCP, not filesystem paths

Context

The 2026-05-14 locked strategy moved consumers to a boot-kit-only model: .petrova/playbook/ + Fleet MCP (petrova.prompts.list/get) for everything else. The distribution mechanism was migrated; the prompt text was not. Prompt bodies, META-RULES (MR-15), the petrova_prompt_path shell helper, and the petrova_install_playbook contract still instruct agents to resolve sibling prompts as literal core/prompts/NN-*.md filesystem paths. Consumer repos have no such tree, so every governed repo halts with a “source-set discrepancy” the moment a prompt hands off to another prompt.

Decision

All playbook prompt cross-references resolve via Fleet MCP. The canonical form is petrova.prompts.get <slug> (list via petrova.prompts.list). Filesystem prompt resolution (petrova_prompt_path, “paste core/prompts/…”) is removed from agent-facing instructions. The petrova_install_playbook contract is inverted: it no longer rewrites cross-references to literal local paths.

Consequences

MR-15 reworded to drop the core/prompts/00-bootstrap.md path assumption.
META-RULES version 1.2 → 1.3.
petrova_prompt_path retained only as an operator/author convenience in eva-hq, never referenced by consumer-facing prompt bodies.
Consumer agents need Fleet MCP reachable to advance the lifecycle (already true under the 2026-05-14 model).

Approval

Human-approved 2026-05-16 (operator: alex@devarno.com) — strategy selected explicitly: “Rewrite cross-refs to MCP fetch”.