Developer
The Developer space records gaps between Jue's target architecture and current implementation. It is for maintainers and implementation agents, not a prerequisite for ordinary users.
Reading order
- Architecture for stable principles.
- Documentation Contract for precedence.
- Implementation Status for current gaps.
- Roadmap for dependency-ordered delivery.
- Delivery Plan to claim work and submit evidence.
- Claude Code Execution Runbook for dependency-aware decomposition, parallel implementation, and verification.
- RFCs for proposals and decisions.
Documentation boundary
| Space | Question |
|---|---|
| Guide | How does a user complete a task? |
| Architecture | Why is Jue designed this way? |
| Reference | What is the ideal complete contract? |
| Developer | How far is implementation from that contract, and what comes next? |
Unimplemented Reference contracts remain normative and link here for status. Completing a feature requires synchronized implementation, tests, Agent support profiles, status, and Delivery Plan.