Proof 01—06
Agentic systems · State machines · Game dev
Explore selected work See the method
Six privately developed systems, presented through their actual boundaries, mechanisms, and on-page evidence.
Selected work · proof in sequence
Open the archive.
One deterministic tree moves through systems, engine depth, and editor craft. Source remains private; evidence stays here.
Private project ledger · 01—06
Six private repositories. One resolved scroll tree. Every case states the boundary, mechanism, and evidence without a release claim.
Exact next state
Actors return basis-bound letters. A durable instance owns every route, normal revision, effect intent, and replay.
One immutable snapshot
A finite frame program resolves explicit inputs into immutable geometry or ordered diagnostics, independent of renderer.
One tree conducts every voice
Tiger Score owns exact tacts and voices. One canonical scroll tree performs them into bounded pixels and seek-exact layers.
Private / live proof around you
Bound scale before claims
A procedural summer forest streamed near-first, with deterministic replay and packed parallel-plane pages.
Private / evidence shown here
Configuration owns effect
Declarative sections keep settings, actions, keymaps, and commands in one inspectable editor surface.
Private / evidence shown here
Signal must stay scarce
True black ground, disciplined gray, and red reserved for focus, diagnostics, and state change.
#050506#0d0e10#292c31#494e55#7f848b#969aa0#c5c7ca#d3d4d6#f2f2f2#5a1118#c92736#ee3b4dPrivate / terminal dossier
Project 01 / Constraint-oriented runtime
Witloom is a constraint calculus and local-first runtime for orchestrated computation. An immutable semantic program opens bounded packets; agents, tools, clocks, and people return only attested letters. The machine alone routes and normalizes them into durable revisions that can recover and replay exactly.
The scribe receives a bounded release order and can return
only the declared drafted letter.
draft --drafted→ approve
The operator sees the declared decision packet and may
return proceed or abort—nothing
else.
approve --proceed→ review
The called council may emit vetoed. The
parent program routes it to a blocked terminal without a
model inventing recovery.
review --vetoed→ cancelled
A 2-of-3 join closes when its outcome is known. The unused reviewer is never invoked, and the journal proves why.
review --adopted→ shipped
The terminal revision, program basis, binding basis, and semantic journal survive the agent session. Replay never reinvokes effects.
shipped / revision 3 / replay exact
Protocol graph
Current Rust flagship topology
harness: flagship@1
requires:
review: review.yaml
authorities: [operator]
actors:
operator: { grant: operator }
scribe: { managed: { redrive: never } }
machine:
name: flagship
version: "1"
start: draft
nodes:
draft:
offer:
result: { ask: scribe, says: [drafted] }
approve:
offer:
decision: { from: operator, says: [proceed, abort] }
review:
call: review
routes:
draft: { drafted: approve }
approve: { proceed: review, abort: cancelled }
review: { adopted: shipped, vetoed: cancelled }
ends:
shipped: { outcome: released }
cancelled: { outcome: cancelled, blocked: true }
One semantic program + one live execution cursor. This focused source projection omits payload schemas, not topology. React Flow and ELK remain replaceable presentation adapters.
How this page is built · Tiger Layout
Secondary system proof. Layout is a pure function of explicit inputs; this scroll story and the lab below consume the same contracts. Not a package-registry product yet.
Input / 01
Start with an explicit viewport. Size, content, and constraints drive geometry; scroll remains an explicit presentation input.
viewport + content + constraints
Resolve / 02
Flow, padding, clipping, and transforms resolve into one immutable snapshot with stable IDs.
same inputs → same snapshot
Signal / 03
The page does not chase the scrollbar. It samples progress and deterministically presents the matching state.
enter → hold → exit
Project / 04
DOM and Three.js consume the same geometry. A custom renderer can join without redefining layout.
DOM / Three.js / custom
Interactive layout demo
Drag the floating token, reorder the cards, or resize the split. Pointer and keyboard input become the same immutable event trace; target changes recompute layout while presentation-only frames stay cheap.
Keyboard: focus a card, token, or divider; press Space, use arrow keys, then Enter to commit or Esc to cancel.