Capture
Reconcile the approved October 5 editorial decisions into playbooks/g…
Draft text
Review
Update: playbooks/growth-master
Replace the exact text below. Approval stops if the document has changed.
Before
## Shared system Connect what Mattias and Pure know, build, and publish with relevant conversations, career opportunities, projects, and partnerships. Growth is part of Patterns OS, with Markdown and Git as the source of truth. Positioning → Content → Proof → Pipeline → Sales. Expertise and work inform useful public content. Relevant people can recognize the point of view, examine the proof, and begin a conversation about a specific problem. Record actual interactions and outcomes; relevance alone does not establish that someone saw a post or became a lead. [Mattias Growth Playbook](/playbooks/growth-mattias) owns personal voice and distribution. [Pure Growth Playbook](/playbooks/growth-pure) owns studio presentation. [Growth Content System](/playbooks/growth-content-system) owns the editorial workflow and measurement rules. Shared positioning and market priorities live here rather than being copied into each playbook.
After
Shared system
Connect what Mattias and Pure know, build, and publish with relevant conversations, career opportunities, projects, and partnerships. Growth is part of Patterns OS, with Markdown and Git as the source of truth.
Positioning → Content → Proof → Pipeline → Sales.
Expertise and work inform useful public content. Relevant people can recognize the point of view, examine the proof, and begin a conversation about a specific problem. Record actual interactions and outcomes; relevance alone does not establish that someone saw a post or became a lead.
Mattias Growth Playbook owns Wikman's account positioning and topic reference. Pure Growth Playbook owns the studio's account positioning and topic reference. Growth Content System is authoritative for shared publishing rules, writing preferences, scheduling proposals, record structure, and measurement. Shared commercial positioning and market priorities live here.
Mattias explicitly approved these editorial decisions in the attached October 5 source and requested immediate reconciliation through Review and Apply. Publication notes remain user-reported; missing details and the unapproved schedule remain explicit.
Update: playbooks/growth-master
Replace the exact text below. Approval stops if the document has changed.
Before
## Mattias and Pure Use one Growth system, filterable as Mattias, Pure, or Both. Neither career nor studio work has permanent priority. A shared project or proof item can support both, while the resulting content uses the appropriate voice. [Wikman](/mattias) holds personal identity and practice, with wikman.co as the primary website. [Pure](/pure) holds studio identity and practice, with purerxd.com as its separate website. Future selected outputs may serve those sites and Slides; V1 does not synchronize them.
After
Mattias and Pure
Use one Growth system, filterable as Mattias, Pure, or Both. Neither career nor studio work has permanent priority. A shared project or proof item can support both accounts; their post topics follow the distinct-topic rule in Growth Content System.
Wikman holds personal identity and practice, with wikman.co as the primary website. Pure holds studio identity and practice, with purerxd.com as its separate website. Future selected outputs may serve those sites and Slides; V1 does not synchronize them.
Mattias explicitly approved these editorial decisions in the attached October 5 source and requested immediate reconciliation through Review and Apply. Publication notes remain user-reported; missing details and the unapproved schedule remain explicit.
Update: playbooks/growth-master
Replace the exact text below. Approval stops if the document has changed.
Before
## V1 boundaries Project, Proof, and Content are approved document types; Mattias has approved their schemas and the three pilot examples. Topic is lightweight Content metadata, not an entity. Reuse companies, people, relationships, and existing trackers. New business-development tracking should remain a small Playbook until real usage requires more. Publish manually. Do not add social APIs, automated outreach, AI lead scoring, revenue forecasts, external synchronization, a Topic database, or a separate marketing database. AI-derived Knowledge changes still require Review and Apply. These playbooks record the approved operating strategy, not a claim that every Growth capability already exists.
After
V1 boundaries
Project, Proof, and Content are approved document types. The October 5 editorial decisions supersede the earlier per-platform Content policy; Growth Content System owns the current record convention and its implementation limits. Topic remains lightweight Content metadata, not an entity. Reuse companies, people, relationships, and existing trackers. New business-development tracking should remain a small Playbook until real usage requires more.
Follow the publishing workflow in Growth Content System. Do not add social APIs, automated outreach, AI lead scoring, revenue forecasts, external synchronization, a Topic database, or a separate marketing database. AI-derived Knowledge changes still require Review and Apply. These playbooks record the approved operating strategy, not a claim that every Growth capability already exists.
Mattias explicitly approved these editorial decisions in the attached October 5 source and requested immediate reconciliation through Review and Apply. Publication notes remain user-reported; missing details and the unapproved schedule remain explicit.