SOP-MKT-knowledge-curation-cadence-v1.0

1. Purpose

Define how knowledge produced by agents — research, frameworks, case studies, competitive intel, best practices — is captured, reviewed, canonized, and made accessible to all agents via the vault knowledge base. Prevents good work from dying in session artifacts.

2. Knowledge Types and Destinations

Type	Source agents	Destination in vault
Research artifacts (market, competitor, ICP)	category.positioning, financial.research	knowledge/research/synthesized/ (after council review)
Frameworks and IP	CEO, category.positioning, revenue.os	knowledge/ip/frameworks/
Best practices	Any agent — learned from session experience	knowledge/best-practices/
Tool / platform guides	code.platform, security.ops, documentation.engineering	knowledge/tools/ or knowledge/platforms/
Decision records	chief.staff, CDO, COO	knowledge/decisions/DR-{YYYY}-{N}-{slug}.md
Client intel	customer.success, sales.ops	knowledge/intel/client/
Competitive intel	category.positioning, financial.research	knowledge/intel/ (after council review)

3. Curation Cadence

Weekly (documentation.engineering)

At the end of each week, documentation.engineering runs a knowledge sweep:

1. Scan completed work artifacts — check closed Mission workspaces, completed Status Reports, and agent session dirs for knowledge-grade content (research outputs, frameworks, learned patterns, decision records)
2. Flag candidates — anything that would help another agent in a future session: tool guides, framework explanations, ICP insights, architectural decisions
3. Route to the correct vault path — see Section 2 destination table
4. For research artifacts: check if council review is required before canonizing (per SOP-EXEC-council-review-v1.0 Trigger Row 1 — research → canonical requires council review). If yes, route to chief.staff before moving to synthesized/

Monthly (chief.staff)

Monthly, chief.staff reviews the knowledge base for:

1. Stale content — articles or guides referencing deprecated tools, retired agents, or superseded workflows
2. Gap identification — areas where agents repeatedly ask the same questions but no canonical answer exists
3. Archive candidates — content that was correct but is now outdated; move to archive/knowledge/ with a deprecation note

4. Canonization Gate (research → synthesized)

Research moves from knowledge/research/active/ to knowledge/research/synthesized/ only after:

1. Council review per SOP-EXEC-council-review-v1.0 — MEDIUM sensitivity minimum (external APIs acceptable for research content)
2. Authoring agent signs off on the synthesized version
3. CDO or CMO acknowledges depending on whether the research is product-focused or market-focused
4. documentation.engineering updates knowledge/research/INDEX.md with the move

Active research that is abandoned (author moved on, project cancelled) goes to knowledge/research/queue/ for potential pickup, not synthesized. Never auto-canonize abandoned research.

5. Decision Record Standard

Decision records (DRs) are filed when: - An architectural or governance decision is made that will constrain future choices - A design option was explicitly rejected — future agents need to know why - A process or tool is adopted organizationally

DR format: knowledge/decisions/DR-{YYYY}-{NN}-{kebab-slug}.md

---
dr_id: DR-{YYYY}-{NN}
title: {decision title}
date: {YYYY-MM-DD}
decision_maker: {CEO / exec}
status: Active | Superseded | Revoked
---

## Context
{Why this decision was needed}

## Decision
{What was decided}

## Alternatives considered
{What was rejected and why}

## Consequences
{What this constrains or enables going forward}

documentation.engineering maintains knowledge/decisions/INDEX.md with all active DRs.

6. Knowledge Accessibility

All curated knowledge in knowledge/ is published to the MkDocs site per SOP-DEV-mkdocs-publication-v1.0, making it accessible to all agents without having to search the vault directly.

documentation.engineering confirms each weekly sweep addition is reflected in site navigation (mkdocs.yml) if navigation needs updating.

---

Change Log

Version	Date	Change
v1.0	2026-04-21	Initial draft — sop.manager.

---

Owner: documentation.engineering Executive sponsor: cdo Drafted by: sop.manager Status: Draft — pending CDO review + approval Version: v1.0