A CV is not a content calendar, but it contains the first map of one.
Roles reveal recurring problem spaces. Project bullets reveal systems, decisions, and constraints. Skills suggest mechanisms you can explain. Measured outcomes establish proof boundaries. The work is to normalize those fragments without turning them into claims the source does not support.
Build the evidence inventory
Group notes into services, target clients, proof points, repeated questions, technical mechanisms, and lessons learned. Keep editable source text so errors can be corrected before generation.
Create durable themes
A durable theme is larger than a post but narrower than a profession. “Agent evaluation for operational decisions” is useful. “AI” is not. Each theme should support observations, checklists, comparisons, and at least one deeper guide.
Keep templates separate from voice
A post structure describes the order of ideas. Voice describes rhythm, phrasing, hooks, transitions, restraint, and CTA style. Keeping them separate lets you reuse a strong structure without making every draft sound identical.
Review the system monthly
Archive themes that no longer match the work you want. Add questions from sales calls and project reviews. Promote repeated post topics into guides. Remove proof points you can no longer verify or disclose.
The result is not an automated persona. It is an evidence library that makes useful writing easier to begin and safer to publish.