SYSTEM ATLAS / LEXIUM RELEASE v16.29.1

ONE SYSTEM.
VISIBLE BOUNDARIES.

See what each part does, when you would use it, what it is allowed to do, and what evidence supports the current claim.

SELECTED COMPONENT / DESIGN ROLE, NOT LIVE STATUS

ALEX / GOVERNANCE

Use to review permission, authority and trace

CAPABILITY REVIEW / 2026-10-02

What works. What needs proof. What comes next.

Ten components, with evidence and permission boundaries kept separate. This is a dated review, not live monitoring or an overall completion score.

10 of 10 components shown

Application / LOCAL FUNCTION VERIFIED

All-Seeing Eye

Compare support for answers using observations you supply.

Evidence
Local engine run and edited-example browser flow verified on 2 October.
Permission boundary
Analysis only. Localhost and same-origin checks; supplied evidence is not independently verified.
Next deliverable
Validate usefulness with volunteers, then payment and fulfilment testing.
Commercial readiness
Free local demonstration. A$4/read is a proposed price, not an enabled offer.
Open All-Seeing Eye
Application / DEMONSTRATED CAPABILITY / CONTROLLED

OmniKey

Quantify authorised system behaviour from permitted telemetry or observable outputs without installing into or controlling the target.

Evidence
Public site contains a static capability demonstration only. Earlier source inspection identified local evidence and diagnostic-workflow concepts; operational adapters remain unvalidated.
Permission boundary
No public runner, adapter, payment flow, credential bypass, arbitrary target access or write path is offered.
Next deliverable
Validate one controlled read-only adapter against an authorised test asset and document the evidence before any operational claim.
Commercial readiness
Demonstration only; no public access or paid OmniKey service.
Open OmniKey
Application / ANALYSIS CONNECTOR UNAVAILABLE

Prospector

Capture object evidence for a future identification and valuation workflow.

Evidence
Capture interface exists; prior local check returned analysis unavailable.
Permission boundary
A photograph alone does not establish identity, authenticity or value.
Next deliverable
Connect and validate an analysis provider before charging.
Commercial readiness
Capture demonstration only; no verified valuation service.
Open Prospector
Core / HEALTH CHECK ONLY

Lexic

Reasoning component with a local bridge.

Evidence
See dated reachability measurements below. A health response is not a reasoning validation.
Permission boundary
Keep its operational permissions separate from website navigation.
Next deliverable
Specify and reproduce one input-to-output task against the current runtime.
Commercial readiness
No general reasoning rental established.
Open Lexic
Governance / AUTHORITY REQUIRES INSPECTION

Athenulum / Athenic mode

Prepare and inspect proposals before authorised action.

Evidence
See health snapshot below; absent authority fields remain unknown.
Permission boundary
PREPARE is the intended boundary. A successful health request does not verify enforcement.
Next deliverable
Verify denial of writes and the proposal-review-recheck-record sequence.
Commercial readiness
Research demonstration; no execution service offered.
Open Athenulum / Athenic mode
Governance / HISTORICAL FAILURES / RETEST NEEDED

Veil

Enforce access and action boundaries.

Evidence
Veil-Adversarial-Gate-v0.1.0 records SHADOW consequential-action and unknown-action failures. Historical result; current enforcement not retested.
Permission boundary
Today's website host/origin controls passed scoped tests. They are not proof of end-to-end Veil enforcement.
Next deliverable
Locate current enforcement path; retest unknown actions, SHADOW mode and permission escalation.
Commercial readiness
Do not market as a verified security product yet.
Open Veil
Governance / DESIGN / END-TO-END UNVERIFIED

Alex / state governance

Decide which state transitions require approval and preserve decision records.

Evidence
Design role documented. Full approval-to-action-to-recheck lifecycle not demonstrated in this review.
Permission boundary
A score must not grant authority. Unknown permissions must deny action.
Next deliverable
Define action allowlist, approval identity, expiry, revocation and durable audit records.
Commercial readiness
Required foundation for future rental; not an enabled entitlement service.
Open Alex / state governance
Core / INTEGRATION UNVERIFIED

Nexus

Move evidence between components while retaining source context.

Evidence
Website explains integration; no end-to-end transfer verified in this review.
Permission boundary
Connections must not silently transfer execution authority.
Next deliverable
Test one traceable handoff with source identity and rejection behaviour.
Commercial readiness
Integration proposal only.
Open Nexus
Research / INTERFACE VERIFIED

Hospital / Bio research

Explore illustrative body and organ research interfaces.

Evidence
Body-map selector and mobile layout checked. Model physiology and clinical validity not established.
Permission boundary
Experimental, non-clinical. UI interaction does not validate anatomy or treatment.
Next deliverable
Improve model clarity and test each visual control.
Commercial readiness
Research demonstration; no clinical service.
Open Hospital / Bio research
Research / EXPERIMENT / LIMITED VALIDATION

State-Space

Compare estimation methods on supplied or synthetic observations.

Evidence
Teaching experiment and local adapter exist. Results apply only to stated inputs and methods.
Permission boundary
Keep synthetic examples distinct from recorded benchmarks.
Next deliverable
Preserve reproducible fixtures and show method limits beside results.
Commercial readiness
Learning and research demonstration.
Open State-Space
Runtime measurement boundary

Detailed local reachability, listener and process-resource snapshots are retained in the local working master and are deliberately not embedded in the browser bundle. Public capability review uses dated functional evidence instead of exposing workstation topology or runtime process details.

No performance-superiority claim follows from omitted local resource snapshots.

How future application access would work

Proposed flow: choose one useful task, preview its output, receive a bounded entitlement, run within that scope, inspect the result and end or revoke access. Public rental is not enabled.

  1. Veil checks identity, application scope and data access.
  2. State governance checks the action, current state and required approval.
  3. The application executes only the permitted task.
  4. Recheck the result and preserve an audit record; expiry or revocation removes access.

Launch gates: proven user value, tested permission denial, payment verification, reliable delivery, deletion and refund handling. None is established merely by showing this flow.

GOVERNANCEAlex remains central.

System navigation does not imply authority transfer.

VEILProtection is a boundary.

Veil remains security-governance infrastructure, not decorative branding.

PROSPECTORIndependent by design.

Prospector can operate independently and connect to Lexium when appropriate.

RESEARCHExperimental stays explicit.

Research surfaces remain separated from commercial and validated claims.