---
id: domain.slug                    # <domain prefix>.<slug>, unique, never reused (prefixes: schemas/knowledge-item.schema.json)
title: Title in sentence case
kind: standard                     # standard | practice | checklist | concept | tutorial | term | playbook
domain: architecture               # SWEBOK v4 knowledge area
description: One sentence (20–300 characters) for search, SEO and agent discovery.
version: 0.1.0                     # item SemVer: MAJOR new/stricter MUST, MINOR new item or SHOULD, PATCH wording
status: draft                      # draft | review | approved | published | deprecated
applies_to: [core]                 # core, or profile names
extends: ~                         # profile items only: the core item id they specialise
sources:                           # at least one for standard, practice, checklist
  - title: Name of the primary source
    url: https://example.org/spec
    license: CC-BY-4.0             # SPDX id; LicenseRef-All-Rights-Reserved if none; BY-SA only in content/adapted/
    accessed: 2026-01-01
standards: []                      # external standards by name, reference only
requires: []                       # item ids to understand or apply first
related: []                        # item ids
templates: []                      # paths such as templates/adr.md
skills: []                         # skill names in skills/
last_reviewed: 2026-01-01
review_every: 12                   # months
supersedes: ~
superseded_by: ~                   # required when status is deprecated
---

<!-- Template of a knowledge item. Use it when adding a new item under content/: copy it to content/<part>/<domain>/<slug>.md, replace every
value and delete this comment. The schema schemas/knowledge-item.schema.json and tools/validate_content.py decide what is valid. -->

## Summary

Two to four sentences: what this is and why it matters.

## Rules

- **R1.** One testable rule with an RFC 2119 keyword (MUST, MUST NOT, SHOULD, SHOULD NOT, MAY).
- **R2.** Rule ids are stable: never renumber; retire a rule by marking it "(removed in 2.0.0)".

## Guidance

Recommendations, trade-offs and when not to apply the rules. No upper-case keywords here.

## Explanation

Why the rules exist; background and history.

## Examples

A short good example and a short bad one.

## Sources

- [Name of the primary source](https://example.org/spec) — licence, what was used. Accessed 2026-01-01.
