Skip to content

[Methodology] Machine-readable PIR status sidecar (pir-status.json) for cross-cycle inheritance #2033

@pethers

Description

@pethers

📋 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

  1. JSON Schema schemas/pir-status.schema.json defining {pir_id, cycle, statement, trigger, status, confidence, inherits_from[], evidence_refs[]}.
  2. Each analysis/daily/{date}/{subfolder}/pir-status.json validated in CI.
  3. New script scripts/roll-forward-pirs.ts propagates open PIRs from yesterday → today's cycle automatically.
  4. CI gate: missing/invalid pir-status.json fails the analysis-gate.

🔧 Implementation Approach

  1. Define schema (Documentation Architect).
  2. Implement roll-forward script (data-pipeline-specialist consulted).
  3. Add Vitest schema-validation test.
  4. 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

  • schemas/pir-status.schema.json published
  • pir-status.json template emitted in all 11 workflows
  • Roll-forward script with idempotency
  • CI gate enforces presence + validity
  • Methodology guide updated

📚 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

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions