VPS admin
9478aaa22e
- Expand CANONICAL_STRATEGY with retrieval substrates, commerce chairs, multi-path discovery, ingestion, quality/decommission, trust bar - Rebalance platform vs SSP (portal is activation, not the company) - Add principal-PM use cases for endpoint auto repair and tourism board - Update product docs and README entry points
24 lines
815 B
Markdown
24 lines
815 B
Markdown
# Use cases
|
|
|
|
Canonical use cases for product, engineering, and GTM. These are operating specs, not marketing blurbs.
|
|
|
|
| ID | Name | Model | Status |
|
|
|----|------|-------|--------|
|
|
| [UC-01](./uc-01-endpoint-auto-repair.md) | Endpoint activation — independent auto repair | Model 1 | Spec |
|
|
| [UC-02](./uc-02-intermediate-tourism-board.md) | Intermediate activation — destination tourism board | Model 2 | Spec |
|
|
|
|
## How to write more of these
|
|
|
|
Use the same template as UC-01/UC-02:
|
|
|
|
- Problem and context
|
|
- Primary actor and stakeholders
|
|
- Preconditions
|
|
- Main success scenario (numbered)
|
|
- Alternate and exception paths
|
|
- Success metrics
|
|
- Explicit out of scope
|
|
- Open questions
|
|
|
|
If a use case only restates strategy prose, it is not ready. If it cannot drive a sprint ticket, it is not ready.
|