LunaNet LSIS-AFS Deliverables Planning Pack
This folder contains execution-ready LunaNet plans organized for a 6-person team across Gateways 0-8.
Documents
Team Assumptions
- Team size: 6
- Roles: 3 engineers + 3 developers
- Objective: pass minimum viability gate and maximize score through evidence-driven execution.
Why This Structure
- The phase split follows dependency order: code families and encoding first, then signal and decoding, then integration and package hardening.
- RACI is separated into its own file to keep ownership stable even when phase tasks evolve.
- Program-level and phase-level plans are separated so schedule governance and implementation detail can evolve independently.
Usage
- Assign names to role placeholders and confirm role backups.
- Run phase plans as gateway checklists with weekly review against acceptance criteria.
- Keep RACI and evidence links current at each gateway close.
⬆️ Back to Top ⬆️