# <Atlas Title>

ID: knowledge:<keyword-rich-slug>
Type: Knowledge Atlas
Status: active
Created: <YYYY-MM-DD>
Updated: <YYYY-MM-DD>
Triggers: <area names, modules, packages, paths, systems, task words>
Applies To: <paths, modules, services, packages, or domains>

## Summary

<What area this atlas maps and why future agents should read it.>

## Major Areas

<Important directories, modules, services, packages, or responsibilities.>

## Entry Points

<Files, commands, APIs, records, or workflows that future agents commonly need.>

## Validation And Risk

<Relevant checks, risky areas, coupling, generated files, persistence boundaries,
or audit/evidence expectations.>

## Boundaries Or Sources

<Optional. Name source records, last inspection context, or limits when useful.
Remove when not useful.>

## Related Records

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

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