Topics are now notes in Driftless

Driftless topics used to be rigid forms: fill in what, how, gotchas, decisions. It worked, but it forced teams to think in our structure, not theirs.

Today, topics are markdown notes. Write anything. Use YAML frontmatter for tags and metadata. Structure it your way — ADR, roadmap, runbook, or freeform.

Why notes, not forms

Teams do not think in forms. They think in notes, documents, ADRs, and roadmaps. A form creates friction. A note invites writing.

The old fields (what, how, gotchas, decisions) still work for backward compatibility. But the new content field lets you write in the format that matches how your team actually communicates.

What changed

• content: Full markdown with optional YAML frontmatter
• tags: Freeform labels for filtering and discovery
• kind: Typed classification (decision, roadmap, runbook, code-context, domain-map...)

All existing topics keep working. New topics can use either the old fields or the new content field — the API handles both.

How to use it

driftless context add "auth-decision" \
  --content "# Auth Provider Decision\n\nWe chose Clerk because..." \
  --kind decision \
  --tags architecture,auth

Or write it in a file and use --content @docs/auth.md.

Context that fits your workflow, not the other way around.