BEYOND THE OUTPUT

Intelligence
leaves a trace.

An answer is only the surface.
Explore the computation underneath.

ATLAS captures model execution on our own K3 research runtime and has published eleven measured findings from it. Shadow State is our next step: a one-way window into the running model.

Eleven measured findings published. Runtime layer in development.
SCROLL TO LOOK CLOSERORBITAL ARTWORK MEASURED RESULTS BELOW
01 / THE FOUNDATION

Not just what
it says.
What it computes.

ATLAS gives captured model execution a structure. Tokens, depth, routes and retained internal states become connected observations—and measured results.

Meet the capture platform
02 / THE COMMON COORDINATE

A trace.
Not a pile
of tensors.

One index connects the record: a run, a token, a layer, an operator. Capture coverage and retained evidence stay part of the story.

Explore the measured depths
03 / THE NEXT LAYER

Inside the model.
Outside its
memory.

Shadow State is being designed to stream selected internal observations to an external observer. A one-way path out. No shadow memory fed back in.

Explore the runtime direction
THE ATLAS CAPTURE SURFACE

The answer has layers.
So does the evidence.

Different observations answer different questions. Explore what the capture pipeline records, what has been measured from it, and where the boundaries remain.

EXECUTION CONTEXTResearch captures

The sequence, not just the answer.

Follow captured prompt and generated-token sequences through indexed model execution. Keep positions, model identity and capture context attached to the observations.

  • Prompt and generated-token records
  • Token, sequence and layer alignment
  • Capture configuration and run identity
THE BOUNDARY

Generated text is an output record, not guaranteed access to a model’s private reasoning. Historical short-prompt runs were capped at 32 generated tokens.

Coverage is model-, configuration- and publication-dependent.See what was measured ↗  ·  Read the full capture notes ↗
HIGHLIGHT · LOCATE · TRACE

Point at a phrase.
Follow it into the state.

Select a word or phrase in a captured prompt. Shadow State maps it to the token positions it covers, opens the residual measurements recorded for those positions at every captured depth, and exports the trace with its source metadata.

CAPTURED PROMPT · SAMPLE · GPU KERNELSPREFILL STATE · READ-ONLY

Write a CUDA kernel for a tiled matrix multiply that stages both operands in shared memory. Explain the bank-conflict risk in the inner loop and how coalesced loads avoid it.

Drag to select, or press a word.
RECORDED TOKEN POSITIONS · SAMPLE SPLIT
RECORDED STATE · RESIDUAL STREAMNO SELECTION

Highlight a word or phrase in the prompt to locate its recorded token positions.

THE EXPORT CARRIES
  • Selected text and token positions
  • Captured rows at each depth
  • Chart and source metadata
STATED LIMITS

This view’s credibility rests on saying these before anyone asks.

  • Prefill only: it inspects captured input states and does not start a new capture or follow the phrase into generated text.
  • Coverage is whatever the capture stored; a gap stays a gap.
  • Vector previews show the first 32 components; the RMS figure uses the full stored vector.
  • Charts and exports cover the current results page, not the whole capture.
  • Association, not causation: recorded state at these positions does not show the phrase influenced the answer.
  • K3 captures with recorded input token positions only.
  • Reads captures; not yet connected to Shadow State live streams.
MEASURED · DEPTH EXPLORER

One coordinate.
Four measured signals.

Move through the captured depth of the K3 research runtime. Select a depth, switch the signal, and read the published value at that coordinate—each a fraction of instrumented depth or a ratio against a stated baseline.

ATLAS / DEPTH EXPLORERMEASURED · ONE CAPTURE SERIES · NOT YET REPLICATED
4 SIGNALS × 92 CAPTURED DEPTHS
SIGNAL ↓SELECT A DEPTH TO INSPECT
DEPTH → (FRACTION OF INSTRUMENTED DEPTH)LOW HIGH (each signal scaled to its own range)
atlas/cross-domain-routing-series/depth-0.505/expert_reuse

Every cell is a published aggregate from one capture series on the instrumented K3 runtime. Depth is a fraction of the instrumented depth; magnitudes are ratios against stated baselines. Blank cells are depths a companion experiment did not sample. No token-level rows, weights or index layouts are published.

SHADOW STATE / IN DEVELOPMENT

A window.
Not a way back in.

The runtime direction: selected model observations leave through an indexed stream. Storage and analysis stay outside the model’s accessible context.

01 / COMPUTE

The model

Normal model-owned
execution and state.

02 / EXTRACT

Shadow State

Selected observations.
External, indexed stream.

03 / INVESTIGATE

The observer

Archive, inspect and
evaluate monitoring.

One-way by design. No Shadow State fed into model attention. Non-interference, capture overhead and isolation need validation in each runtime.

TWO RESOLUTIONS. ONE RESEARCH DIRECTION.

From a signal
to the surrounding evidence.

A compact, continuous view of selected observations. Intended for baseline comparisons and escalation to richer capture.

DESIGN DIRECTION · NOT A SHIPPING TIER
COMPACT OBSERVATIONSILLUSTRATION
THE RUNTIME / OUR OWN STACK

K3 runs on a runtime
we wrote ourselves.

Capture at this depth needs control of every boundary, so K3 does not run on a public inference framework. Its weights are converted into our own proprietary format and the model is streamed from local NVMe on a single DGX system, with the capture hooks in the execution path rather than bolted on.

It is a research runtime tuned for observation, not a serving stack tuned for speed. The throughput is published so the trade is visible: everything on the findings page was captured at this pace.

Runtime access notes
WEIGHTSProprietary format

Converted from the source checkpoint into our own layout.

STORAGEStreamed from NVMe

The model is streamed from local NVMe rather than held fully resident.

HARDWAREOne DGX

A single system. No cluster, no hosted API, no public inference framework.

THROUGHPUT≈0.4 / 0.6 tok/s

Generation in bf16 and int8 respectively on that single system.

RESEARCH BEFORE RHETORIC

Ambition is not evidence.
We keep them separate.

ATLAS has a measured model-capture research record. Shadow State extends that work toward runtime observability. The next step is replication and validation—not a stronger promise.

320 prompts

Ten domains, thirty-two each, in the published capture series.

29.4% reuse

Of the previous token’s experts re-activated, against 1.8% chance.

13% of layers

Hold 90% of the backward-pass gradient energy.

Measured on the instrumented K3 research runtime in one capture series, with the control and caveat stated per finding. Single-model, single-capture until replicated; not an independent audit or a security benchmark. Read the eleven findings ↗

MEASURED

Eleven findings
from one capture.

Routing breadth, expert reuse, backward concentration, attention provenance, recall collapse and the depth rewrite—each with its control and caveat.

Read the findings
IN DEVELOPMENT

The runtime
observability layer.

Model-wide Shadow State extraction, bounded streaming and complete live agent lifecycle integration.

View development boundaries
TO BE VALIDATED

Monitoring that
earns its conclusions.

Outlier detection, pre-action warning, intervention and alignment feedback remain research questions.

Read the open questions
LOOK CLOSER

Good questions.
Clear boundaries.

Read the research notes
THE NEXT QUESTION IS INSIDE

Don’t stop
at the answer.

Start with a model, a question, and the evidence
you would need to trust the result.

Read the public platform notes ↗
A GOOD QUESTION IS A START

What would you
like to observe?

Tell us about the model, the runtime and the question. Sending delivers the brief to Shadow State Labs by email; you can also keep a local copy.

Sending emails the brief to Shadow State Labs. The website server keeps no copy. Please keep secrets, private captures and credentials out of the form.