WorldBuilder

A durable AI generation system that transforms creative direction into a governed world model, connected lore, narrative structure, a readable edition, and a versioned software package.

Designed and built by Mobolaji Ogunbiyi · January 2026—Present

Status: complete offline mechanics path; live creative qualification not yet claimedRole: architecture, workflow, domain model, evaluation and verification
DemoCase StudyEvidencePrivate repository

Trace explorer

This fixture-driven replay shows the implemented mechanics boundary: generation, persisted checkpoints, linked branching, independent evaluation, bounded repair, and re-evaluation. It does not present synthetic content as live creative-quality proof.

The Ash Meridian / generation run 047Offline fixture · sanitized · read only

1. Generate governed products

Creative direction enters a finite compiled program. Model proposals are treated as untrusted input until validated and admitted by the owned domain boundary.

direction: fractured archipelago after a vanished sun
products: lore corpus, narrative web, world edition, package manifest
proposal_authority: none

2. Persist checkpoints and provenance

Workflow state stores references to immutable artifacts, preserving identity, dependencies, provider evidence, costs, and the exact point from which work can continue.

checkpoint: world_foundation
artifact_refs: 14
provenance: sealed
controls: pause | resume | cancel | replay

3. Create a linked fork

A proposed change starts from an exact checkpoint and creates a non-destructive linked branch. The original world remains inspectable.

source_checkpoint: world_foundation:v3
change: make the eastern islands politically independent
target_run: ash-meridian-fork-02
original_mutated: false

4. Evaluate independently

The evaluator judges admitted state and generated products across eighteen non-waivable dimensions and emits cited findings instead of a vague quality score.

verdict: blocked
dimension: causal_coherence
finding: trade route depends on a removed treaty
evidence_refs: lore:71, narrative:18

5. Repair once, then re-evaluate

The workflow creates a finite repair contract for the cited weakness, revises only affected descendants, recompiles the product, and runs the independent evaluator again.

repair_scope: trade_route + affected narrative edge
repair_turns: 1
reevaluation: certified
delivery: revised edition + inspection refs
Read the complete trace
  1. Compile a finite generation program and admit only validated proposals.
  2. Persist checkpoint references, provenance, and controls.
  3. Create a non-destructive fork from an exact checkpoint.
  4. Evaluate admitted state and actual products across eighteen dimensions.
  5. Execute one cited repair and re-evaluate before delivery.

Contextualized evidence

The repository proves a complete zero-live mechanics path. It does not yet prove live creative quality, benchmark acceptance, production operations, or a desktop release.

Offline baseline
511 / 511 tests passing
Independent rubric
18 dimensions
Durable controls
Pause · replay · linked forks

Evidence covers deterministic contracts, persistence, retained transport, workflow execution, evaluator verdicts, bounded repair, delivery, controls, and inspection at the documented revision.

What I engineered

Durable generation

A finite workflow separates direction, foundation, growth, program execution, integration, product authorship, evaluation, repair, and delivery.

Trusted world state

Model proposals cannot assign canonical identity or mutate trusted state. Authority validates, records provenance, and admits revisions.

Independent quality control

An eighteen-dimension evaluator produces evidence-backed findings and bounded repair requests that re-enter the durable workflow.

Architecture

Durable execution coordinates model work, but trusted admission and independent evaluation remain separate owners.

Engineering decisions and tradeoffs

Models propose; code governs

Creative decisions remain model-driven, while identity, feasibility, budgets, validation, and proof are deterministic. This reduces hidden mutation at the cost of more explicit contracts.

References, not giant workflow payloads

Large immutable bodies use content-addressed storage and workflow state retains references. That improves recovery and provenance, but demands disciplined artifact ownership.

Repair is finite

Evaluator findings can trigger bounded cited repair, never an open-ended self-improvement loop. This limits runaway cost and preserves causal history.

Current status

WorldBuilder has a complete offline mechanics path for generation control, trusted admission, product compilation, independent evaluation, bounded repair, delivery, and inspection. Live creative quality, the complete benchmark, production operations, and a desktop release remain unclaimed.