Back to corpus
research noteexperiment writeup candidatescore 18

N'Ko Inscription System — Design Document

The N'Ko Inscription System compiles embodied dynamics (z-trajectory from DELL) into justified N'Ko statements with cryptographic provenance. Every inscription is traceable to its source evidence through a typed IR pipeline.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

The N'Ko Inscription System compiles embodied dynamics (z-trajectory from DELL) into justified N'Ko statements with cryptographic provenance. Every inscription is traceable to its source evidence through a typed IR pipeline. **Design Principle**: The N'Ko surface is a *controlled technical register* using sigils (single N'Ko characters) as operator markers. This keeps the system deterministic and learnable. Natural-language N'Ko phrasing can be layered on later once the lexicon is settled by usage. Each claim has: a typed IR structure, a canonical N'Ko line form, and a specific sigil. | # | Name | Sigil | IR Type | What It Detects | |---|------|-------|---------|-----------------| | 1 | Stabilization | ߛ | `StabilizeClaim` | Dispersion decreased measurably | | 2 | Dispersion | ߜ | `DisperseClaim` | Spread/entropy increased | | 3 | Transition | ߕ | `TransitionClaim` | Discrete change point (curvature spike) | | 4 | Return | ߙ | `ReturnClaim` | Re-entry to known basin | | 5 | Dwell | ߡ | `DwellClaim` | Sustained stay in basin | | 6 | Oscillation | ߚ | `OscillateClaim` | Rapid alternation between basins | | 7 | Recovery | ߞ | `RecoverClaim` | Latency to return after disruption | | 8 | Novelty | ߣ | `NovelClaim` | New basin discovery | | 9 | Place-Shift | ߠ | `PlaceShiftClaim` | Location class change coupled to dynamics | | 10 | Echo | ߥ | `EchoClaim` | Pattern match to prior episode | Basins are **hypotheses the machine bets its consistency on**. Each basin has an origin, stability phase, possible refinement, and eventual persistence or retirement.

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.