# Roadmap

The roadmap is evidence-gated. Dates are intentionally omitted until the work
has an owner and a verified execution window.

## Now — presentation and proof baseline

- [x] Preserve the nine-stage workflow and authority split.
- [x] Add direction-gate and visual-report logic tests.
- [x] Fail closed on malformed gates and reject empty declarations.
- [x] Publish explicit evidence states and degraded-mode boundaries.
- [x] Add deterministic repository validation and manifest verification.
- [x] Present the fictional Meridian outcome without implying a live run.
- [x] Add dependency-free run-order and completion validation with adversarial fixtures.

## Next — witnessed operation

- [x] Record the gate inside clean, live Claude Code sessions.
- [x] Publish a validated redacted run covering all nine stages.
- [x] Add isolated hostile/clean pages and browser witnesses for `visual-checks.js`.
- [x] Verify managed setup and doctor in isolated homes and the operator environment.
- [x] Record media-free and explicitly self-reviewed degraded paths.
- [ ] Record independent stranger installation feedback.
- [ ] Witness a paid-media integration only when a real project requires it.

## Later — evaluate, do not assume

- [ ] Decide whether a small state-machine runner adds safety without turning
  creative judgment into brittle automation.
- [ ] Add adapters only for integrations with stable, inspectable contracts.
- [ ] Define a release threshold after independent installation feedback.

## Explicit non-roadmap

Web Studio will not automatically publish without operator approval, treat a
model as the final authority for brand identity, claim visual checks are a full
accessibility audit, or hide paid generation behind an implicit retry loop.