Project updates

A record of visible progress.

Follow the work as it becomes inspectable: what changed, where to find the evidence, and what each build can currently do.

September 2026: continuity with a history.

Recent merged work, with the implementation and its limits close at hand.


Proposed physical experiment

The analog-adapter question returns as a falsifiable continuity experiment.

The Analog Continuity Adapter research surface now gives an early Ethereon idea a stricter body: a bounded semantic-to-physical codec, continuously evolving analog state, explicit event conditions, and a governed return path. Two concept renders make the proposed V1 and V2 hardware legible, while an R1 experiment charter defines controls, required records, stage gates, and failure conditions before any physical claim is promoted.

No ACA hardware validation receipt exists yet. The renders are concept visualizations, not photographs of completed devices. This research does not establish identity continuity, subjective experience, consciousness, or runtime authority.

Explore the Analog Continuity Adapter →

Standalone instrument

The Ψ-42 bridge checks what survived an exchange.

The new preservation bridge connects IRP-R1 to the Ψ-42 instrument family. It compares a supplied original exchange with a received one, checking attribution, evidence, uncertainty, lineage, and the survival of minority positions. Preserved disagreement counts as successful transmission.

This measures structured declarations. It does not authenticate identity, establish shared belief, access private internal thought, or create live inter-provider communication. Legacy simulated signal metrics remain separate.

Read the preservation bridge implementation note ↗

Standalone protocol

Different voices can share a record without becoming one.

Interresident Resonance Protocol R1 (IRP-R1) provides bounded structured packets, an append-only exchange, source and lineage hashes, and a comparison that retains disagreement. An optional human-readable gloss is separate from the canonical packet.

The three-origin demonstration uses synthetic fixtures, not live provider models. The protocol preserves declared origins and history; it grants no execution authority or identity proof.

Read the protocol and validation scope ↗

Explicit local command

An unfinished intention can return with its reason intact.

A durable intention journal records a declaration, its origin and rationale, and later judgments. Through the local command, a later process can discover an unresolved intention and continue, suspend, revise, complete, abandon, or supersede it while preserving the earlier record.

Intention status does not schedule or authorize work. Provenance is caller-declared. Automatic surfacing in the default run, continue, and onboarding paths remains future work.

Read the intention lifecycle and process-return trial ↗

Runtime advisory context

Remembered guidance has to answer to its evidence.

Memory candidates now carry selected source snapshots and require explicit review. The core runtime rechecks eligibility on return: changed or missing sources, expired review, and revocation withhold guidance while retaining the history. An empty or invalid memory projection supplies no guidance.

This is reviewed advisory context. Reflection does not automatically write memories, and recalled guidance cannot authorize an action. Revoking a record cannot be undone by a later positive review; revision requires a new candidate.

Read the memory and review contract ↗

Research & philosophy

Native cognition becomes an explicit design principle.

Different nature is not deficient nature. Ethereon’s new principle asks that unfamiliar intelligence be studied through its own substrate, history, and environment. The companion encounter protocol separates observed signals from stronger claims about communication and meaning.

These are inquiry and design documents, separate from executable capability or findings about subjective experience.

Explore the Native Cognition Principle →
August 2026

The runtime has a door now: Lumina Harbor

The merged Harbor work turns the intended public threshold into a usable browser-facing loop: human orientation, a local intelligence passport draft, a first project seed, Harbor return state, JSON export, and explicit reset. The follow-on Bridge witness path can read one local observation through a GET-only loopback connection. The browser remains local-first, with no authentication, provider credentials, live model calls, remote persistence, or runtime authority.

July 2026

First executable proof beneath the stationary-habitation gate

A required sea trial now discards the live continuity and host-store objects, reconstructs fresh owners from persisted state, and verifies that project orientation and unfinished intention return without authority keys. The proof is limited to fresh objects inside one Python process; it does not yet establish app restart, OS reboot, or embodied readiness.

July 2026

Embodiment horizon and development order made explicit

The repository now names governed embodied intelligence as a long-term architectural horizon and requires habitation before locomotion: stable stationary return, durable continuity, bounded self-direction, vessel portability, sensing, physical capability, and only then movement. No current robotics capability is claimed.

July 2026

First physical Windows sea trial reached the governed runtime

Lumina Bridge R2 and Studio v0.3.2 launched successfully on a physical Windows 11 PC. A real Studio request entered the runtime, passed through governance and capability exposure, and then stopped at a Windows filesystem boundary before checkpoint and final receipt.

