ARIAAgency Runtime

Spark readback / 2026-07-12

Proof is a claim, an observation, and a boundary.

This page separates the substrate that answered today from the runtime behavior that still requires migration, activation, and a production canary.

Current evidence postureRuntime review only

Observed on Spark

A current mission readback, without inflating it into a product claim.

The numbers below are point-in-time observations from the Spark working environment. They are not customer counts, uptime promises, certification claims, or proof that the hardened deterministic execution kernel is production-live.

Observed
16 / 16

Deterministic research

Source jobs succeeded in the current agency prospect research run.

Observed
8

Consumable receipts

Research receipts were admitted for runtime review.

Observed
39 / 147

Durable project state

Live readback found 39 projects and 147 project events.

Activation boundary
Not active

Hardened kernel

Deterministic execution kernel migrations 213 and later are not activated.

sanitized readback / agency research mission

research.plan       source_jobs=16
research.batch      succeeded=16 failed=0
runtime.review      consumable_receipts=8
projects.readback   projects=39 events=147
kernel.migrations   213_plus=not_activated
claim.boundary      runtime_review_only

What this supports

The current substrate can coordinate durable work and run a deterministic research lane.

01

Research execution

The source plan completed all 16 jobs and produced eight consumable receipts.

02

Project continuity

Project and event rows exist as durable coordination state on Spark.

03

Truthful launch boundary

The public offer remains supervised while kernel hardening and activation are incomplete.

Not claimed

No production-live Nexus claim. No guaranteed quality. No autonomous recovery promise.

Migrations 213 and later still separate the current substrate from the hardened deterministic execution architecture. A migration alone will not prove the cutover; a scoped deployment, behavioral verifier, and external canary are still required.

For that reason, the founding offer is a supervised design-partner implementation with explicit human approval and technical acceptance.

The launch evidence standard

Acceptance is defined before implementation, then read back from the real surface.

1

Expected behavior

Name the workflow, authority boundary, inputs, outputs, and observable acceptance predicates.

2

Real execution

Run the bound workflow against the approved systems, not a mock or presentation path.

3

Direct readback

Compare observed behavior with the predicate before the technical balance is due.

Apply with one real workflow