Read the contract
Understand validation order, canonical bytes, transformations, invariants, and Keccak construction.
Protocol specificationProtocol infrastructure · FoldKernel 1.1
FoldKernel preserves structured relations as reproducible identity. Its outputs can condition grammar, form, and tone while applications, instruments, archives, and material systems retain authorship and evolve above it.
The invariant
Begin a project
The application owns meaning and history. FoldKernel owns canonical encoding and the resulting identity. The first implementation is Swift, but compatibility belongs to the byte contract—not the language.
Understand validation order, canonical bytes, transformations, invariants, and Keccak construction.
Protocol specificationGenerate a memory signature and convergence hash locally with no account, network call, or timestamp.
Developer previewReproduce all fifteen canonical vectors before declaring another implementation compatible.
Integration contractAuthority boundary
FoldKernel contains no interface, rendering system, application logic, randomness, custody, or claim to the meaning or authorship of a work.
Root Logos demonstrates the distinction clearly: it reads fragments and encounters, FoldKernel preserves their structural history and derives deterministic relation weights, and those weights condition a grammar through which Root Logos writes. Sound is another derived expression of the same structure, not the source of the writing.
Sovereign Standard uses the same relational contract to condition its Sigil Engine. The vessel, provenance, and resulting mark remain Sovereign Standard's work; FoldKernel makes their admitted relations reproducible.
FoldForge, FoldPortrait, Root Logos, Sovereign Standard, The Record, and Telos use the substrate without surrendering their own authority. Their works can reveal new capacities of FoldKernel and refine how it is understood; they do not silently rewrite its versioned contract. New projects may begin here and remain themselves.