Jue specifications
This section indexes Jue's public protocols and implementation contracts. Specifications define valid inputs, outputs, and compatibility boundaries. For design rationale and runtime flow, start with Architecture.
Recommended reading order
- Jue MVP defines the
Capability → Preset → Adapterproduct model, capability boundaries, and Preset directory contract. - Canonical Model defines the normalized structure shared by resolution, validation, and Adapters.
- External Capability references defines how a Preset references canonical directories through
ai.capabilities. - Codex / Claude Code Adapter defines native outputs and verification boundaries for Codex and Claude Code.
Implementers follow the Adapter standard, Extension API.
Status labels
| Status | Meaning |
|---|---|
| Draft | The target contract can still change; implementation gaps must be explicit |
| Accepted | The document is the accepted product or protocol boundary for the current phase |
| Implemented | The contract has implementation and verification evidence; later changes must consider compatibility |
The status at the top of each specification is authoritative for that document. If a specification and the implementation differ, verify the runnable behavior and track the mismatch as a protocol defect rather than silently choosing one.