# <Entity Title>

ID: knowledge:<keyword-rich-slug>
Type: Knowledge Entity
Status: active
Created: <YYYY-MM-DD>
Updated: <YYYY-MM-DD>
Triggers: <entity name, aliases, services, packages, tools, people, topic words>
Applies To: <optional domains, paths, workflows, or remove>

## Summary

<Compact description of the recurring entity and why it matters for retrieval.>

## Aliases Or Search Terms

<Names, abbreviations, nearby terms, package names, services, or labels future
agents may search.>

## Useful Context

<Current facts that help orientation without overclaiming the entity note's scope.>

## Boundaries Or Sources

<Optional. Name related records, code paths, source context, or limits when useful.
Remove when not useful.>

## Related Records

<Optional. Add records or paths that help future agents orient around this entity.
Remove when none are useful.>

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