ANN-DXENC RFC Draft v1.0.0 — Part VI
ANN-DXENC RFC Draft v1.0.0 — Part VI
PRIVATE AND PROPRIETARY. Owned by Kanjani AI Research & Causum. See NOTICE.md.
Registry and IANA Considerations
This section establishes the formal registries required to support Digital DNA, mutation classes, vaccine classes, glyph dialects, manifold specification versions, and policy URIs across the Cognitive Substrate ecosystem.
These registries MUST be controlled, authoritative, and cryptographically verifiable.
33. IANA Considerations Overview
IANA SHALL create and maintain a new registry category:
“CS2-DNA Registries”
The CS2-DNA registry family MUST contain the following sub-registries:
- Digital Sense Glyph Registry
- Mutation Class Registry
- Vaccine Class Registry
- Manifold Specification Registry
- Sovereign Dialect Registry
- Policy URI Registry
- CSR Status Code Registry
- Firebreak Event Registry
Each registry provides canonical values, compatibility rules, and designated expert review requirements.
34. Digital Sense Glyph Registry
34.1 Purpose
This registry defines the canonical glyphs, classifications, and Unicode normalization rules for the 7-sense system.
IANA SHALL maintain:
- canonical identifiers
- Unicode representations
- sense-to-glyph category mappings
- normalization rules
- reserved code points
34.2 Registry Fields
| Field | Description | Required |
|---|---|---|
| sense_name | One of the 7 senses | MUST |
| glyph_id | Stable identifier | MUST |
| unicode_value | NFC-normalized string | MUST |
| class | Basic or Extended | MUST |
| sovereign_override_allowed | Boolean | MUST |
34.3 Registration Policy
New glyphs MUST undergo:
- expert review
- dialect conflict resolution
- security analysis
- perceptual distinctiveness evaluation
Glyphs MUST NOT resemble other glyphs in a way that risks misclassification.
35. Mutation Class Registry
The registry MUST include:
| Class | Meaning | Allowed Planes |
|---|---|---|
| M0 | Immutable CSR | None |
| M1 | Reasoning-plane phenotype | Data → Reason |
| M2 | Extended reasoning & memory | Data → Reason → Outcome |
| M3 | Delegated mutation policy | Delegated |
35.1 Registration Rules
Mutation classes MUST:
- specify allowed transitions
- define legal phenotype operations
- specify immunological interactions
- reference a policy URI
New mutation classes MUST NOT conflict with existing ones.
36. Vaccine Class Registry
This registry defines allowable vaccine profiles.
36.1 Required Fields
| Field | Description |
|---|---|
| vaccine_id | Stable identifier |
| immunity_layers | Which immunological layers apply |
| firebreak_allowed | Boolean |
| sovereign_enforcement | Boolean |
| description | Human-readable |
36.2 Standard Classes (Mandatory)
The registry MUST include:
- V0: None
- V1: Genotypic
- V2: Genotypic + Manifold
- V3: Sovereign Immunity
- V4: Full Immunological Response
36.3 Registration Rules
IANA SHOULD reject vaccine classes that:
- permit unsafe cross-tenant interactions
- bypass genotype integrity
- disable firebreak mechanisms
37. Manifold Specification Registry
Manifold specifications define:
- dimensionality
- compression method
- hashing rules
- drift thresholds
- stability parameters
37.1 Registry Fields
| Field | Description |
|---|---|
| manifold_id | Unique ID |
| version | Semantic version |
| dimension | MUST be 7 |
| compression | zstd or brotli |
| topology | Graph or metric description |
| sovereign_binding | Keyed parameters |
A manifold implementation MUST be uniquely tied to:
- a sovereign entity
- a dialect signature
- a versioned specification
37.2 Registration Requirements
- MUST include full mathematical formulation
- MUST specify drift tolerance bands
- MUST document security properties
38. Sovereign Dialect Registry
This registry defines each Digital-Entity’s glyph dialect, which is the primary mechanism for cognitive sovereignty.
38.1 Dialect Structure
A dialect includes:
- a unique sovereign identifier
- glyph subset for each of the 7 senses
- sovereign hashing parameters
- sovereign manifold parameters
- sovereign vaccine definitions
38.2 Registration Policy
Dialects MUST:
- be unique
- be cryptographically bound to sovereign keys
- never overlap in ways that cause ambiguity
New sovereign dialects MUST undergo:
- expert review
- security analysis
- collision detection
- compatibility verification
39. Policy URI Registry
Mutation and vaccine classes often refer to external policy URIs.
39.1 Requirements for Policy URIs
A Policy URI MUST:
- be stable
- be cryptographically integrity-protected (hash or signature)
- describe governance rules
- include contact/regulatory information
- specify override behavior
39.2 Registration
Policy URIs MUST NOT:
- be ephemeral
- depend on runtime state
- contain executable logic
40. CSR Status Code Registry
This registry defines canonical status codes used in CSR lifecycle transitions.
40.1 Standard Status Codes
| Code | Meaning |
|---|---|
| 0 | Valid |
| 1 | Invalid DNA |
| 2 | CRC mismatch |
| 3 | Manifold drift |
| 4 | Sovereignty violation |
| 5 | Vaccine rejection |
| 6 | Quarantined |
| 7 | Firebreak activated |
| 8 | Memory-eligible |
| 9 | Memory-rejected |
41. Firebreak Event Registry
41.1 Purpose
Defines standardized identifiers for firebreak activation events.
41.2 Standard Entries
| Event ID | Trigger |
|---|---|
| FB-01 | Manifold drift threshold exceeded |
| FB-02 | Sovereign mismatch |
| FB-03 | Coordinated anomaly cluster detected |
| FB-04 | Phenotype collapse |
| FB-05 | Cross-tenant attempt detected |
| FB-06 | Repeated mutation-policy violation |
41.3 Registration Criteria
New entries MUST:
- be globally unique
- represent a systemic-level threat
- be actionable
- be recognized by all fabric governance modules
42. Registry Governance Requirements
IANA MUST:
- ensure registry availability
- digitally sign registry contents
- publish registry updates via secure channels
- allow expert review
- maintain backward compatibility
Implementations MUST:
- validate registry contents cryptographically
- refuse unverifiable registry updates
- log registry-based decisions immutably