📋 Issue Type
Feature / Documentation & Tooling
🎯 Objective
Replace markdown-only PIR (Priority Intelligence Requirement) tracking with a structured pir-status.json per analysis cycle so PIRs roll forward automatically and cross-cycle gaps are detectable by CI.
📊 Current State (evidence from 2026-04-26 reflections)
realtime-pulse/methodology-reflection.md Improvement 4: "PIR disposition is tracked in human-readable markdown. Automated aggregation across analysis cycles requires manual extraction. Recommended improvement: Add a pir-status.json sidecar file alongside each analysis cycle's README.md, containing machine-readable PIR status, trigger conditions, and cross-cycle inheritance. This would enable automated PIR roll-forward and gap detection."
month-ahead/methodology-reflection.md: "PIR-1 through PIR-7 defined for next cycle" (markdown only).
monthly-review/methodology-reflection.md PIR-A described in prose only.
🚀 Desired State
- JSON Schema
schemas/pir-status.schema.json defining {pir_id, cycle, statement, trigger, status, confidence, inherits_from[], evidence_refs[]}.
- Each
analysis/daily/{date}/{subfolder}/pir-status.json validated in CI.
- New script
scripts/roll-forward-pirs.ts propagates open PIRs from yesterday → today's cycle automatically.
- CI gate: missing/invalid
pir-status.json fails the analysis-gate.
🔧 Implementation Approach
- Define schema (Documentation Architect).
- Implement roll-forward script (data-pipeline-specialist consulted).
- Add Vitest schema-validation test.
- Document in
analysis/methodologies/ai-driven-analysis-guide.md §PIR.
🤖 Recommended Agent
documentation-architect — owns templates/schemas; coordinates with data-pipeline-specialist for the script.
✅ Acceptance Criteria
📚 References
analysis/daily/2026-04-26/{realtime-pulse,month-ahead,monthly-review}/methodology-reflection.md
- Gate:
.github/prompts/05-analysis-gate.md
- ISMS: STYLE_GUIDE.md, Change_Management.md
📋 Issue Type
Feature / Documentation & Tooling
🎯 Objective
Replace markdown-only PIR (Priority Intelligence Requirement) tracking with a structured
pir-status.jsonper analysis cycle so PIRs roll forward automatically and cross-cycle gaps are detectable by CI.📊 Current State (evidence from 2026-04-26 reflections)
realtime-pulse/methodology-reflection.mdImprovement 4: "PIR disposition is tracked in human-readable markdown. Automated aggregation across analysis cycles requires manual extraction. Recommended improvement: Add apir-status.jsonsidecar file alongside each analysis cycle's README.md, containing machine-readable PIR status, trigger conditions, and cross-cycle inheritance. This would enable automated PIR roll-forward and gap detection."month-ahead/methodology-reflection.md: "PIR-1 through PIR-7 defined for next cycle" (markdown only).monthly-review/methodology-reflection.mdPIR-A described in prose only.🚀 Desired State
schemas/pir-status.schema.jsondefining{pir_id, cycle, statement, trigger, status, confidence, inherits_from[], evidence_refs[]}.analysis/daily/{date}/{subfolder}/pir-status.jsonvalidated in CI.scripts/roll-forward-pirs.tspropagates open PIRs from yesterday → today's cycle automatically.pir-status.jsonfails the analysis-gate.🔧 Implementation Approach
analysis/methodologies/ai-driven-analysis-guide.md§PIR.🤖 Recommended Agent
documentation-architect— owns templates/schemas; coordinates withdata-pipeline-specialistfor the script.✅ Acceptance Criteria
schemas/pir-status.schema.jsonpublishedpir-status.jsontemplate emitted in all 11 workflows📚 References
analysis/daily/2026-04-26/{realtime-pulse,month-ahead,monthly-review}/methodology-reflection.md.github/prompts/05-analysis-gate.md