runtime phase 1/8

world gate · the public proof surface

Software should understand the world before it renders the interface.

Reality Loom is the open foundation for Reality-Oriented Computing: a way to describe reality, compute understanding, and project living experiences.

world_graphwil: “rearrange my morning…”cw_1: “rearrange my morning…” — not yet realauthority boundarylaw: is this actor permitted?snap_n+1 · diff: + “rearrange my morning…”trace: what · why · whoSLI projection · “rearrange my morning…”living surface

world gate · a world graph awakens

this surface is composed from @realityloom/interface primitives — no cards, no panels, no template

interface contract · validateScene: 0 violations · 27 primitives · 27 objects

runtime phase 3 · capability constellation

Capabilities are nodes, not cards.

reality loomWorld GraphsCandidate WorldsAuthority BoundariesTraceable AISpatial ProjectionCompiler PipelineCompliance FixturesDeveloper Inspectors

hover a node — every one carries a runtime meaning

no-overlap registry: 9 objects · 0 collisions

runtime phase 4 · compiler flow

Description becomes executable reality.

WDL SourceWIL Semantic OperationsWorld CompilerWIRExecutable WorldRuntimeProjection

the runtime never executes raw WDL — description compiles, reality executes

runtime phase 5 · authority boundary

Nothing becomes real without permission.

authority boundaryproposalrealitytrace
  1. AI can propose.
  2. Runtime validates.
  3. Authority permits.
  4. Commit changes reality.
  5. Trace explains.

runtime phase 6 · open foundation boundary

The foundation is open. The moat is not.

open · Apache 2.0 + CC BY 4.0

  • ROC — the category
  • WGE — world graphs
  • WIL — the protocol
  • WDL — world language
  • SLI — projection
  • compliance fixtures
  • reference runtime

private · the boundary holds

  • EmiLu
  • Sentii
  • DeckLogic
  • Autelier
  • Trader Sherpa
  • proprietary prompts
  • private cloud runtime
  • product intelligence

open-source the foundation. do not accidentally open-source the moat.

the interface contract · executable, not aspirational

  1. 1. Reality Loom does not use cards as its primary visual metaphor.
  2. 2. Every visible element is a field, node, trace, surface, layer, projection, or boundary.
  3. 3. The UI must visually express runtime behavior.
  4. 4. Generic SaaS layouts are invalid.
  5. 5. Light textured card grids are invalid.
  6. 6. MUI visual components may not define primary brand surfaces.
  7. 7. No visual object may overlap another unless explicitly intentional.
  8. 8. Motion must express projection, trace, ripple, commit, recede, or recomposition.
  9. 9. The system must distinguish candidate state from committed reality.
  10. 10. Reality Loom should feel like an operating substrate, not a website template.

runtime phase 7 · builder commit

Commit yourself into the world.

This is not a normal AI startup. It is a new computing and interface substrate — and the foundation is public. Clone it, run the loop, read the Codex, break something, propose.

$ git clone https://github.com/Architech-Forge/reality_loom.git

$ pnpm install && pnpm build

$ pnpm demo # simulate → law-check → commit → project