LEXIUM / SYSTEM GUIDE

Understand the system without decoding it first.

Plain-language definitions for the core terms used across Lexium, Prospector, Veil, Proof and State-Space.

STATE-SPACE / PLAIN LANGUAGE

Not one answer. A map of how a system can exist and change.

01OBSERVE

Record the current LIVE state and the evidence attached to it.

02CLONE

Create a SHADOW state so experiments do not overwrite the source.

03PERTURB

Change a variable, input, relationship or condition in the shadow.

04REPLAY

Run the same sequence again and compare the resulting state.

05COMPARE

Inspect invariants, divergence, residuals and UNKNOWNs.

State-Space is a method for representing, observing and testing system states. A simulation or shadow result is not automatically evidence that the same result occurs in the physical world.

MODULE INSTRUCTIONS / TAXONOMY

What belongs where, and how to use it.

Choose a category, then open a module. Each uses the same six questions.

Architecture

LEXIUM

Architecture / LEXIUM

What
The overall project linking applications, reasoning, evidence and governance.
How
Choose a module, read its status, and open its instructions before using an input or running an experiment.
Why
Keep each part understandable while retaining a common standard for evidence.
How Lexium applies
Lexium supplies the organising principles: freedom, truth, coherence and responsibility.
Current boundary
A website page or diagram is not proof that its underlying service is connected.
Nexus

Architecture / Nexus

What
An overview of routing evidence between components while retaining source context.
Where
Open Nexus/nexus
How
Read source, route, handoff and verification stages; check the connection status.
Why
Avoid losing origin and meaning when information moves between systems.
How Lexium applies
Nexus has the integration role in the Lexium design.
Current boundary
The current page explains the workflow; it does not itself transfer evidence.
Veil & governance

Architecture / Veil & governance

What
The map of roles, permissions and boundaries around system actions.
Where
Open Veil & governance/architecture
How
Inspect which component proposes, which reviews and which is allowed to act.
Why
Keep a useful connection from becoming an unintended grant of authority.
How Lexium applies
Veil represents the security-governance boundary; Alex is the designated governor in the project design.
Current boundary
A policy description is not evidence that every enforcement path has been tested.

Experiments

State estimation

Experiments / State estimation

What
A repeatable comparison of five causal estimation methods on identical synthetic observations, with an optional authentic local Lexium trace.
Where
Open State estimation/state-space
How
Choose a scenario and seed. Keep noise fixed; vary a gain. Run, inspect MAE/RMSE, reset to repeat, and export the revealed samples.
Why
Investigate the trade-off between reacting to change and following noise.
How Lexium applies
Demonstrates how Lexium can present assumptions, comparisons and error openly.
Current boundary
The five baseline methods run in the browser; the optional Lexium trace needs the local adapter. Initial variances differ and dropout is unsupported by that adapter. This teaching comparison does not reproduce the recorded benchmark.
Athenic mode

Experiments / Athenic mode

What
The PREPARE-stage workflow and a health request to the local Athenulum service.
Where
Open Athenic mode/athenulum
How
Read the current health response and authority fields. Use State-Space to explore the teaching experiment.
Why
Examine proposed changes before any authorised action.
How Lexium applies
Applies the observe, diagnose, prepare and verify sequence within Lexium.
Current boundary
This page does not execute proposals. An unreachable service leaves its current authority unverified.

Applications

Prospector

Applications / Prospector

What
An image-capture surface for object evidence and an optional analysis connector, currently not configured.
Where
Open Prospector/foundry/quickscan
How
Choose an object photo, inspect its preview and connector status, then request analysis if the service is available.
Why
Help separate visible evidence from identification and valuation guesses.
How Lexium applies
Applies the evidence-first workflow to practical objects and possible value.
Current boundary
Capture does not establish authenticity, material composition or value. A missing connector means analysis is unavailable.
All-Seeing Eye

Applications / All-Seeing Eye

