23 lines
992 B
Markdown
23 lines
992 B
Markdown
# Repository Inventory and Map
|
|
|
|
Build an evidence-based inventory of applications, services, packages, data stores, deployment assets and key relationships without changing the repository.
|
|
|
|
## Purpose
|
|
|
|
This is a publishable P0 built-in DevRunbook package. It is designed for the `inspect` work mode with default autonomy `diagnose` and risk tier `low`.
|
|
|
|
## Required context
|
|
|
|
- Target scope: Describe the repository areas, modules or boundaries that should be included.
|
|
- Desired depth: Choose how deeply the playbook should investigate the selected scope.
|
|
|
|
## Completion
|
|
|
|
- Repository structure and major components are mapped with evidence paths.
|
|
- Unknowns and conflicting evidence are reported separately.
|
|
- Validation evidence and unresolved limitations are reported honestly.
|
|
|
|
## Quality status
|
|
|
|
Editorially reviewed and covered by static structure and determinism fixtures. It is not represented as execution-validated or battle-tested until the platform stores corresponding evidence.
|