# <Product> — Vision

<!-- Managed with super-ux (ux-contract v4). The layer above the chain. -->

<!--
  Owned by the `vision` skill (super-ux). Nine sections, these headings, in
  this order — `python3 docs/ux/lint.py` keys off them.

  This file says what the product IS. `scenarios.md` says what it DOES.
  A feature can satisfy every scenario and still violate the anti-vision;
  that case is the whole reason this layer exists.

  Writing this file is half the job. The other half is the
  `## Vision alignment — hard rule (super-ux)` block in the project's own
  instruction file — without it nothing ever reads this document.
-->

**Status:** draft
**Last reviewed:** <YYYY-MM-DD>

## 1. Essence

<!-- One sentence: "[Product] is [type of system] that changes how [user] [does X]".
     No feature names, no UI, no technology. Test: would it survive a total
     rewrite on a different stack? If not, it names an implementation. -->

## 2. Core idea

<!-- An observation about the world, not a problem statement:
       [X] is abundant.
       [Y] is scarce.
       -> this product bridges the gap.
     One observation, not a list. -->

## 3. What the system does

<!-- Continuous behaviour, verbs not nouns: observes ... understands ...
     transforms ... surfaces ... "Has a dashboard" is not behaviour. -->

## 4. The user's role

<!-- What the user becomes. Not "the user clicks" — the user directs, judges,
     decides. If it reads like operating any other tool, go deeper. -->

## 5. Principles

<!-- Three to five, each "we do X, not Y", where Y is something a reasonable
     team would genuinely have picked. A principle with no rejected side is a
     slogan. -->

## 6. Anti-vision

<!-- What this product refuses to become, explicitly. Name the adjacent
     products it could drift into and say no to each. This is the layer teams
     skip and the only one that ever settles an argument. -->

## 7. Horizon

<!-- Two to three years, as a direction. Not a roadmap — roadmaps belong in
     the tracker and go stale in a quarter. -->

## 8. The one sentence

<!-- If someone remembers exactly one thing. -->

## 9. The alignment test

<!-- Three to five questions any proposed feature must pass. These are what
     the hard rule in the instruction file actually runs. A stranger should be
     able to reject a plausible feature with them. -->

1. <question>
2. <question>
3. <question>