27 lines
811 B
Markdown
27 lines
811 B
Markdown
# Domain Docs
|
||
|
||
How engineering skills should consume this repository’s domain documentation.
|
||
|
||
## Layout
|
||
|
||
This is a single-context repository:
|
||
|
||
```text
|
||
/
|
||
├── CONTEXT.md
|
||
├── docs/adr/
|
||
└── ...
|
||
```
|
||
|
||
## Before exploring
|
||
|
||
Read `CONTEXT.md` and relevant ADRs under `docs/adr/` when they exist. If they do not exist, proceed silently. Domain-modeling skills create them lazily when terminology or durable architectural decisions are resolved.
|
||
|
||
## Use the glossary’s vocabulary
|
||
|
||
Use terminology defined in `CONTEXT.md` consistently. If required terminology is missing or contradictory, raise it through domain modeling rather than silently inventing synonyms.
|
||
|
||
## Flag ADR conflicts
|
||
|
||
If proposed work contradicts an existing ADR, identify the conflict explicitly instead of silently overriding it.
|