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

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.

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.

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.

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.