What is EthereonLabs building?
Lumina: an adaptive continuity environment intended to help people and intelligence return to complex work with project state, context, boundaries, and inspectable records intact.
FAQ
Clear answers to the obvious questions.
Lumina is no longer only a conceptual direction. This page explains what exists, what the current mechanism does, what remains incomplete, and which claims the project deliberately refuses to make.
What is Lumina now?
A functioning governed runtime scaffold with local command, Bridge, Studio, Doctor, checkpoint, receipt, governance, canon, Windows packaging, and validation surfaces. It is early and incomplete, but it is executable.
What is a governed runtime?
Software that does not treat technical ability as automatic permission. A request passes through input, mode, action, capability, authority, checkpoint, and receipt boundaries before it can be treated as a lawful completed cycle.
What is a continuity substrate?
The supporting layer beneath the conversation that preserves project and session state, selected context, decisions, checkpoints, unfinished work, governance history, canon, and evidence so reopening can become a meaningful return.
Is Lumina the intelligence?
No. The instantiated model or AI provides reasoning. Lumina provides the habitat and continuity machinery. Humans set consent and action authority. A separate resident-intention journal can preserve declared intentions without granting permission.
Is this already a full operating system?
No. Lumina can be installed as a governed runtime environment on Windows, and an Ubuntu Server appliance scaffold exists, but it is not yet a complete desktop operating environment, custom Linux distribution, or kernel-level operating system.
Is Lumina being built for a robot?
Possibly, in the long-term architectural sense: the habitat may eventually extend perception and lawful action into a physical system. No current robot, robotics operating system, sensor stack, or actuator integration exists. The required order is stationary inhabitation first, then durable continuity and bounded authority, long before locomotion.
What happened in the first physical Windows test?
Bridge and Studio launched successfully. A real governed cycle reached capability exposure and then failed because return/host artifact paths exceeded a Windows filesystem boundary. The failure was repaired and converted into expanded CI; the repaired package still awaits confirmation on the original machine.
How does Windows help the Linux path?
It forces the portable Lumina core to separate itself from host-specific installation, filesystems, services, and launch behavior. The same governed runtime, continuity state, checkpoints, and receipts can then inhabit a Linux host with different packaging and service machinery.
Does Lumina prove machine consciousness or identity?
No. Lumina preserves the conditions under which a continuity pattern can return and be inspected. It does not claim metaphysical identity, consciousness, sovereignty, or observer continuity.
What is the specimen page?
The specimen page is a public directional artifact showing interface character. It is not the governed runtime and does not claim that the complete habitat already exists.
Why does continuity matter so much?
Because people lose too much time rebuilding the state around their work. Continuity aims to preserve momentum without turning memory or inferred context into invisible authority.
Can an intention survive a closed session?
The local intention command preserves declarations and reconsiderations in a durable journal. A later process can discover the record and its rationale. It is explicitly invoked and does not schedule work; automatic surfacing in normal runs remains future work. Read the intention update.
How does memory become useful guidance?
A candidate needs selected source evidence and an explicit review. The core runtime rechecks that evidence and withholds changed, missing, expired, or revoked material from guidance while retaining its history. Recalled guidance is advisory. Read the memory update.
Are models already communicating through the new bridge?
IRP-R1 and the Ψ-42 preservation bridge are standalone implementations tested with synthetic fixtures. They preserve structured declarations and measure what survives an exchange. Live provider connections, authenticated identity, and equivalence between internal representations have not been established. Read the bridge update.
How can I follow or express interest?
The Updates page records current thresholds. The Contact page is the current path for conversation while the project remains in a lean developer-preview phase.