# KDNA RFC Index

KDNA is an open protocol. Protocol-level changes should be proposed as RFCs
before they affect the asset format, Registry trust model, runtime contract, or
quality governance.

Current initial RFC set:

- [RFC-0001: KDNA Asset Format](./RFC-0001-kdna-asset-format.md)
- [RFC-0002: Registry Trust Model](./RFC-0002-registry-trust-model.md)
- [RFC-0003: Domain Quality Badges](./RFC-0003-domain-quality-badges.md)
- [RFC-0004: Runtime Loading Contract](./RFC-0004-runtime-loading-contract.md)
- [RFC-0005: Composition Policy](./RFC-0005-composition-policy.md)
- [RFC-0006: Provenance, Signing, and Transparency](./RFC-0006-provenance-signing-transparency.md)
- [RFC-0007: Canonical Authoring and Asset Build Pipeline](./RFC-0007-canonical-authoring-build-pipeline.md)
- [RFC-0008: Encrypted and Licensed KDNA Assets](./RFC-0008-encrypted-licensed-kdna-assets.md)
- [RFC-0009: Password-Protected KDNA Assets](./RFC-0009-password-protected-kdna-assets.md)
- [RFC-0010: KDNA Fidelity Protocol](../specs/fidelity-protocol.md)
- [RFC-0011: KDNA Product Runtime](../docs/product-runtime.md)
- [RFC-0012: KDNA Artifact Contract](../specs/RFC-0012-artifact-contract.md)

## RFC States

- `draft` — proposed, not binding.
- `accepted` — approved for implementation.
- `active` — implemented and part of the current contract.
- `superseded` — replaced by a newer RFC.
- `withdrawn` — intentionally abandoned.

## Required Sections

Every RFC should include: summary, motivation, normative rules,
compatibility impact, conformance requirements, security considerations, and
open questions.