What
A local evidence-analysis workspace using the original All-Seeing Eye v0.3 engine to rank supplied candidate signals.
Where
Open All-Seeing Eye/all-seeing-eye
How
Supply evidence sources, candidate signals and confidence inputs. Run locally, inspect support scores and alternatives, then export the result. Synthetic examples are labelled.
Why
Make proposed analysis services understandable before a run.
How Lexium applies
Uses the Lexium principle that an output needs assumptions, evidence and uncertainty.
Current boundary
This page does not establish a working prediction engine or guarantee an outcome.
Black Box Lab

Applications / Black Box Lab

What
A privacy-first browser workspace for CSV validation and provenance reporting without uploading the raw file.
Where
Open Black Box Lab/black-box
How
Load a CSV, map truth, observation and candidate columns, select a supplied estimate or disclosed baseline, inspect MAE/RMSE/max error/bias/coverage and export the report.
Why
Let scientists inspect validation evidence without emailing sensitive datasets.
How Lexium applies
Keeps evidence, assumptions, provenance and execution boundaries visible while preparing for a separate local Lexium runner.
Current boundary
Browser-only metrics do not execute the proprietary Lexium engine. A signed loopback runner is still required for that capability.

Reasoning

Lexic

Reasoning / Lexic

What
The reasoning component's overview and a status request to the local bridge.
Where
Open Lexic/lexic
How
Read the reported runtime status and evidence. Follow the available demo link to inspect its own operating boundary.
Why
Make reasoning, uncertainty and source relationships inspectable.
How Lexium applies
Lexic is the intended reasoning layer within Lexium; it is not the whole system.
Current boundary
A status response establishes reachability only. Historical test labels do not prove a current reasoning run.

Navigation

Command Centre

Navigation / Command Centre

What
A website navigation and operations showcase, separate from the local operational master.
Where
Open Command Centre/command-centre
How
Use the launcher links to open a module, the experiment, the guide or the evidence pages.
Why
Provide a clear route through the system.
How Lexium applies
Presents Lexium's modules together while the local operational master remains separate.
Current boundary
Website tiles are not confirmation that launch, shutdown or recovery is wired to a service.
System directory

Navigation / System directory

What
A directory of components and their roles.
How
Choose a component and follow its page for instructions and current connection information.
Why
Help you find where a task belongs.
How Lexium applies
Shows the organisation of Lexium's different parts.
Current boundary
Directory metadata is not a live health check.

Research

Bio research

Research / Bio research

What
Experimental organ and body visualisations and research interfaces.
Where
Open Bio research/hospital
How
Choose a lab, inspect its experimental status and use the controls available in that view.
Why
Explore how research models are represented and inspected.
How Lexium applies
Applies the same separation of model, input and evidence to biological research.
Current boundary
Experimental and non-clinical. A rendered organ does not establish physiological validity.
Research

Research / Research

What
An index of research directions and experimental work.
Where
Open Research/research
How
Open a topic and check its stated scope, inputs and evidence before interpreting a result.
Why
Keep unfinished investigations visible without presenting them as finished products.
How Lexium applies
Locates experimental work within the broader Lexium programme.
Current boundary
A research listing is not a validation result.

Evidence

Provenance Ledger

Evidence / Provenance Ledger

What
A local SHA-256 and publication-evidence workspace for exact disclosures, online digest timestamping and a separate private ownership record.
Where
Open Provenance Ledger/provenance
How
Choose the exact file, hash it locally, timestamp only the digest online, add the public disclosure URL and export the manifest. Keep the original, manifest and timestamp proof together.
Why
Establish a reproducible chain showing which exact file existed, when its digest was timestamped and where any public disclosure was made.
How Lexium applies
Applies Lexium's evidence-first approach to provenance, ownership intent and disclosure history without publishing the private ownership address.
Current boundary
A timestamped hash is not by itself proof that technical content was publicly disclosed or that legal ownership has been perfected.
Proof

Evidence / Proof

What
The place to inspect project claims and their supporting records.
Where
Open Proof/proof
How
Read the method, dataset, baseline and limitations attached to a result. Look for reproducible evidence.
Why
Distinguish a measured result from an attractive assertion.
How Lexium applies
Evidence is the basis for deciding which Lexium claims are justified.
Current boundary
A pass applies only to the stated test. Missing source material remains unverified.

