# . (index)
dir: .

## Project Map Protocol

1. Read this protocol and the root `.pi-map.index.md` first.
2. Use `index:` / `map:` references to open relevant directory indexes and maps.
3. Load indexes before rich maps during task-start navigation.
4. Read the local rich map and actual source before editing.
5. Treat non-empty `## dirty` sections in either artifact as stale.
6. If source and generated artifacts disagree, trust source.
7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
8. After editing source, run `project_map_patch` for each changed file.
9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.

Trust boundary: index routes, map orients, source decides.

## role
Defines a living documentation methodology and project configuration for managing software requirements, specifications, and development discipline rules within a Docker-based coding agent platform.
## parent
-
## children
- changes
  index: changes/.pi-map.index.md
  map: changes/.pi-map.md
- designs
  index: designs/.pi-map.index.md
  map: designs/.pi-map.md
- docs
  index: docs/.pi-map.index.md
  map: docs/.pi-map.md
- explorations
  index: explorations/.pi-map.index.md
  map: explorations/.pi-map.md
- proposals
  index: proposals/.pi-map.index.md
  map: proposals/.pi-map.md
- specs
  index: specs/.pi-map.index.md
  map: specs/.pi-map.md
- tasks
  index: tasks/.pi-map.index.md
  map: tasks/.pi-map.md
## files
- README.md
- config.yaml
## links
index: ./.pi-map.index.md
map: ./.pi-map.md
## workflows
-
## dirty
-