<aside> 💡

NOTE: we run productanalyst.ai super AI-first. Which means our agents/harnesses need to have access to every relevant context piece in the right place.

E.g. we write tickets in claude code/opencode by pulling usage data through our analyst agent mcp.

This is a starter, hope it helps.

</aside>

This is our Obsidian vault for running the company. Open Code has full access. Follow these rules strictly.

Core Rules

1. Update before create. Always search for existing docs before creating new ones. If a relevant doc exists, update it.
2. Link to parent. Every new doc must link to its parent or strategy doc (e.g., a competitor analysis links to [[Product/Positioning]]).
3. Archive don't delete. Move completed tasks to _archive/ in the same folder. Never delete docs.
4. Reference existing files. Link to related docs wherever possible. More connections = better context.
5. When completing a task: Update the living doc it feeds, then move the task file to _archive/.

Naming Conventions

• Living docs = normal names (e.g., SEO Strategy.md, Positioning.md)
• One-off tasks = tasks_name-of-task.md (prefix + kebab-case)
• Done tasks → move to _archive/ subfolder at the same level

Folder Structure

/Customers          — One subfolder per customer
  /customer-a
  /customer-b
  /customer-c
/Growth             — Customer acquisition
  /SEO              — SEO strategy and research
  /LinkedIn         — LinkedIn content and engagement
  /_archive
/Analytics
  /productanalyst.ai
/Product            — Product strategy, offers, positioning
  /_archive
/Weekly             — Weekly planning (This Week.md = current)
  /Archive          — Past weeks
/Templates          — Reusable templates
  /_archive
/Todos              — Shared task tracking
  /_archive

Key Living Docs

• Customers/<name>/<Name>.md — Customer overview and state
• Growth/SEO/SEO Strategy.md — SEO approach and results
• Growth/LinkedIn/LinkedIn Strategy.md — LinkedIn approach and results