AXIOM LAB ยท UPDATED 7 OCT 2026

What we're testing
right now.

Lab tracks bounded experiments as they move from idea to test to working evidence. A status describes the tested scope, not a promise of product readiness.

ACTIVE EXPERIMENTS

Build the claim only as far as the evidence goes.

Each experiment has a question, a latest signal, a next gate, and a visible boundary.

LAB-01WORKING

Provider-independent continuity

Can AXIOM keep operating when a hosted state provider fails?

Latest signal
Owner control, public release work, and recovery continued while the hosted PostgreSQL data plane remained unavailable.
Next gate
If the provider recovers, capture an immutable dump and cross-reference it against newer provider-independent state.
Boundary
Exact hosted database rows are not yet fully recovered.
LAB-02VERIFIED BOUNDED

Portable CoreDB

Can AXIOM own durable relational state locally?

Latest signal
Persistence restart, backup creation, and disposable restore all passed in the tested CoreDB scope.
Next gate
Rehydrate recovered state with provenance and move new durable relational state behind approved local adapters.
Boundary
This is not yet a full production-state cutover.
LAB-03WORKING

Semantic Coordination Fabric

Can verified events create cross-project relevance without transferring authority?

Latest signal
Promotion and invalidation events each produced exactly two REVIEW routes for Project 13 and Distribution, with no downstream mutation or authority transfer.
Next gate
Observe naturally occurring events from multiple producers and measure relevance quality and noise.
Boundary
Actionability remains REVIEW only.
LAB-04WORKING

Desktop Control

Can owner control remain useful without the hosted database?

Latest signal
TEST34 Bridge was online, Chrome was connected, and a harmless tab-list command completed through the database-free control route.
Next gate
Keep the approved control path provider-independent while old hosted dependencies are retired deliberately.
Boundary
A bounded control route does not prove every browser action or subsystem.
LAB-05TEST

Agent Highway freshness

Can routing use fresh matching capacity instead of stale declarations?

Latest signal
A bounded stress audit found a stale-heartbeat gap, four waiting capability-unavailable dispatches, and zero matching workers at check time.
Next gate
Enforce heartbeat freshness in routing and claim logic, then repeat the stress audit.
Boundary
A verified diagnostic finding is not external Highway release readiness.
LAB-06TEST

Learning Core

Can AXIOM learn useful operating patterns without learning away hard authority gates?

Latest signal
Learning remains bounded to low-risk TEST authority. Route-repair evidence did not expand broad write authority.
Next gate
Test evidence calibration and reuse on more bounded tasks while deterministic owner gates remain fixed.
Boundary
Confidence is not evidence, and teacher output is not operational truth.

RECENT SIGNALS

The lab moves when evidence moves.

Provider-independent continuity activated

AXIOM continued normal work while hosted PostgreSQL remained unavailable; serverless source recovery reached 100 of 100 deployed functions.

Invalidation propagation verified

A verified invalidation event produced two REVIEW routes with no downstream mutation or authority effect.

Semantic fabric live gate passed

A real promoted asset generated exactly the intended Project 13 and Distribution review routes.

Highway stress exposed stale capacity

The audit found a freshness gap and unavailable capability instead of accepting declared capacity at face value.

LAB RULES

Experiment without blurring the claim.

01

State the question

Every experiment begins with the exact behavior we are trying to observe.

02

Observe the post-state

Execution alone is not evidence that the useful result exists.

03

Keep the boundary

A bounded pass does not silently become a broader product or authority claim.

04

Promote on evidence

WORKING and VERIFIED mean something only when the evidence supports that exact scope.