skills/architecture-author/references/homes.md

# Choosing a home

Where new architecture docs go, and how to check they will be found. The places
themselves — what each is for, how to reach it, what it cannot show you — are owned by
the `architecture` skill's where-docs-live reference. Read that before choosing.

## The existing corpus wins

1. **An existing architecture corpus wins.** New docs join it, matching its layout and
   its FORMAT.md if it carries one.
2. **Otherwise default to the plugin** — it is the one home every agent can reach
   without anything else being connected.
3. **Where the existing corpus lives somewhere else**, put the depth there and put an
   index entry and a summary in the plugin. Both, not either: depth where the team
   already keeps it, discoverability where every agent will look.
4. **Where what you are writing falls outside what this skill's guidance covers**, ask
   the user rather than choosing. A home chosen by guessing is one nobody maintains.

Then check it will be found: say which places will surface the new docs, and for a repo
home say whether that repo is connected — if it is not, the docs reach people with a
checkout and no one else. A test the user can run beats a claim: after the next sync,
searching the document index for a distinctive identifier from the doc should return it.