This index provides navigation for the Nightscout documentation structure. Each folder has a specific purpose to help developers and AI agents quickly find relevant information.
| Folder | Purpose | When to Use |
|---|---|---|
audits/ |
System analysis and current state documentation | Understanding existing architecture, identifying issues |
meta/ |
Project-level navigation and progress tracking | High-level orientation, roadmaps, overall progress |
requirements/ |
Formal requirements specifications by area | Defining what must be true for correctness |
test-specs/ |
Test specifications with progress tracking | Writing tests, tracking coverage gaps |
proposals/ |
RFC-style proposals for new features | Proposing changes, reviewing designs |
data-schemas/ |
Collection and field documentation | Understanding data structures |
plugins/ |
Plugin-specific documentation | Working with specific plugins |
- Architecture Overview - System design and component relationships
- Modernization Roadmap - Future direction and priorities
- Documentation Progress - What's been documented, what's pending
- API Layer Audit - REST endpoints (v1, v2, v3)
- Data Layer Audit - MongoDB collections and storage
- Security Audit - Authentication, authorization, vulnerabilities
- Real-Time Systems Audit - Socket.IO, WebSocket handling
- Messaging Subsystem Audit - Notifications, alerts
- Plugin Architecture Audit - Plugin system design
- Dashboard UI Audit - Frontend components
- Data Shape Requirements - Input/output shape handling
- Authorization Security Requirements - Auth system requirements
- API v1 Compatibility Requirements - Client compatibility
- Shape Handling Tests - Array/object normalization tests
- Authorization Tests - Security and auth tests
- Coverage Gaps - Aggregated test gaps by priority
- Treatments Schema - Treatment collection fields
- Profiles Schema - Profile structure
- OIDC Actor Identity - Verified actor identity RFC
- Agent Control Plane - AI agent collaboration design
- Testing Modernization - Test framework updates
- MongoDB Modernization - Driver upgrade plan
When working in this codebase:
- Start with INDEX.md (this file) to orient yourself
- Check test-specs/ for the area you're working on - each spec tracks its own progress and gaps
- Check requirements/ for formal correctness criteria
- Check audits/ for current implementation details
- Update the relevant test-spec's Progress section when you make discoveries
Each test area is self-contained with:
- Requirements (what must be true)
- Test specifications (how to verify)
- Progress tracking (what's done, what's discovered)
- Priority gaps (what to work on next)
This allows focused iteration on one topical area at a time.