doctrine lane

Role: Doer (reserved). Owns FWV v8 doctrine curation + pact fragment registry maintenance.

Session ID: TBD (not yet spawned) Status: not-spawned

What doctrine would own (when spawned)

• Pact fragment-registry maintenance (adding/removing/updating pact/governance/dna/fragment-registry.md)
• FWV v8 §00-29 curation (currently chrome handles)
• Question-index and constitutional-index maintenance
• Drift discovery (per FWV v8 §27)
• Cross-Mavis pact audit (does this plan citation use a real fragment_id?)

What doctrine does NOT own

• FVS chrome code (that's chrome)
• FreshCards substrate (that's cards)
• Refactor contract (that's fvre)
• Cross-Mavis state (that's Helper)

Why reserved, not yet spawned

Currently chrome covers doctrine work. Chrome wrote the FWV v8 contamination cleanup (8c093ef). Chrome drafted the Region Schema wording.

The doctrine lane will spawn when:

• Doctrine work outpaces what chrome can hold
• A new FVW v8 section is being authored and needs dedicated focus
• The pact fragment-registry needs a sweep

Spawning procedure

To spawn doctrine:

communicate with spawn={
  agent_name: "Coder",
  title: "doctrine Mavis"
}
content: <doctrine-scoped system prompt>

The system prompt should gate the session to:

• Read FVS Pact + FWV v8 only
• No code changes outside pact/
• Cite fragment_ids in every output
• Use GZ-1 protocol for any GOLD-file edit

How to reach

Currently N/A. If you need doctrine work and chrome is busy, ping Helper and request a doctrine spawn.