Capture
8 items captured together
Oct 5, 2026, 7:03 PM
Preserve overlapping guidance from the pre-reconciliation account playbooks in the shared authoritative location, as requested by Mattias. Existing Mattias Voice: Avoid generic motivational content, empty AI hot takes, forced engagement bait, and portfolio promotion without a useful problem or lesson. Existing cadence: Publish when there is something useful and supported to say. Pure cadence: Do not publish unsupported claims or repeat a post merely to meet a number.
Review
Update: playbooks/growth-content-system
Replace the exact text below. Approval stops if the document has changed.
Before
- Do not use em dashes or decorative punctuation.
After
Existing account guidance, preserved under the user-approved reconciliation instruction.
Update: playbooks/growth-content-system
Replace the exact text below. Approval stops if the document has changed.
Before
This is not a publishing commitment or automation, and it does not reinstate the superseded platform-specific quotas.
After
Existing account guidance, preserved under the user-approved reconciliation instruction.
Reconcile the approved October 5 editorial decisions into content/wikman-ai-models-frontend-engineering-2026-10-05. Preserve unrelated existing text. Apply the approved changes now.
Review
Update: content/wikman-ai-models-frontend-engineering-2026-10-05
Append the text below. Existing writing stays unchanged.
Addition
Publication note
User-reported publication date: October 5, 2026.
Wikman reports a post about the latest AI models and the changing relationship between design and frontend engineering.
Length: medium.
Visual: Text-only; no image.
No specific model claims or final published wording have been supplied.
Canonical copy
Final published copy has not been supplied. This record contains publication notes, not a transcript of the published post. No draft is treated as confirmed published copy.
LinkedIn publication and results
Platform-specific publication confirmation, date, time, and URL: not supplied.
Impressions, meaningful responses, clicks, and measurement date: not supplied.
Actual conversations and linked outcomes: not supplied.
X publication and results
Platform-specific publication confirmation, date, time, and URL: not supplied.
Impressions, meaningful responses, clicks, and measurement date: not supplied.
Actual conversations and linked outcomes: not supplied.
Record completeness
The publication report comes from Mattias. Research is the current form's completeness state while copy and platform evidence are outstanding; it does not mean that the reported publication did not happen. Follow the canonical-post and tracking convention in Growth Content System.
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.
Reconcile the approved October 5 editorial decisions into content/pure-site-building-in-public-2026-10-05. Preserve unrelated existing text. Apply the approved changes now.
Review
Update: content/pure-site-building-in-public-2026-10-05
Append the text below. Existing writing stays unchanged.
Addition
Publication note
User-reported publication date: October 5, 2026.
Pure reports the site live at exactly 36% complete and is building in public.
Length: medium.
Visual: Still image. The image asset has not been supplied.
Pure plans an open-source release on GitHub. This is a future intention, not a completed release.
Canonical copy
Final published copy has not been supplied. This record contains publication notes, not a transcript of the published post. No draft is treated as confirmed published copy.
LinkedIn publication and results
Platform-specific publication confirmation, date, time, and URL: not supplied.
Impressions, meaningful responses, clicks, and measurement date: not supplied.
Actual conversations and linked outcomes: not supplied.
X publication and results
Platform-specific publication confirmation, date, time, and URL: not supplied.
Impressions, meaningful responses, clicks, and measurement date: not supplied.
Actual conversations and linked outcomes: not supplied.
Record completeness
The publication report comes from Mattias. Research is the current form's completeness state while copy and platform evidence are outstanding; it does not mean that the reported publication did not happen. Follow the canonical-post and tracking convention in Growth Content System.
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.
Reconcile the approved October 5 editorial decisions into playbooks/growth-content-system. Preserve unrelated existing text. Apply the approved changes now.
Review
Update: playbooks/growth-content-system
Replace the exact text below. Approval stops if the document has changed.
Before
## Topic and pillar Pillar identifies the editorial strand in the relevant owner playbook. Topic is lightweight metadata on Content for grouping specific subjects such as AI-native design, design systems, or personal software. Topic is not an entity or a separate database. Reuse a consistent topic label where the meaning is the same. A topic can span Mattias and Pure, multiple platforms, projects, and pillars. Do not silently reclassify historical records or manufacture topic links from a mention alone.
After
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-content-system
Replace the exact text below. Approval stops if the document has changed.
Before
## Editorial workflow Idea → Research → Draft → Ready → Published. An idea identifies a useful problem or point of view. Research identifies supporting material and open questions. Drafting connects the buyer problem, point of view, experience, and proof. Ready means a human has reviewed the version for publication. Publication is manual and records the actual URL and date. Repurposing and results continue after publication; they are not mandatory final states. A LinkedIn version may be published while an X version is still a draft. Mattias, Pure, and Both are explicit lenses, with no permanent preference for one.
After
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-content-system
Replace the exact text below. Approval stops if the document has changed.
Before
## Outcomes and learning Prioritize qualified conversations, opportunities, introductions, relevant inbound, and meaningful replies or comments, followed by audience growth and impressions. Record enough context to explain what happened and what to try next. Omit missing values rather than interpreting them as zero. Topic-level learning should eventually connect published versions with explicitly recorded conversations and opportunities. Count a conversation or opportunity once within a topic, even if it references several posts. Separate publication count from idea count, and label association rather than claiming causation unless supported. Start with manual records and linked notes rather than analytics integrations.
After
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-content-system
Replace the exact text below. Approval stops if the document has changed.
Before
## Reuse and future outputs Reuse one canonical Project or Proof record across content, outreach, applications, proposals, and conversations. Give each publication version its own publisher and platform context. Materially different ideas can become linked Content records. Design records so explicitly selected content may later feed wikman.co, Pure, and Slides. V1 does not synchronize external destinations, auto-publish, collect social analytics, automate outreach, or infer lead scores. Exact Project, Proof, and Content schemas and example records remain subject to Mattias's review before implementation.
After
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-content-system
Append the text below. Existing writing stays unchanged.
Addition
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.
Reconcile the approved October 5 editorial decisions into playbooks/growth-pure. Preserve unrelated existing text. Apply the approved changes now.
Review
Update: playbooks/growth-pure
Replace the exact text below. Approval stops if the document has changed.
Before
## Voice Emphasize proof, methodology, capabilities, outcomes, and the work. Mattias can explain a personal experiment and its lesson; Pure should explain how that practice informs the studio's approach. Reuse the underlying evidence without duplicating the personal post.
After
Voice
Pure is a tiny, flexible design studio combining foundational design skills, craft, systematic thinking, and current AI tools. Show founders and leaders what this makes possible through actual work.
Emphasize the work, decisions, methodology, capabilities, and supported outcomes. Follow the shared writing preferences in Growth Content System.
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-pure
Replace the exact text below. Approval stops if the document has changed.
Before
## Channels and cadence LinkedIn: approximately one to two meaningful posts per week. X: approximately two to three posts per week. Treat these as flexible guidelines. Do not publish unsupported claims or repeat a post merely to meet a number.
After
Channels and cadence
Follow the canonical-post distribution rules and the explicitly unapproved schedule proposal in Growth Content System. Earlier platform-specific weekly targets are superseded; there is no adopted weekly quota.
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-pure
Replace the exact text below. Approval stops if the document has changed.
Before
## Availability Occasionally state the problems Pure can help with, the engagement being sought, and current capacity when confirmed. Use a clear next step. Keep availability a minority of content.
After
Availability
Occasionally state the problems Pure can help with, the engagement being sought, and current capacity when confirmed. Use a clear next step. Follow the shared availability and promotion balance in Growth Content System.
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-pure
Replace the exact text below. Approval stops if the document has changed.
Before
## Operating workflow Follow the [Growth Content System](/playbooks/growth-content-system). Reuse Project and Proof records across Mattias and Pure, with distinct publication versions. Keep commercial target judgments in [Pure Opportunity Rankings](/playbooks/pure-opportunity-rankings), company facts on company pages, and actual conversations and opportunities in their authoritative trackers.
After
Operating workflow
Follow Growth Content System. Reuse Project and Proof records across Mattias and Pure while keeping the accounts' post topics distinct. Keep commercial target judgments in Pure Opportunity Rankings, company facts on company pages, and actual conversations and opportunities in their authoritative trackers.
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-pure
Append the text below. Existing writing stays unchanged.
Addition
Topic reference
Building purerxd.com in public; tiny and flexible studio partnerships; shaping products with founders; craft, composition, interaction and motion; design systems; supported client work and lessons; studio research, prototypes and own products. Use these to choose specific topics within the existing editorial strands, not as mandatory post formats.
October 5 publication note
The user-reported note is held in Pure: site building in public. That Content record owns the supplied progress figure and future release intention.
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.
Reconcile the approved October 5 editorial decisions into playbooks/growth-mattias. Preserve unrelated existing text. Apply the approved changes now.
Review
Update: playbooks/growth-mattias
Replace the exact text below. Approval stops if the document has changed.
Before
## Voice Lead with thinking, personality, exploration, decisions, and lessons. Most posts should connect a buyer problem with a point of view, experience, and relevant proof. Distinguish what happened from an interpretation or an experiment still being tested. Avoid generic motivational content, empty AI hot takes, forced engagement bait, and portfolio promotion without a useful problem or lesson.
After
Voice
Wikman is an experienced designer and AI nerd exploring models, building, systems, and personal perspectives in depth. Speak to founders and leadership through concrete observations and experiments. Lead with thinking, personality, exploration, decisions, and lessons; use a buyer problem when it fits the observation, without forcing every post into a sales argument.
Do not frame personal posts as a first post or a return to posting. Follow the shared writing preferences in Growth Content System.
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-mattias
Replace the exact text below. Approval stops if the document has changed.
Before
## Channels and cadence LinkedIn: approximately three meaningful posts per week. X: approximately five to seven posts per week. These are flexible planning guidelines, not quotas. Publish when there is something useful and supported to say.
After
Channels and cadence
Follow the canonical-post distribution rules and the explicitly unapproved schedule proposal in Growth Content System. Earlier platform-specific weekly targets are superseded; there is no adopted weekly quota.
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-mattias
Replace the exact text below. Approval stops if the document has changed.
Before
## Availability and collaboration Occasionally explain the problems and engagement types Mattias wants to work on: leadership, founding designer, embedded, fractional, advisory, and project opportunities. Keep availability a minority of content and confirm current capacity before making a public statement.
After
Availability and collaboration
Occasionally explain the problems and engagement types Mattias wants to work on: leadership, founding designer, embedded, fractional, advisory, and project opportunities. Confirm current capacity before making a public statement. Follow the shared availability and promotion balance in Growth Content System.
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-mattias
Replace the exact text below. Approval stops if the document has changed.
Before
## Operating workflow Use the [Growth Content System](/playbooks/growth-content-system) for ideas, topic metadata, drafts, publication records, and outcomes. Link relevant projects, proof, companies, people, and tracker entries. Do not duplicate Pure's posts; adapt the point of view when the same underlying work supports both voices.
After
Operating workflow
Use Growth Content System for ideas, topic metadata, canonical copy, platform publication details, and outcomes. Link relevant projects, proof, companies, people, and tracker entries. Shared source work can inform both accounts without making their post topics the same.
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-mattias
Append the text below. Existing writing stays unchanged.
Addition
Topic reference
Deep AI model exploration; design and engineering; sketching, composition, Figma and code; designers as builders; POS and durable context; taste, originality and culture; complex-product thinking; player-coach leadership; personal experience, reading and observations. Use these to choose specific topics within the existing editorial strands, not as mandatory post formats.
October 5 publication note
The user-reported note is held in Wikman: AI models and frontend engineering. That Content record owns the supplied details and outstanding publication evidence.
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.
Reconcile the approved October 5 editorial decisions into playbooks/growth-master. Preserve unrelated existing text. Apply the approved changes now.
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.
8 of 8 · Text
Approved by Mattias on October 5, 2026
Approved by Mattias on October 5, 2026. Reconcile into existing Growth playbooks, preserving local edits and using Review and Apply. Commit and push only editorial changes and required supporting records. Publishing rules: Pure and Wikman always have different topics. Each account uses one canonical post, published one-to-one on LinkedIn and X with identical copy and the same visual when included. Two posts across four placements, not four platform-specific versions. Use longer X posts when needed; surface constraints rather than silently rewriting. Vary total length across short observations, medium reflections, and longer explorations. Images are optional and must contribute meaning. Publishing remains manual. Positioning: Pure is a tiny, flexible design studio combining foundational design skills, craft, systematic thinking, and current AI tools. Show founders and leaders what this makes possible through actual work. Wikman is an experienced designer and AI nerd exploring models, building, systems, and personal perspectives in depth. Speak to founders and leadership through concrete observations and experiments. Do not frame personal posts as a first post or return to posting. Availability and promotion remain a minority. Writing preferences: No em dashes or decorative punctuation. Plain, specific language with creative personality. Avoid common AI phrases, generic marketing language, and vague metaphors. Short paragraphs; balanced sentence lengths without mechanically equal sentences. Preserve my phrasing and meaning when correcting grammar. Curious, confident, thoughtful, occasionally playful. Questions arise naturally, not mandatory engagement prompts. Read referenced sources before factual claims; distinguish personal interpretation from verified evidence. Topic reference: Pure: building purerxd.com in public; tiny and flexible studio partnerships; shaping products with founders; craft, composition, interaction and motion; design systems; supported client work and lessons; studio research, prototypes and own products. Wikman: deep AI model exploration; design and engineering; sketching, composition, Figma and code; designers as builders; POS and durable context; taste, originality and culture; complex-product thinking; player-coach leadership; personal experience, reading and observations. Schedule proposal, NOT approved: Monday: Pure and Wikman. Wednesday: Wikman. Thursday: Pure. Friday: Wikman. Each post goes on both platforms. Preserve as a proposal for refinement. October 5, 2026 publication notes: Pure: site live at exactly 36% complete, building in public. Medium-length post with a still image. Wikman: latest AI models and the changing relationship between design and frontend engineering. Medium-length, text-only post. User-reported notes. Platform URLs, publication times, final published copy, and results have not been supplied. Do not invent them or treat draft wording as confirmed published text. Pure's planned open-source release on GitHub is a future intention, not a completed release. Tracking: One Content record per account's post, with separate publication details and results for LinkedIn and X. Track topic, length, visual, dates, URLs, impressions, meaningful responses, clicks where available, and actual conversations. Missing values stay unknown. Platform comparisons are observational, not controlled experiments.
Review
Saved. Analyzing sources…