gconf canon diff · v2 to v3
что изменилось после звонка 30 апреля
v2 создал управляемый канон. v3 превращает его в архитектуру запуска: кто входит, какой first win получает, как маршрут персонализируется и где живут side tracks.
коротко
начать сегодняшний звонок с diff v2→v3, зафиксировать decisions, потом идти по пунктам.
главные дельты
1. success unit
v2: главный открытый вопрос.
v3: pattern + process + artifact/ritual + agency shift + next step.
2. launch handle
новая формула: актуальный AI-стек для неразработчиков.
решить: headline, subheadline or content pillar.
3. 0→1 spine
первая неделя даёт magic, first quick win and shareable artifact.
4. role paths
operators/leaders идут через intake, team cases and routing.
5. builders
advanced users становятся sidequest layer: shipyard, demo-day, coworking.
6. personalization
personas + quiz/bot routing become product infrastructure.
decision board
| area | decision | default proposal |
|---|---|---|
| handle | headline / subheadline / content pillar | subheadline: актуальный AI-стек для неразработчиков |
| identity | one-sentence object | agency with AI through patterns, artifacts, rituals and community |
| first win | mandatory week-1 result | one shareable artifact + one repeatable task-brief pattern |
| personas | first router set | zero starter, creator, operator, founder/manager, expert, builder |
| operators | inside core or separate | inside core as role path; corporate experiment later |
| builders | role in launch | sidequest: demo-day/shipyard, not core curriculum |
| cadence | default rhythm | Monday material drop + daily light cards |
| metrics | success evidence | week-4 use, shared artifact, process repeated 3+ times |
call flow
first 30 minutes
- read diff v2→v3
- decide handle and identity
- choose first-week 0→1 win
- choose personas/router inputs
then
- operators/corporate role path
- builder sidequest
- cadence and metrics
- continue pointwise from unresolved canon questions