49 lines
1.3 KiB
Markdown
49 lines
1.3 KiB
Markdown
# SCOPE
|
|
|
|
## Current Reality
|
|
|
|
`whynot-control` is the control repository for organizing prototype exploration and early market-signal capture.
|
|
|
|
It currently serves as a place to:
|
|
|
|
- collect prototype ideas;
|
|
- define intake and triage;
|
|
- hold prototype cards;
|
|
- record signals and feedback;
|
|
- prepare closed beta concepts;
|
|
- define promotion criteria;
|
|
- prevent experiments from becoming unmanaged obligations.
|
|
|
|
## In Scope
|
|
|
|
- Prototype idea capture.
|
|
- Prototype classification.
|
|
- Early user feedback notes.
|
|
- Market-signal tracking.
|
|
- Closed beta planning.
|
|
- Experiment records.
|
|
- Promotion recommendations.
|
|
- Agent-assisted drafting and analysis.
|
|
|
|
## Out of Scope
|
|
|
|
- Production implementation.
|
|
- Long-term product maintenance.
|
|
- Payment processing.
|
|
- Legal investment documentation.
|
|
- Public launch operations.
|
|
- Binding financial, legal, or tax conclusions.
|
|
|
|
## Adjacent Areas
|
|
|
|
- `helix`: implementation and intent-to-product production path.
|
|
- `coulomb`: idea and knowledge exploration product surface.
|
|
- `sloppers`: community and discussion hub.
|
|
- `plenitude`: commercial store and offer hub.
|
|
- `binky`: company vehicle and business/legal control.
|
|
- `tegwick`: personal operating control.
|
|
|
|
## Scope Guardrail
|
|
|
|
`whynot-control` explores and validates. It does not absorb all product development.
|