ANN-DXENC RFC Draft v1.0.0 — Part II

PRIVATE AND PROPRIETARY. Owned by Kanjani AI Research & Causum. See NOTICE.md.

Digital DNA Encoding Specification

This section defines the canonical encoding, hashing rules, glyph semantics, structural layout, and validity constraints of the Digital DNA system. The encoding described herein is normative, and all compliant implementations MUST follow it exactly unless explicitly marked otherwise.

6. Digital DNA Structure

Every CSR MUST contain a digital_dna object in its root. This object represents the immutable genotype of the CSR and MUST NOT change after creation.

6.1 Canonical Structure

“digital_dna”: { “sense_glyphs”: { “affective”: “<glyph>”, “auditory”: “<glyph>”, “semantic”: “<glyph>”, “procedural”: “<glyph>”, “social”: “<glyph>”, “situational”: “<glyph>”, “visual_symbolic”: “<glyph>” }, “glyph_hash”: “<sha256>”, “manifold_code”: “<base64url>”, “birth_crc”: “<crc32c>”, “mutation_class”: “<enum>”, “vaccine_class”: “<enum>”}

6.2 Required Properties

Field	Description	Type	Requirement
sense_glyphs	7-sense perceptual glyphs	object	MUST
glyph_hash	hash of canonical glyph concatenation	string	MUST
manifold_code	compressed 7D embedding manifold	bytes (b64url)	MUST
birth_crc	CRC32C digest for integrity	string	MUST
mutation_class	mutation policy category	string	MUST
vaccine_class	vaccine immunity profile	string	MUST

6.3 Immutable Fields

The following MUST be immutable:

sense_glyphs.*
glyph_hash
birth_crc

Any modification permanently invalidates the CSR.

6.4 Sensory Glyph Requirements

Each glyph MUST be:

chosen from the Digital-Entity’s glyph dialect,
normalized to Unicode NFC form,
a single Unicode codepoint OR a single extended emoji sequence,
stable across all compliant implementations.

Glyphs MUST NOT encode metadata or text. They represent symbolic perceptual anchors, not semantic descriptors.

7. Canonical Glyph Encoding

7.1 Canonical Ordering

The canonical ordering of senses MUST be:

affective
auditory
semantic
procedural
social
situational
visual-symbolic

This ordering ensures deterministic hashing.

7.2 Concatenation Rules

The canonical glyph string is constructed as:

No separators are permitted. Whitespace is forbidden.

7.3 Hashing Mechanism

The glyph hash MUST be:

sha256( canonical_glyph_string )

Encoded as lowercase hex.

7.4 Example (Illustrative Only)

Glyphs:

affective = 😐

auditory = 🎵

semantic = ≈

procedural = ➤

social = ⇧

situational = 🕒

visual = 🌌

canonical_glyph_string = “😐🎵≈➤⇧🕒🌌”

glyph_hash = sha256(“😐🎵≈➤⇧🕒🌌”)

Implementations MUST ensure consistent Unicode handling.

8. Manifold Code Specification

The manifold_code describes a compressed representation of the CSR’s 7-dimensional perceptual vector space.

8.1 Generative Rules

The manifold vector MUST be:

generated using the Digital-Entity’s manifold parameters
projected through a stable 7D space
compressed using Zstd or Brotli (entity choice)
encoded using base64url without padding

8.2 Requirements

The manifold_code MUST:

remain constant for the lifetime of the CSR
be derivable independently (to enable verification)
match the Digital-Entity’s manifold specification version
fail validation if generated with incorrect key material

8.3 Purpose

The manifold code allows:

cross-plane coherence checks
poison detection (manifold drift)
reasoning-plane consistency scoring
vaccine-class evaluation

It is not intended to encode semantic content.

9. Birth CRC

The birth_crc is a CRC32C checksum over the CSR’s static fields at creation time.

9.1 CRC Input

The CRC MUST be computed over:

canonical_glyph_string + glyph_hash + manifold_code

in that order.

9.2 Purpose

The CRC provides:

tamper detection
fast integrity validation
early-plane anomaly detection
vaccine-class compatibility checks

If any input changes, the CRC becomes invalid and the CSR MUST be rejected.

10. Mutation Classes

Mutation classes define how the CSR is allowed to change across planes.

A CSR’s Digital DNA is immutable, but higher-level cognitive layers MAY accumulate additional information.

10.1 Allowed Mutation Classes

Mutation Class	Description	Allowed Plane Transitions
M0: Frozen	No mutations allowed	None
M1: Phenotypic Only	Reasoning-plane can attach derived cognition	Data → Reason
M2: Extended Reasoning	Both reasoning-plane and outcome-plane may aggregate cognition	Data → Reason → Outcome
M3: Delegated	External policies govern mutation behavior	Delegated

10.2 Normative Rules

M0 MUST be used for high-integrity records.
M1 SHOULD be the default for standard CSRs.
M2 MAY be used for knowledge-building systems.
M3 MUST reference a valid mutation-policy URI.

Mutation class determines phenotype stability.

11. Vaccine Classes

Vaccine classes define immune responses, i.e., how a CSR interacts with:

poisoned data
cross-tenant signals
drift detection
training/inference engines

11.1 Vaccine Profiles

Class	Behavior	Purpose
V0: None	No immune checks	Testing, sandboxing
V1: Local Consistency	Checks glyph + CRC	Basic poisoning protection
V2: Manifold Coherence	Validates local manifold + drift	Reasoning-plane safety
V3: Sovereign Immunity	Enforces tenant-bound DNA + vaccine dialect	Prevents cross-tenant contamination
V4: Full Immunological Response	Multi-layer evaluation (glyph, manifold, CRC, lineage)	Production-grade Cognitive Fabric

11.2 Rules

High-stakes CSRs MUST use V3 or V4.
Cross-tenant communication MUST enforce V3 at minimum.
V0 MAY be used only in isolated environments.

12. Validity Conditions

A CSR MUST satisfy:

All 7 glyphs present.
glyph_hash matches canonical string.
manifold_code decodes properly.
birth_crc validates.
mutation_class allowed by entity policy.
vaccine_class supported by entity immunology model.

If any condition fails, the CSR MUST be rejected.