Setting the file. One moment.
Subchapter 7.50
references/support-topics/README.mdMarkdown2 KBView on GitHub
Support topics are small, candidate-scoped investigation guardrails injected into sub-agent briefs.
They are not recommendations, gates, scanners, or broad documentation. A topic tells the investigator what evidence to check, what false positives to avoid, and when to abstain for one class of candidate.
Add one file: references/support-topics/<id>.md.
The filename must match the id. Frontmatter uses a strict subset of YAML: one key: value per line, arrays as JSON arrays.
---
id: cdn-cache-auth-safety
title: CDN cache auth safety
status: active
candidateKinds: ["uncached_route", "cache_header_gap"]
frameworks: ["*"]
priority: 90
citations: ["https://vercel.com/docs/caching/cdn-cache"]
maxBriefChars: 900
---
## Investigation Brief
...
## Evidence To Check
...
## Do Not Recommend When
...
## Verification
...references/docs-library.json.candidateKinds to keep the topic narrow. Use "*" only for workflow/protocol topics that truly apply to every candidate.metrics only when a topic applies to a specific candidate metric, such as ["LCP"], ["INP"], or ["CLS"] for Core Web Vitals.routePatterns as JavaScript regex source strings when a topic should appear only for specific candidate routes, such as ["(^|/)404$"].maxBriefChars; the brief renderer caps selected topics before they reach the sub-agent.