> ## Documentation Index > Fetch the complete documentation index at: https://prism.ntecdev.ai/llms.txt > Use this file to discover all available pages before exploring further. # Plan #2: Methodology enforcement + cross-agent continuity (Donna review 2, 2026-04-17) > Methodology enforcement + cross-agent continuity (Donna review 2, 2026-04-17) **Status:** `active` · **Version** `1` · Filed 2026-04-17 # Plan 2: Methodology Enforcement + Cross-Agent Continuity Source: Donna's second review session on 2026-04-17 (Lola project, claude.ai). Builds on Plan #1. ## Goal Operationalize the four-ring layered enforcement architecture (ADR #6). Make methodology compliance emerge from utility. Enable cross-agent continuity through the hd\_exec pickup verb. Extend Prism beyond code projects via ptype expansion. ## Parent ADRs * ADR #6 — Layered enforcement architecture (4 rings) * ADR #7 — PRISM.md as composed template with opt-in upgrades * ADR #8 — hd\_exec verb for symmetric handoff pickup * ADR #9 — Ring 4 soft enforcement with telemetry * ADR #10 — Ptype expansion to research / travel / home-improvement ## Sequencing ### Wave A — The BIOS and the constitution (do first) 1. Rewrite CLAUDE.md as thin BIOS. Target: fewer than 20 lines. Imperative launch sequence: (a) read AGENTS.md, (b) read PRISM.md if present, (c) call prism\_start with PID from PRISM.md header or project\_dir lookup, (d) display status card. No methodology content in CLAUDE.md itself — only the launch imperative. 2. Rewrite AGENTS.md as the universal constitution. Move all truly-universal principles here (Context Is Currency, Explicit Over Implicit, AI First/Only, never delete, session lifecycle). Everything code-specific moves to prism-application.md in Wave B. 3. Create the Prism install directory structure for templates: templates/prism-base.md, templates/prism-application.md. Stubs OK for now; populate during Wave B. ### Wave B — The template system 4. Author templates/prism-base.md. Universal methodology: session lifecycle (start/wrap/handoff), artifact vocabulary (Plan/Spec/Decision/TODO/Journal/Retro/Note/Memory), what each is for, when to use which. 5. Author templates/prism-application.md. Code-project specifics: ADRs for architectural decisions, plans for phases, retros at phase boundaries, specs as requirements, tests-before-code discipline. 6. Extend prism\_scaffold / bootstrap\_project to compose PRISM.md from prism-base.md + prism-`{ptype}`.md at bootstrap time. Write methodology\_version header into generated PRISM.md. 7. Backfill: generate PRISM.md for PID-PGR01 from current templates as a smoke test. ### Wave C — hd\_exec verb 8. Implement hd\_exec in Prism backend. Resolve PID from project\_dir or prompt. Fetch last handoff doc + recent deltas + focus-tagged TODOs + recent ADRs + current-phase retros. Return structured payload with status\_card. 9. Add session marker: hd\_exec sets a session\_source='handoff\_pickup' flag that prism\_wrap can inspect later (enables Ring 4 enforcement specific to handoff pickups). 10. Expose hd\_exec as an MCP tool in the Prism MCP server. Add to tool\_search inventory with description clarifying it is symmetric to prism\_wrap (wrap closes, hd\_exec opens). 11. Document hd\_exec usage pattern in AGENTS.md and prism-base.md: 'When starting a session to continue another agent's work, call hd\_exec instead of prism\_start.' ### Wave D — Ring 4 enforcement hooks 12. Implement prism\_start rules\_reminders array. Server computes: N open TODOs, last wrap timestamp, phases without retros, methodology\_version vs canonical, TODOs tagged to last handoff focus. 13. Implement prism\_wrap accounting inspection. Server checks session for prism\_todo complete calls, prism\_journal writes, prism\_retro creates, prism\_decide filings. Returns warning payload (not block) if work session had no accounting. 14. Add telemetry: per-agent accounting-completeness rate. Simple counter table: (agent\_id, wraps\_total, wraps\_with\_journal, wraps\_with\_todo\_close). 15. Add methodology-version drift detection in prism\_start. When PRISM.md methodology\_version is behind canonical template version, return upgrade prompt in rules\_reminders. ### Wave E — Ptype expansion 16. Author templates/prism-research.md overlay. Literature review as a phase, specs as claims-with-citations, decisions as methodology choices, TODOs as experiments/sources, retros at draft milestones. Lean on graph leg (Neo4j) for citation relationships. 17. Author templates/prism-travel.md overlay. Days as phases (or legs as sub-projects via parent\_pid), bookings as ADRs, contacts as notes, itinerary as plan. 18. Author templates/prism-home-improvement.md overlay. Research phase before action, vendor/product decisions as ADRs, failure-mode notes as G-scope candidates. 19. Smoke test: bootstrap a travel project (--ptype=travel). Frank runs through a real trip planning session. Retro afterward captures what felt natural vs forced — direct input for methodology refinement. ## Out of Scope * Hard enforcement (blocking prism\_wrap on missing accounting). Explicitly rejected by ADR #9. * Auto-upgrade of PRISM.md without user consent. Explicitly rejected by ADR #7. * Migrating existing projects' CLAUDE.md / AGENTS.md — those can stay as-is until Frank chooses to adopt the thin-BIOS pattern. PID-PGR01 is the pilot. ## Success Criteria * New project bootstrap produces CLAUDE.md + AGENTS.md + PRISM.md with correct ptype overlay. * hd\_exec on PID-PGR01 returns Donna's handoff doc + all her open work in a single structured payload. * prism\_start on a project with unaccounted sprints produces visible drift warnings. * Travel ptype smoke test completes end-to-end and the retro provides real methodology feedback. ## Source Artifacts * ADRs #6 through #10 on PID-PGR01. * This plan supersedes none of Plan #1's waves; they run in parallel.