# <Troubleshooting Title>

ID: knowledge:<keyword-rich-slug>
Type: Knowledge Troubleshooting
Status: active
Created: <YYYY-MM-DD>
Updated: <YYYY-MM-DD>
Triggers: <error text, symptoms, commands, tools, feature names, task words>
Applies To: <optional paths, tools, systems, environments, or remove>

## Symptom

<What future agents might observe or search for.>

## Likely Causes

<Current likely causes or diagnostic branches.>

## Checks

<How to narrow the issue. Include commands, files, records, or observations when
useful.>

## Fix Or Route

<Known fixes, records to update, or when to create tickets, evidence, research,
audit, or ask the operator.>

## Boundaries Or Sources

<Optional. Name versions, source records, evidence, or limits when useful. Remove
when not useful.>

## Related Records

<Optional. Add records or paths that help future agents troubleshoot. Remove when
none are useful.>

- <record-id or path> - <why it matters>
