Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

RFC proposals

Hees.ai uses RFCs to review public contracts before implementation. A Draft describes proposed behavior only: it is not part of the checked 0.0.1 API. Until an RFC and its implementation are merged, Contracts and src/lib.incn remain the source of truth for supported behavior.

The RFC set is deliberately coupled. RFC 000 defines the foundational authority model; RFC 001 and RFC 002 establish Spectrum and Content DNA as core contracts; RFC 003–009 refine governed memory, constraints, packages, receipts, verifier findings, behavior selection, and visible-response governance; RFC 010 proposes a permanent hees.ai console with one deliberately bounded profile; and RFC 011 defines canonical structural identity for validated Incan models. RFCs 003–005, 007–009, and 011 are Planned: together they define governed memory, deterministic constraint composition, closed Package admission, evidence-grounded verifier findings, behavior selection, visible-response governance, and the separation of exact artifact integrity from semantic authority identity. None transfers runtime authority to a model, provider, serializer, or storage engine.

RFCProposalStatus
000: Foundational governance authority#1Draft
001: Spectrum terminal adjudication#2Draft
002: Content DNA answer-time provenance#3Draft
003: Governed memory and retrieval results#4Planned
004: Composable governance constraints#5Planned
005: Canonical package artifact admission#6Planned
006: Export-safe governance receipts#7Draft
007: Evidence-grounded claim verification findings#8Planned
008: Governed behavior envelopes#9Planned
009: Governed visible response lifecycle#11Planned
010: hees.ai console#14Draft
011: Canonical structural identity for Incan models#18Planned

See the RFC process and lifecycle for the status definitions and publication boundary.