Consequences
Positive
- A public experience claim becomes traceable from journey through declaration, test, evidence, projection, and gate.
- Host, CLI, documentation, issue, support, and release surfaces stop depending on manually synchronized lists.
- New hosts can land honest partial slices without overclaiming full support.
- Humans and agents can discover options, outputs, side effects, errors, and recovery without reading implementation source.
- Maintainers can distinguish deterministic, package, native, installed, deployed, and release evidence.
- Privacy and support become first-use architecture rather than troubleshooting footnotes.
- DX improvements can be evaluated by task outcomes and evidence freshness.
Negative and Operational Cost
- Structured declarations, schemas, compatibility policy, validators, and dual migrations add short-term work.
- Native evidence has recurring execution, isolation, redaction, freshness, and triage cost.
- Projection tooling can introduce review noise while existing copies are being migrated.
- Maintainers must own demotion and rollback behavior, not only successful promotion.
- Journey measurement requires careful denominator and privacy definitions.
- Supporting curated prose beside projected facts requires explicit boundaries and tests.