Artifacts
Everything the system produces lives here, organized by type.
Artifact Types
Each subfolder holds a specific type of output. Three hub files live at the root:Artifacts.md(index), Content Calendar.md, and Content Pipeline.md. Everything else goes in a subfolder.
| Subfolder | What It Holds |
|---|---|
| article-ideas/ | Pre-draft concepts. Ideas that might become articles but are not ready yet. |
| articles/ | Published blog posts and thought leadership content. |
| briefs/ | Product briefs, strategy briefs, and research briefs. |
| page-copy/ | Website copy, landing pages, and feature pages. |
| plans/ | Implementation plans, specs, and architecture docs. |
| presentations/ | Slide decks, pitch decks, and PowerPoints. |
| spreadsheets/ | Excel docs, data analysis, and reports. |
The Content Pipeline
Two files manage the flow of content from idea to published:
- Content Calendar.md tracks what to write and when. The editorial schedule.
- Content Pipeline.md is a Kanban board that moves articles through stages: draft, review, published.
Loom, the Creative Director agent, owns this pipeline. Loom drafts content, manages the editorial calendar, and ensures brand voice consistency across everything produced.
Publishing Route
Content goes from draft to live in three steps. No shortcuts.
- Human approves the draft in the content pipeline
/distributecreates platform-native versions for LinkedIn, X threads, and X posts/publishpushes the article to Webflow and schedules social posts via Postiz
Where Strategy Docs Live
Strategy docs belong with their project, not in artifacts. If you are writing a marketing strategy for Agent0, it lives in projects/agent0-markops-app/, not in artifacts/plans/.
Cross-project plans that span multiple projects go in artifacts/plans/. This is the exception, not the rule.
This prevents orphaned strategy docs. When a strategy lives inside its project folder, it stays connected to the work it describes. When it lives in a generic plans folder, it gets forgotten.