State estimation
Work with noisy, changing signals and compare estimation methods on the same observations.
Try the Black Box →AN INTERACTIVE SYSTEM DEMONSTRATION
A local-first experimental computing platform for state estimation, evidence-aware reasoning and governed simulation — built to keep evidence, uncertainty and action visibly distinct.
Website demonstration · Separate from the local operational master · A diagram is not a service health check.
FREEDOM · TRUTH · COHERENCE · RESPONSIBILITY
Lexium is an experimental local-first computing environment. Its research asks whether more direct representations of state, relationships and change can reduce unnecessary processing while keeping evidence, uncertainty and permission boundaries visible.
Work with noisy, changing signals and compare estimation methods on the same observations.
Try the Black Box →Structure observations, relationships, competing explanations and preserved unknowns without pretending input evidence has been independently verified.
Understand Lexic →Keep simulation, preparation and proposed actions separate from authority. A model result does not silently become an action.
See the architecture →Representation-efficiency tests support the general shorter-path hypothesis. They do not yet establish that Lexic semantics causes all Lexium speed or estimator accuracy. That causal claim remains UNKNOWN.
Lexium organises reasoning, preparation and evidence around explicit governance. Select a component to inspect its role and limits.
Conceptual relationships only. Athenic remains PREPARE; this map grants no execution authority. Inspect the component directory →
Choose a repeatable dataset, inspect truth and noisy observations, then measure estimation error.
USE WHEN You want a reproducible state-estimation comparison rather than a marketing claim.
YOU GET Downloadable CSV datasets, MAE evidence and local black-box Lexium comparison without exposing the estimator source.
PUBLIC DATA · LOCAL PROPRIETARY RUNTIME
Run the MAE →Capture an image and inspect what is actually visible before identification or value is inferred.
USE WHEN You have an object or photo and need an evidence-first starting point.
YOU GET A retained image record; recognition and valuation still require a verified connector.
ANALYSIS CONNECTOR: NOT CONFIGURED
Open Prospector →Supply observations that point to different answers and inspect how support accumulates.
USE WHEN Sources, notices or observations disagree and you need to see what supports each candidate.
YOU GET Ranked support, alternatives, limitations and next checks — not a guaranteed prediction.
LIVE LOCAL ENGINE · PUBLIC A$4 / READ NOT YET ENABLED
Open All-Seeing Eye →Demonstrate local-first analysis of permitted telemetry and observable outputs without installing into or controlling the target system.
USE WHEN You want to understand the research direction for vehicles, machines or low-connectivity field environments.
YOU GET A static capability demonstration, example report and clear validation boundaries. There is no public runner or adapter access.
DEMONSTRATED CAPABILITY · NO PUBLIC EXECUTION
View OmniKey demo →An input or measurement, with its source.
A record supporting a specific, bounded claim.
A model output under stated assumptions.
A proposal awaiting review and permission.
An explicitly permitted action; verify its result.
A question the available evidence cannot resolve.
PASS, FAIL and UNKNOWN retain their meaning within the stated test. One synthetic run does not establish universal superiority. Inspect methods, evidence and limitations →
The public demonstration is intentionally narrower than the local development system. These boundaries are part of the product, not footnotes.
The Black Box can execute Lexium locally here, but the Windows installer/signing path for outside researchers is not complete.
Bio twins, organ models and surgical simulation are research interfaces. They are not clinically validated and have no diagnostic authority.
Public application rental and unfinished payment/fulfilment paths remain disabled until their delivery boundaries are verified.
Compact representation has shown lower transport overhead, but Lexic semantics has not been proven to cause all estimator speed or accuracy results.
The recorded 100k request used 1,821,174 bytes for JSON and 800,056 bytes for LXS1. JSON was 2.276× the LXS1 wire payload — about 56.1% fewer bytes for LXS1. Scoped to this test; not a universal density claim.
The public-safe build profile blocks local Command Centre, Dialogue, Analytics and operational APIs while preserving the local master.