Story

Origin

Story / Origin

What
The story of Jamie and his work with ChatGPT: motivation, iterations and setbacks.
Where
Open Origin/origin
How
Read the narrative alongside its source note; use Proof for technical claims and the experiment to explore a method.
Why
Explain the human purpose and the limits behind the project.
How Lexium applies
Connects Lexium's emphasis on truth and responsibility to the way it was developed.
Current boundary
Personal context comes from Jamie's account. The story is not independent verification of every event.

Lexium

The governed system-of-systems.

Lexium is the umbrella architecture joining governance, reasoning, evidence, state-space work, applications and research surfaces. Individual systems can remain independently usable while connecting through governed interfaces.

Lexic

Residual-preserving reasoning core.

Lexic is the reasoning layer. Its design emphasis is to preserve uncertainty, contradictions, provenance and residual information instead of forcing every observation into a confident answer.

Veil

Security-governance boundary.

Veil is the security and governance layer. It defines permission, authority, access and policy boundaries between systems. It is not the reasoning engine.

Athenic

Adjective for controlled PREPARE and shadow-analysis operation.

Athenic describes the controlled PREPARE-stage mode used for observing, diagnosing, preparing and verifying proposed responses. The internal Athenulum service can use State-Space as an internal shadow, but it has no authoritative-write authority and shadow state cannot execute.

State-Space

A map of possible system states and transitions.

State-Space represents a system as a set of states, variables, relationships and permitted transitions. Instead of viewing only one output, it provides a structured way to inspect how a system moves, changes and diverges over time.

LIVE

The observed current state.

LIVE represents the current system state being observed. Experimental work should not casually overwrite LIVE evidence.

SHADOW

A safe experimental copy.

SHADOW is a clone or derived state used for simulation, comparison or testing. A shadow can diverge from LIVE while keeping that divergence visible.

Deterministic replay

Re-running a recorded sequence consistently.

Replay lets a known sequence of inputs, events or states be run again so outputs can be compared. Determinism helps separate real system changes from randomness or hidden variation.

Invariant

A property that should remain true.

An invariant is a rule or relationship expected to remain valid across a run or transition. Violating an invariant is evidence that something important changed or failed.

Residual

What the explanation did not account for.

Residuals are the remaining differences between observation and explanation. Lexium preserves them because discarded residuals can hide uncertainty, contradiction or a missing variable.

UNKNOWN

A valid evidence state.

UNKNOWN means the available evidence has not earned a stronger conclusion. It is preserved instead of manufacturing confidence.

Evidence

The observations supporting an output.

Evidence can include measurements, source records, images, extracted marks, benchmark results and system events. It should remain traceable to its origin.

Provenance

Where information came from and what happened to it.

Provenance records origin and transformation history so raw observation can be distinguished from extraction, interpretation, inference and later action.

Confidence

How strongly evidence supports a conclusion.

Confidence is not certainty. It should rise only when evidence supports it and should never replace UNKNOWN when evidence is insufficient.

Prospector

The practical phone-first object analysis application.

Prospector moves from capture through identification, extraction, analysis, verification, value, confidence and action. It remains an independent practical application and can connect to wider Lexium services when appropriate.

Nexus

Integration and connective surface.

Nexus links systems and services without requiring every component to become one inseparable application.

Proof

The evidence room for reproducible claims.

Proof surfaces benchmarks, reproduction status, methods, limitations and boundaries so claims can be inspected rather than presented as slogans.

PROVEN

Demonstrated within the stated test boundary.

PROVEN should describe something demonstrated by the defined test or evidence. It does not automatically mean universal, clinical or commercial validation.

EXPERIMENTAL

Still under investigation.

EXPERIMENTAL identifies work that may be functional or promising but has not earned the same evidence status as a proven component.

FAILED / BLOCKED

A failed test or intentionally prevented action.

FAILED means the relevant test did not pass. BLOCKED means governance, authority or another explicit gate prevented execution.

READING RULE

Evidence first. Interpretation second.

Lexium status labels describe the state of evidence or the role of a component. They should not be read as claims that experimental capabilities have been clinically, commercially or universally validated.