Current surfaces

Lumina is becoming visible through more than one doorway.

The public dashboard remains a browser-based witness surface. The local Bridge and Studio make the working environment more legible, and the unsigned Windows developer preview now packages those local surfaces with the embedded runtime. None of these surfaces outrank runtime governance.

How to read the surfaces

Each doorway has a different job.

Public pages explain and witness. Bridge orients. Studio requests. Runtime governance decides legality. Receipts record what happened. Canon preserves promoted lineage. The separation is part of the product, not an implementation detail to hide.

Public dashboard

Displays continuity weather, history, trends, symbolic grammar, and diagnostic state. It is an instrument panel, not an execution authority.

Chamber

Offers a simple browser-local reflection loop with selectable perspective lenses. It remains a public prototype, not the governed runtime substrate.

Lumina Bridge R2

A local read-only surface for ship position, continuity, committed authority, runtime witness, truth alignment, and verified luminous-thread evidence.

Lumina Studio

The explicit local operator surface for requesting governed cycles. It can ask; the runtime still decides.

Windows developer preview

An unsigned Windows 11 installer adds the embedded runtime, Bridge, Studio, Doctor, launchers, and state-preserving upgrade behavior. Hosted lifecycle validation now executes installed governed Studio cycles before and after upgrade.

Resonant Field sample

A deterministic JSON and SVG artifact demonstrates receipted artifact continuity and lawful-versus-denied trajectories without claiming identity or literal magnetism.

Physical Windows evidence

The first real-machine cycle found a path defect before checkpoint completion.

Bridge and Studio launched successfully. The failure was traced to unbounded return/host artifact paths, repaired with compact physical storage names, and turned into installed-runtime CI coverage. The repaired package now awaits confirmation on the original physical machine.

What can be examined now

  • Public continuity status and history
  • Local read-only project and runtime position
  • Explicit operator request flow
  • Hosted Windows install, governed-cycle, upgrade, uninstall, and state-preservation evidence
  • First physical Windows launch and failure evidence
  • Verified governance, canon, and field evidence
  • Where public claims agree—or fail to agree—with implementation

What remains incomplete

  • No signed public installer yet
  • Repaired physical Windows cycle still awaits retest
  • No frictionless first-run configuration yet
  • No complete desktop workspace replacement
  • No proof of consciousness, identity, or observer continuity
  • No visitor-facing governed execution through the public website
Plain next step

Understand the mechanism, then examine the surfaces.

How Lumina Works explains the governed cycle. This page shows the doorways through which that cycle becomes visible.

How Lumina works