Commit Graph

4 Commits

Author SHA1 Message Date
Matthew Raymer
87594be5be docs: integrate Phase 1-3 into unified directive and activation guide
Updates master coordination documents to reflect Phase 1-3 completion status.

Changes:
- Update 000-UNIFIED-ALARM-DIRECTIVE.md status matrix:
  - P1: Marked as emulator-verified
  - P2: Marked as implemented, ready for testing
  - P3: Marked as implemented, ready for testing
  - V1-V3: Added verification doc rows
- Update ACTIVATION-GUIDE.md status bullets:
  - Phase 1: Complete and emulator-verified
  - Phase 2: Implemented, ready for emulator testing
  - Phase 3: Implemented, ready for emulator testing
  - Overall status updated to reflect all three phases

All three phases now have:
- Implementation directives
- Emulator testing guides
- Verification documents
- Automated test harnesses

Related:
- Unified Directive: docs/alarms/000-UNIFIED-ALARM-DIRECTIVE.md
- Activation Guide: docs/alarms/ACTIVATION-GUIDE.md
2025-11-27 10:01:55 +00:00
Matthew Raymer
bd842c6ef8 [ALARM-DOCS] fix(docs): remove duplicate status matrix and fix cross-references
Remove duplicate status matrix from Section 3.3 and consolidate to Section 11
as single source of truth. Fix all section number references throughout
documentation.

Changes:
- Remove duplicate status matrix table from Section 3.3
- Update all references from "Section 3.3" and "Section 10" to "Section 11"
- Fix phase directive paths to use consistent ../ prefix format
- Fix P1 path typo (missing "directive" in filename)
- Update Doc C status in matrix to reflect completion
- Remove duplicate text in Doc B baseline scenarios
- Remove self-referencing links in Doc B

All status matrix references now point to Section 11, eliminating confusion
about which matrix is authoritative.
2025-11-27 07:34:47 +00:00
Matthew Raymer
35babb3126 docs(alarms): unify and enhance alarm directive documentation stack
Create unified alarm documentation system with strict role separation:
- Doc A: Platform capability reference (canonical OS facts)
- Doc B: Plugin behavior exploration (executable test harness)
- Doc C: Plugin requirements (guarantees, JS/TS contract, traceability)

Changes:
- Add canonical rule to Doc A preventing platform fact duplication
- Convert Doc B to pure executable test spec with scenario tables
- Complete Doc C with guarantees matrix, JS/TS API contract, recovery
  contract, unsupported behaviors, and traceability matrix
- Remove implementation details from unified directive
- Add compliance milestone tracking and iOS parity gates
- Add deprecation banners to legacy platform docs

All documents now enforce strict role separation with cross-references
to prevent duplication and ensure single source of truth.
2025-11-25 10:09:46 +00:00
Matthew Raymer
afbc98f7dc chore: synch this plan 2025-11-25 08:04:53 +00:00