Back to corpus
research noteexperiment writeup candidatescore 36

cc-inscription: N'Ko Inscription System

A system that compiles embodied dynamics (z-trajectory) into justified N'Ko statements with cryptographic provenance. Every inscription is traceable to its source evidence through a typed IR pipeline.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

A system that compiles embodied dynamics (z-trajectory) into justified N'Ko statements with cryptographic provenance. Every inscription is traceable to its source evidence through a typed IR pipeline. - [Overview](#overview) - [Design Philosophy](#design-philosophy) - [Architecture](#architecture) - [The Ten Claim Types](#the-ten-claim-types) - [Core Types](#core-types) - [Basin Lifecycle](#basin-lifecycle) - [Lexicon Versioning](#lexicon-versioning) - [Surface Rendering](#surface-rendering) - [Phrase Emergence](#phrase-emergence) - [Integration Points](#integration-points) - [API Reference](#api-reference) - [Examples](#examples) The N'Ko Inscription System transforms continuous motion data (z-trajectory from DELL - Distributed Embodied Latent Learner) into discrete, justified claims expressed in N'Ko script. Each claim: 1. **Has typed structure** - A strongly-typed Intermediate Representation (IR) 2. **Has a sigil** - A single N'Ko character that identifies the claim type 3. **Is traceable** - Links back to the evidence that produced it 4. **Is versioned** - Rendered through a versioned lexicon N'Ko is a right-to-left African script with rich typographic potential. We use it as a **controlled technical register** where single characters (sigils) serve as operator markers. This keeps the system deterministic and learnable while opening the door to natural-language phrasing as the lexicon matures.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.