ADR And RFC Policy

Every substantive 0x0 change must include both:

• an ADR in docs/adrs/ADR-NNNN-title.html;
• an RFC in docs/rfcs/RFC-NNNN-title.html.

The ADR records the decision that future maintainers must respect. The RFC

records the proposed design, alternatives, and acceptance evidence.

Every behavior-affecting change must also include a documentation impact review

inside the changed ADR/RFC records. The review lists updated documentation or

explains why no documentation update was required.

Use the templates:

• docs/adrs/ADR_TEMPLATE.html;
• docs/rfcs/RFC_TEMPLATE.html.

Run:

make adr-rfc-check
make documentation-impact-check

The check uses staged files during commits. If no files are staged, it checks

tracked and untracked working-tree changes. CI can set ADR_RFC_BASE_REF to

check a branch range.

Generated metadata and build outputs are ignored, but source, docs, tools,

runtime, package, app, and release changes all require both records.

See docs/documentation-impact-review.html for the documentation-impact standard.