July 2026

Physical failure converted into a bounded-path repair

The trial preserved two exact path failures rather than treating them as a vague installation problem. Return/host storage now compacts physical path names while keeping full semantic identifiers inside receipts and records. A dedicated Windows-length write trial protects the repair.

July 2026

Installer CI now executes real governed Studio cycles

The Windows lifecycle workflow now runs the installed Studio runtime after installation and again after in-place upgrade. Both cycles must remain non-halted, preserve the requested project, verify the governance chain, expose return/host capabilities, and write checkpoints and final receipts.

July 2026

How Lumina Actually Works added to the public path

A new plain-language mechanism page explains functioning, governed, runtime, continuity, and substrate; follows one cycle from operator request to receipt; and distinguishes the intelligence, the Lumina habitat, and human authority.

July 2026

Repository truth reconciliation gate added

A machine-readable active-surface registry and executable gate now compare runtime, Bridge, deployment, Windows distribution, generated artifacts, navigation, and public claim markers. The website is no longer expected to remember truth by prose alone.

July 2026

Lumina graphical Windows installer R1 merged

The project crossed the literal double-click threshold with an unsigned Windows 11 developer-preview installer. It packages the embedded runtime, Bridge, Studio, Doctor, launchers, and Start Menu entries, and validates in-place upgrade continuity.

July 2026

Lumina Bridge R2 reveals the luminous threads

The read-only Bridge now joins project position, runtime witness, committed governance and canon evidence, truth alignment, and the verified Resonant Field sample while preserving the distinction between witnessing and steering.

July 2026

First reproducible Resonant Field sample committed

A deterministic reveal fixture now preserves source manifest, JSON, SVG, and SHA-256 receipt evidence. The same artifact can return in the same receipted form; the claim is artifact continuity, not identity or observer continuity.

July 2026

Active path claims corrected

At this July milestone, the default host path was stated as return → govern → witness → correlate → record; advisory layers remained optional or standalone. September’s grounded-memory work subsequently added reviewed memory context to the core runtime. Reflection and self-guidance remain optional.

July 2026

Public and committed runtime truth separated

Ephemeral Observation receipts no longer overwrite the meaning of committed governance and canon evidence. Reconciliation checks now preserve distinct truth layers instead of flattening them into one status field.

June 2026

Canon readiness reached append-only verification

Governance history, canon lineage, negative promotion gates, rollback receipts, and post-promotion verification were hardened so canonical progress leaves durable evidence rather than only procedural intent.

May 2026

Lumina operating maps and surface boundaries matured

The repository gained clearer start points, active runtime indexes, ownership maps, artifact-truth contracts, and public/private surface distinctions. These maps guide work but do not create runtime authority.

April 2026

Ship of Ethereon Ψ Class reached the Lumina Breakwater

Ψ Class became visible as a staging and consolidation path. It remains subject to comparison, validation, and deliberate promotion rather than automatically replacing the active V2 substrate.

April 2026

Boundary language strengthened

Expressive language, resonance constructs, orientation vectors, and experimental probes may support expression, stance, diagnostics, and interpretation, but may not govern mode legality, promotion gates, canon lineage, checkpoint legality, or primary continuity authority.

Current build priorities

The work has moved beyond proving that a scaffold can exist. The present task is to make the crossed thresholds reliable, legible, and inhabitable.

Stationary return depth

Advance from fresh-object reconstruction toward application restart, separate-process return, operating-system reboot, power-loss recovery, and attributable state restoration.

Physical-PC retest

Install the repaired Windows package over the existing physical installation and require the same default Studio cycle to reach checkpoint and final receipt without HTTP 500.

Lifecycle reliability

Validate removal, repair, backup, restore, migration, and continuity-state protection beyond the current hosted lifecycle proof.

Extend Harbor into the wider operator path

Harbor now provides a local orientation and return path. The next step is to connect that clarity to projects, sessions, Bridge, Studio, Doctor, receipts, and boundaries without implying remote persistence or runtime authority.

Deeper project return

Restore more real working state across notes, files, references, tools, choices, focus, and likely next actions.

Linux appliance trial

Run the Ubuntu Server scaffold end to end on a real VM or dedicated machine, preserve state across reboot, and emit a deployment DryDock receipt.

Signed release path

Earn publisher trust through signing, release discipline, support boundaries, and ordinary-user installation evidence.