Internal Documentation
Purpose: Working documents for active development and internal processes
Audience: Development team, architects, and project contributors
🧭 Quick Access: For comprehensive internal navigation, see NAVIGATION.md
🌐 Public Docs: For project information and user guides, see README.md
Directory Organization
Development (development/)
- Current sprint/iteration work
- Development methodologies and tools
- Agent coordination and handoff prompts
- Active planning and status tracking
Architecture (architecture/)
- Current architectural decisions (ADRs)
- Domain models and system design
- Technical patterns and guidelines
- Architecture evolution tracking
Planning (planning/)
- Active planning cycles
- Backlog and issue tracking
- Roadmap and strategic planning
- Resource allocation and timelines
Operations (operations/)
- Deployment and infrastructure
- Monitoring and maintenance
- Performance tracking
- Operational procedures
Usage Guidelines
Active vs Historical
- Internal docs: Current, actively maintained content
- Archives: Historical content moved after completion
- Clear status: Use status indicators for document lifecycle
Working Document Lifecycle
- Draft - Initial creation in appropriate subdirectory
- Review - Internal review and collaboration
- Active - Current working version
- Complete - Finished, ready for archive
- Archived - Moved to
/docs/archives/
Cross-References
- Link to archived decisions and historical context
- Reference public documentation where appropriate
- Maintain archaeological research links
Access Patterns
By Role
- Developers: Focus on
development/ and architecture/
- Product Managers: Focus on
planning/ and development/
- Operations: Focus on
operations/ and architecture/
- Architects: Access across all internal directories
By Work Type
- Current tasks:
development/active/
- Technical decisions:
architecture/current/
- Sprint planning:
planning/current/
- System operations:
operations/
Internal documentation organization established: September 20, 2025