🌳 trigger-tree — documentation health

Example report — generated from synthetic demo data so you can see the full format. Real reports are produced locally by /tt insights and never leave your machine.

Period 2026-08-01T09:00:00Z → 2026-08-21T15:21:00Z (20.26 days) · maturity: mature

Current inventory: 12 files = 11 evaluable + 1 always loaded. Evaluable coverage reconciles as 9 touched + 2 untouched = 11.

a rule that is never read protects nothing — use the evidence below to improve routes, not to confuse discovery with understanding. Glossary.

Instruction adherence

Did the instructions change what happened? Each rate comes from deterministic, per-session evidence. Unobserved means evidence was not captured; it does not mean violated.

Token counts are estimates at four characters per token. Never-triggered is a review prompt, not a removal recommendation.

Agent personas

A persona's name and description sit in the system prompt on each request; the body is paid only when the agent runs, so the two are counted separately. A persona that is never invoked is recurring cost. Never-invoked is a review prompt, not a removal recommendation.

Never invoked: release-manager. Worth reviewing.

Current heat

The same indented tree used by the live dashboard: color shows last-read recency, while bar length and h show decayed attention volume. Untouched files collapse to a · summary.

Color is time since last read: hot ≤1 day, warm ≤3 days, active ≤7 days, cool ≤30 days, cold >30 days. Heat is attention volume with a 30-day half-life; lifetime reads never decay. Cold means inactive now, not unimportant.

Folder heat & cold map

Folder color follows its most recently read current file; folder heat still sums decayed attention volume. Coverage and lifetime reads remain separate; cold means inactive now and never proves removal is safe.

Untouched review

Never read during the measurement period. This is a review queue, not a removal recommendation.

Low reads can mean rare-but-critical; verify purpose and owners before archiving.

Out of scope (always loaded via system prompt / Skill tool): CLAUDE.md

Unread routers: docs/operations/index.md. Router files are never classified as templates.

Trend

Search/read ratio per period. Movement after a note is correlation, not proof that the recorded edit caused it.

Movement after a note is correlation, not proof that the recorded edit caused it.

Notes (router changes & annotations)

• 2026-08-12T12:00:00Z — sharpened the design router

Search activity inside doc folders

A search event records explicit search activity, not its cause. Concentrated bursts may be intentional bulk work; distributed recurrence can support, but does not prove, a routing hypothesis.

Task clusters

Doc-and-skill sets per prompt, grouped by similarity (Jaccard ≥ 0.6) across sessions.

Folder-router coverage

Unlisted means absent from that folder's existing README.md, _index.md, index.md, or CLAUDE.md; links elsewhere do not count as folder-router reachability.

Most often read together