The documents describe the agreed-upon architecture and are the source of truth for implementation. When a key decision changes, the corresponding ADR is created or updated first, then the affected documents are updated in lockstep.
- Product requirements and boundaries
- Architecture
- Domain model
- JSON storage
- MCP integration
- Security
- AI endpoints and agent loop
- Implementation plan
- Testing strategy
- Operations and diagnostics
- Implementation progress
- UX decisions
- Headless chat testing
- Concurrent chat runs
- Logging
- Composer rules
- Default MCP tools
- Application management tools
- Compact turn view
- Asking the user (
ask_user) - LLM context management
- Tool selection and adaptive compaction
- Hidden model instructions and run completion
- Desktop app
- Chat artifacts and reviews (proposal)
- Long-term memory and project instructions
- Skills
- Token usage
- Chat widgets
- Dependency injection with Pure.DI
- Context request budgets and quality evaluation
- Styles and palette
- Asides and team messages
Generator diagnostics and complaints are tracked separately in Pure.DI observations and issues.
- ADR-001: Hosted Blazor WebAssembly
- ADR-002: JSON graph of immutable nodes
- ADR-003: Per-tool MCP permissions
- ADR-004: Responses API as the primary OpenAI protocol
- ADR-005: Fast unit tests on xUnit
- ADR-006: Architecture simplification
- ADR-007: Application management tools in an in-process MCP server
- ADR-008: Desktop app on Avalonia with the system web view
- ADR-009: One adaptive context policy
- ADR-010: Adaptive compaction decisions and measured savings
- ADR-011: Budgeted summary requests and separate quality evaluations
- ADR-012: Comparable prefix overlap and adaptive tool headroom
All listed documents have the status Accepted and capture decisions made before implementation began. NuGet package versions must be set centrally in Directory.Packages.props; the latest compatible stable version is chosen during implementation and pinned by the lock file.
The actual state of work, verification results, and the next increment are recorded in Implementation progress. It has the status Active and is updated after each completed increment.
All UI text, source-code comments, identifiers, technical messages, and project documentation introduced by the project are written in English.
Current decisions: ADR-006.
- Default MCP tools — process execution, permissions, and CLI.