# References

## Source of truth

| Source | Type | Owner | Last checked | Notes |
|--------|------|-------|--------------|-------|
| {{SOURCE_1}} | {{TYPE_1}} | {{OWNER_1}} | {{CHECKED_1}} | {{NOTES_1}} |

## Canonical terminology

Use this table when `/scr:discuss` or `/scr:plan` resolves a term through domain grilling. Keep entries short enough to load during planning and review.

| Term | Preferred wording | Avoid | Boundary or example | Source of truth | Reason |
|------|-------------------|-------|---------------------|-----------------|--------|
| {{TERM_1}} | {{PREFERRED_1}} | {{AVOID_1}} | {{BOUNDARY_1}} | {{SOURCE_1}} | {{REASON_1}} |

## Domain boundaries

Use this section for terms, procedures, or system behaviors that are easy to confuse.

| Boundary | This means | This does not mean | Example check |
|----------|------------|--------------------|---------------|
| {{BOUNDARY_NAME}} | {{MEANS}} | {{DOES_NOT_MEAN}} | {{EXAMPLE_CHECK}} |

## Examples to keep current

{{EXAMPLES}}

## Review checklist

- Command or procedure steps match current behavior: {{CHECK_BEHAVIOR}}
- Version references are explicit: {{CHECK_VERSION}}
- Audience assumptions are still valid: {{CHECK_AUDIENCE}}
- Links and paths are still correct: {{CHECK_LINKS}}
- Canonical terminology matches the terms used in drafts and plans: {{CHECK_TERMS}}
- Domain boundaries still match current behavior and recovery paths: {{CHECK_BOUNDARIES}}