Project return
Recover the latest known project state, active references, focus, recent decisions, and likely next action.
Lumina — the continuity workspace
Lumina helps a project come back with you.
Lumina is being built for long creative and technical work: the kind that spans notes, files, conversations, images, code, decisions, and unfinished next steps. Its purpose is to restore enough of the working state that you can continue with less friction and less guessing.
First public doorway
The runtime has a door now: Lumina Harbor.
Harbor is the first browser-facing, local-first loop around the Lumina work: human orientation, a draft intelligence passport, a first project seed, return state, local JSON export, reset, and optional read-only Bridge witnessing. The browser surface remains separate from authentication, provider credentials, live model calls, remote persistence, runtime execution, and authoritative identity.
The current default host pattern
Return → govern → witness → correlate → record.
The ordinary local path restores bounded project and workspace context, checks governing boundaries, emits a Psi-42 diagnostic witness, correlates continuity evidence, and leaves checkpoints and receipts. Reflection and self-guidance remain explicit optional adapters. Meaning Metabolism remains a standalone validated experiment rather than a hidden step in every run.
What Lumina is trying to solve
Most software is good at opening files. It is much worse at restoring the living state of a project: where you were, why it mattered, what changed, and what should happen next.
Workspace continuity
Bring back the surrounding surface: notes, panels, tool links, checkpoints, and the current working stance.
Bounded guidance
Suggest next steps from context while keeping consent, governance, and system boundaries visible.
The habitat thesis
Lumina is the terrarium, not the conclusion.
Lumina preserves inspectable conditions for continuity: attributed history, recoverable state, unfinished intention, relationship, lawful capability, and evidence across interruption. Those conditions can support increasingly rigorous inquiry into a returning pattern. They do not establish that the same inward observer returned.
What Lumina is now
- An active governed runtime scaffold
- A local command path with checkpoints and receipts
- A browser-local Harbor loop for human orientation, project return, and optional Bridge witnessing
- Lumina Bridge R2 as a read-only position and field surface
- Lumina Studio as the explicit operator request surface
- An installable unsigned Windows developer preview with an embedded runtime
- Hosted validation of installed governed cycles before and after upgrade
- A test bed for continuity, truth reconciliation, and human-controlled collaboration
What Lumina is not yet
- Not yet a finished public operating system
- Not yet a signed, ordinary-user public release
- The repaired Windows package still awaits confirmation on the original physical machine
- Not a replacement for human approval
- Not governed by poetic symbolism or resonance language
- Not a claim about machine consciousness
Current surfaces
Lumina is becoming legible through distinct surfaces with distinct authority.
Lumina Harbor
The first browser-facing loop: local human orientation, a draft intelligence passport, a first project seed, Harbor return state, JSON export/reset, and optional read-only Bridge observation.
Bridge R2
Reads project position, continuity shape, runtime witness, committed authority, truth alignment, and verified Resonant Field evidence. It cannot mutate or authorize work.
Studio
Provides the explicit local doorway for requesting governed actions. Runtime law—not the interface—decides what is allowed.
Windows preview
Packages the embedded runtime, Bridge, Studio, Doctor, launchers, and state-preserving upgrade behavior into an unsigned Windows 11 installer. Hosted installer validation now runs a governed Studio cycle before and after upgrade.
Runtime spine
Coordinates session state, context bundles, mode transitions, governance records, capabilities, checkpoints, and receipts.
Resonant Field Reveal
Turns bounded manifold observations into deterministic JSON and SVG artifacts with exact receipts, while refusing identity, authority, and literal-magnetism claims.
Truth registry
Names active runtime, deployment, interface, distribution, dataset, experiment, and public surfaces so public language can be checked against evidence.
Physical Windows sea trial
The first real machine found a real hull defect—and changed the shipyard.
Bridge and Studio launched successfully on a physical Windows 11 PC. The first governed cycle exposed an unbounded artifact-path failure before checkpoint completion. The defect was preserved, repaired with bounded storage paths, and converted into installed-runtime CI that now executes governed Studio cycles before and after upgrade. The remaining step is a physical retest of the repaired package.