How The Views Relate
Cautilus design specs use one promise model and several reading views. The map names the product concepts. Each view chooses an order and emphasis for a specific reader task.
Canonical ledger: Promise Ledger. Naming rules: Names And Keys.
Map
The Promise Ledger names workflow promises, cross-cutting rules, and their first-order relationships. The model favors stable concepts and short commitments over explanation of past debates.
Views
| view | reading task | primary order |
|---|---|---|
| User Workflow | understand what a Cautilus user can do | readiness, discovery, evaluation, improvement |
| Contracts | see which contracts and evidence routes maintain the promises | evidence-route ownership |
| Cross-Cutting Rules | inspect rules and risks that apply across workflows | concern name |
| Evidence State | inspect current evidence, selected evidence, and open proof gaps | evidence state |
Context Map
| context | owns |
|---|---|
| Promise identity | human names, compact keys, view membership |
| User workflow | reader-facing jobs and acceptance criteria |
| Maintainer evidence | contracts, adapters, fixtures, and evidence routes |
| Host execution | prompts, models, credentials, runtime wiring, fixtures, and acceptance policy in host repos |
| Evidence state | selected evidence, stale evidence, and open proof gaps |
Traceability
The current traceability contract is Markdown reachability plus executable Specdown checks.
Typed Specdown traceability is tracked as gap.traceability-config in Proof Gaps.