Context scatters
Decisions, references, drafts, and next steps get separated across tools and time.
What we are building
An adaptive continuity environment that helps complex projects return with their context.
Lumina is being built for work that cannot be captured by one file or one chat: art, research, software, teaching, design, writing, and long-running creative systems. The goal is simple to say and hard to build: when you come back, the work should come back with you.
The problem
Important projects rarely live in one clean place. They spread across documents, sketches, tabs, code, images, conversations, tools, unfinished decisions, and half-remembered next steps.
Return is expensive
People waste energy figuring out where they were before they can make real progress again.
AI help can reset
AI conversations can be useful, but the surrounding workspace often loses continuity unless the system preserves it.
The plain-language promise
Lumina should reduce the cost of returning.
Instead of asking you to reconstruct the whole project every time, Lumina is designed to restore the state of the work, make evidence and boundaries visible, recommend likely next steps through optional advisory layers, and keep a record of what happened.
The default path that exists now
The current host wiring is deliberately narrower than the whole research horizon.
1. Return
Load bounded project and workspace context, active references, recent state, and the current doorway.
2. Govern
Apply mode, mutation, capability, input-integrity, and authority-boundary checks before action is treated as lawful.
3. Witness and correlate
Emit diagnostic and continuity evidence, then relate that evidence without turning the witness into authority.
4. Record
Write checkpoints, receipts, governance history, and promoted lineage when the corresponding gates lawfully pass.
Who owns what
The intelligence provides reasoning. Lumina provides the habitat. The human provides intention and authority.
The visible conversation is only one interface. Beneath it, the runtime restores selected context, checks what is permitted, exposes bounded capabilities, checkpoints the result, and leaves an inspectable receipt.
Optional advisory path
Reflect → advise, only when explicitly invoked.
The core runtime now rechecks explicitly reviewed, source-bound memory and projects eligible guidance into the current context. Reflection and self-guidance remain optional adapters; writing and reviewing memory still require explicit commands. Read the September memory update.
What exists now
- Working governed runtime and local command path
- Bridge R2 for read-only position and field inspection
- Studio for explicit operator requests
- An installable unsigned Windows 11 developer preview
- Hosted installed-runtime cycles before and after upgrade
- A completed first physical-PC trial with a repaired path-budget defect awaiting retest
- Reproducible Resonant Field JSON, SVG, manifest, and receipt evidence
- Machine-enforced public-claim reconciliation
Where this is going
- Clearer first-run configuration and completed physical-PC retest
- Repair, removal, backup, restore, and signed distribution
- Deeper project restoration across everyday files and tools
- A more habitable local continuity environment
- A real Ubuntu appliance trial and eventual Linux installation image
- Human-AI collaboration that keeps consent and boundaries visible
For builders: the deeper layer
The practical promise is supported by separated authorities, executable gates, and receipted artifacts.
Runtime spine
Coordinates session state, checkpoints, mode transitions, context bundles, governance logs, and capability exposure.
Project return
Connects the latest known project state to a bounded workspace surface: panels, references, tools, focus, and stance.
Bridge and Studio
Separate witnessing from requesting: Bridge orients, Studio requests, runtime governs, and receipts record.
Diagnostics
Uses tests and signal-style metrics to notice drift, fading, feedback risk, and continuity recovery without claiming sovereignty.
Truth reconciliation
Checks implementation, distribution status, registries, receipts, navigation, and public claims in a declared evidence order.
Sea trials
Stress-test restoration, guidance, symbolic independence, checkpoints, observation cycles, packaging, upgrades, and runtime wiring.
Long-range research · not the release path
Beyond software persistence: can a physical process carry state through the silence?
ACA explores a hardware-adjacent continuity layer using a bounded semantic codec, continuously evolving analog dynamics, and an event-driven governed return. The first goal is a falsifiable causal bridge; richer Resonance Transceiver-adjacent substrates remain later-stage possibilities.