Themes

Some ideas don't belong to one initiative — they run through several, across collections. Tag the initiatives, and optionally give the theme an overview document.

Tags

tags: [notifications, accessibility]

Tags are lowercase kebab-case. A collection can declare the tags it expects, with descriptions, so typos are caught:

# collection README front-matter
tags:
  notifications: Telling captains about changes to their slots

Theme overview docs

A non-numbered Markdown file in a collection folder becomes the theme's overview when its front-matter names the tag:

---
theme: notifications
summary: How captains hear about changes
icon: 🔔
---
# Notifications — orientation map

Brindley then:

• keeps a generated list in the doc of every initiative tagged notifications, in any collection, with status and readiness — your prose is left alone;
• points to the doc from get, tags, the overview and the briefs, so an agent working on a tagged initiative reads it first.

Ask "show me everything in the notifications theme" to get the overview plus every member as one document.

Themes in the collection README

A collection's README lists the themes its initiatives use, each linked to its overview doc where there is one, with its description and how many of the collection's initiatives are open and closed.

Themes in the dependency graph

A collection can show themes in its README graph with graph: { themes: … }:

• icon — each initiative's theme icons (the doc's icon:, or [name] without one) before its title, with a legend under the graph;
• label — the theme names after its title;
• box — initiatives grouped in a box for their first theme; combine it with icon or label (themes: [box, icon]) so initiatives with several themes still show them all.

See Graph settings.