FoldKernel

Protocol infrastructure · FoldKernel 1.0.0

A stable beginning
for systems that change.

FoldKernel turns structured interaction into reproducible identity. It preserves origin while applications, instruments, archives, and material systems evolve above it.

The invariant

Identical histories produce identical artifacts.

  1. 01Interaction
  2. 02Permutation events
  3. 03Memory signature
  4. 04Convergence hash

Begin a project

Start with one state you need to remain verifiable.

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.

01

Read the contract

Understand validation order, canonical bytes, transformations, invariants, and Keccak construction.

Protocol specification
02

Run the reference

Generate a memory signature and convergence hash locally with no account, network call, or timestamp.

Developer preview
03

Verify conformance

Reproduce all fifteen canonical vectors before declaring another implementation compatible.

Integration contract

Authority boundary

The kernel does less
so the system can do more.

FoldKernel contains no interface, rendering system, application logic, randomness, custody, or claim to the meaning of a work.

FoldForge, FoldPortrait, Root Logos, Sovereign Standard, and Telos use the same substrate without surrendering their own authority. New projects may begin here and remain themselves.