OfOne Skillchain

What It Is

OfOne is a Codex skillchain and repository toolchain for representing bounded inquiry as typed, auditable, patchable state. The public answer is only a rendering of the map.

Decision-state intermediate representation

Charters, evidence, claims, unknowns, criteria, tradeoffs, edges, loops, gates, triggers, and renderings live as addressable objects.

Geometry

Abstract structure before domain language

Scenes, frames, tokens, moves, loops, invariants, and gates are the base. Adapters project domain semantics onto that base.

Compiler

Validate, render, patch, review

The toolchain checks schema and semantic validity, renders human views, computes patch impact, and preserves benchmark boundaries.

objective -> adapter projection -> typed geometry -> object graph -> validation -> rendering -> patch closure -> review or benchmark

How To Operate It

Use OfOne when the cost of hidden assumptions is higher than the cost of mapping. Do not use it for simple answers, casual explanations, or high-stakes advice without human review.

Step 01

Write a bounded charter

Name the decision, scope, criteria, stakes, time horizon, and what would count as a useful output.

charter

Step 02

Project the domain into geometry

Select or mix adapters, then represent the problem as scenes, frames, tokens, moves, loops, and gates.

adapter + scene

Step 03

Separate evidence from claims

Evidence carries source identity and risks. Claims stay atomic, typed, supported, contradicted, or disputed.

evidence + claims

Step 04

Build the decision surface

Connect options to criteria, tradeoffs, unknowns, stakeholders, temporal validity, and information value.

criteria + tradeoffs

Step 05

Validate before release

Run schema and semantic checks. Unsupported claims, illegal edges, missing gates, and stale dependencies block confidence.

validator_result

Step 06

Render, patch, and benchmark

Render the answer for the audience. When evidence changes, patch the affected closure. Benchmark before claiming superiority.

decision pack

Public audit index for Pages parity, benchmark traceability, Launch Proof, and Research Watchdog evidence

Visual Walkthrough

The hyperframe is a frame-by-frame visual grammar for the Remotion walkthrough. It shows the inquiry moving from raw objective to validated rendering and then into patchable lifecycle state.

Frame 01Objective EntersA messy question is bounded into a charter.

Frame 02Geometry KernelThe scene gains frames, tokens, moves, edges, loops, and gates.

Frame 03Adapter ProjectionDomain language is mapped into the primitive geometry.

Frame 04Evidence LedgerSources become traceable evidence objects with identity and risk.

Frame 05Claim GraphClaims become atomic, supported, disputed, or killed.

Frame 06Loops And GatesFeedback, temporal validity, and human review blocks become explicit.

Frame 07ValidatorThe compiler rejects unsupported, unsafe, or malformed state.

Frame 08RenderingThe user sees a decision view, not raw graph noise.

Frame 09Patch ClosureNew evidence updates only affected dependencies.

Frame 10Benchmark BoundaryClaims of superiority wait for controlled comparison.

Hyperframe JSON Remotion cue data Voiceover script

Compiler Contract

OfOne is not done when it produces an impressive answer. It is done for a cycle when the artifact validates, renders, patches, and preserves the benchmark boundary.

Validate

Schema plus semantic checks

Profiles, closed object definitions, movement jobs, references, adapter contracts, edge legality, gates, triggers, and review sidecars are checked.

Render

Answer as projection

Executive, Analyst, Audit, and Patch Impact views compress the map for a human without pretending the rendering is the full state.

Patch

Incremental update discipline

Changed evidence or claims propagate through closure to affected options, gates, renderings, and benchmark eligibility.

npm run schema:check
npm run validate
npm run render -- examples/source-backed-wastewater-map.json Map
npm run patch -- examples/source-backed-wastewater-map.json E1
npm run benchmark
npm test

Current Boundary

OfOne has not reached a terminal state where no more improvement is possible. The current loop state is benchmark handoff: broad architecture iteration pauses while the system proves workflow value through controlled benchmark slices.

Done This Cycle

Architecture hardening

The core IR, validation, rendering, patching, review sidecars, and benchmark protocol are implemented enough to test.

Active Mode

Benchmark handoff

The next work is not more grand language. It is benchmark execution, negative evidence, and controlled comparison.

Blocked Claim

No superiority claim yet

OfOne can claim architectural coherence and working tooling. It should not claim empirical superiority until benchmarks support it.

Artifacts

The repository keeps method, type system, compiler tools, walkthrough, and benchmark evidence separate so the public site can explain the system without hiding the source of truth.

OfOne turns complex questions into validated decision maps.