Reconcile the approved October 5 editorial decisions into playbooks/g…

## 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.

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.

## 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.

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.

## 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.

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.

## 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.

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.

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.