gconf canon diff · v1 to v2
что изменилось после product-design call
v1 был хорошим каноном содержания. v2 добавляет систему управления каноном: provenance, отдельные версии, market-handle testing, security onboarding and focus/alignment module.
коротко
начинать звонок с diff: что v1 уже держит → что добавил звонок → какие решения нужны сегодня.
главные дельты
1. provenance
v1: source list в шапке.
v2: каждый тезис должен иметь lineage: source / synthesis / decision.
2. versions
v1: один visible документ.
v2: current, diff and archive разделены.
3. handle
v1: vibe coding as market handle with risk.
v2: handle для теста; identity строим через AI / agency / operating system.
4. dignity
v1: non-technical first.
v2: non-technical first without primitive language or patronizing tone.
5. security
v1: security hygiene under technical foundation.
v2: security/data-use is zero-step onboarding and support artifact.
6. focus
v1: focus as bottleneck.
v2: focus/alignment as product module after curiosity and inspiration.
decision board
| decision | current state | output today |
|---|---|---|
| success unit | open | one sentence + 3 evidence traces |
| headline object | open | 1 primary + 2 test handles |
| provenance marker | requested | minimal source/status format |
| security FAQ | underdefined | owner + scope |
| content map | emerging | first 5 entry pages |
| focus/alignment | emerging | one participant artifact |
call order
v1 baseline
this diff
decisions
owners / next artifacts
source paths
docs/canon/2026-04-30_diff-v1-to-v2.mddocs/gconf-positioning-marketing-product-canon.mddocs/canon/versions/2026-04-23_gconf-positioning-marketing-product-canon.md01-vision/inputs/2026-04-23_product-design-call-input.md