This page tracks the thresholds that have become inspectable: active runtime wiring, local operator surfaces, physical and hosted distribution evidence, reproducible artifacts, and the mechanisms that keep public language subordinate to repository truth.
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.
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.
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.
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.
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.
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.
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.
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.
The current default host path is stated as return → govern → witness → correlate → record. Reflection, self-guidance, and Meaning Metabolism remain explicit optional or standalone advisory layers rather than being implied as hidden default wiring.
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.
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.
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.
Ψ 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.
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.
The work has moved beyond proving that a scaffold can exist. The present task is to make the crossed thresholds reliable, legible, and inhabitable.
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.
Validate removal, repair, backup, restore, migration, and continuity-state protection beyond the current hosted lifecycle proof.
Make projects, Harbor sessions, Bridge, Studio, Doctor, receipts, and boundaries understandable without repository expertise.
Restore more real working state across notes, files, references, tools, choices, focus, and likely next actions.
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.
Earn publisher trust through signing, release discipline, support boundaries, and ordinary-user installation evidence.