This roadmap describes public-safe showcase status and possible future phases.
The public showcase is sealed through MVP20 as review-only release seal output.
Current public documentation polish extends through MVP30:
- MVP21 README polish
- MVP22 public verification guide
- MVP23 public quickstart
- MVP24 public architecture overview
- MVP25 public artifact index
- MVP26 public release notes
- MVP27 public demo transcript
- MVP28 public safety boundary
- MVP29 public reviewer guide
- MVP30 public case study
ARMOR currently demonstrates:
- safe target policy
- release gate reporting
- allowlist validation
- rollback manifest planning
- action preview schema
- action ledger schema
- post-action verification schema
- emergency stop schema
- operator confirmation schema
- execution readiness aggregation
- pre-execution freeze checks
- public regression aggregation
- public release bundle summary
- public release seal
The public showcase intentionally does not implement:
- enforcement
- remediation
- quarantine
- purge
- lockdown
- firewall control
- Wi-Fi control
- Bluetooth control
- USB blocking
- process termination
- permission modification
- private target scanning
ARMOR is being broadened from a Linux-first showcase into a platform-adapter framework.
Planned public-safe expansion:
- MVP37 public cross-platform strategy
- MVP38 public platform capability matrix complete
- MVP39 public adapter contract schema complete
- MVP40 public cross-platform release seal complete
- MVP41 public Linux adapter contract alignment
- MVP42 public Windows adapter plan
- MVP43 public macOS adapter plan
- MVP44 public Android adapter plan
- MVP45 public iOS adapter plan
- MVP46 public cross-platform adapter sample outputs complete
- MVP47 public platform adapter sample validator complete
- MVP48 public adapter validation verification wiring complete
- MVP49 public docs index adapter validation wiring complete
- MVP50 public cross-platform validation seal complete
- MVP51 public cross-platform regression helper complete
- MVP52 public cross-platform regression verification wiring complete
- MVP53 public cross-platform regression seal complete
- MVP54 public cross-platform summary update complete
- MVP55 public README cross-platform status update complete
- MVP56 public showcase final seal
The ARMOR core should remain platform-neutral. Platform-specific behavior should live in adapters.
Future public-safe work could include:
- richer sample report explanations
- diagram assets generated from existing public docs
- public FAQ
- public glossary
- public testing matrix
- public changelog by phase
- recruiter-focused project summary
Any future enforcement work would require a separate private design phase and must prove:
- explicit operator authorization
- strict allowlist boundaries
- rollback manifest completeness
- dry-run parity
- emergency stop readiness
- post-action verification
- full regression pass
- release freeze approval
Treat this repository as a review-only engineering showcase. It proves safety structure and release discipline before action capability.