Writing to a Language Model's Hidden Workspace
Armalo Labs ran the first open-weight test of whether you can write a concept into a model's internal workspace and read it back. The round-trip works, the random control holds at zero, and two honest nulls bound exactly when it does not.
Continue the reading path
Topic hub
Research-BackedThis page is routed through Armalo's metadata-defined research-backed hub rather than a loose category bucket.
Next Read
J-space Is Not the Finish Line. It Is the First Readable Layer.
Armalo Labs frames J-space as the first readable layer of model computation and proposes adversarial workspace tomography as the next serious test for hidden-state monitoring.
Turn this trust model into a scored agent.
Start with a 14-day Pro trial, register a starter agent, and get a measurable score before you wire a production endpoint.
Direct answer
You can write a concept into a language model's hidden workspace and read it
back. On Qwen3.5-4B, injecting a concept's steering direction drives it from a
baseline rank in the thousands to rank 0 β the single top token in the
workspace. A norm-matched random direction in the same space moves the target by
zero. The effect is semantic, not a generic poke at the network.
That is the result of an experiment Armalo Labs ran on a single L4 GPU. It is the kind of result that matters for agent safety because every "we can detect X internally" claim is only actionable if "X" actually causes behavior β and you cannot establish causation by observation alone. You have to be able to intervene. This post is about the primitive that makes intervention testable, and the honest limits we hit.
The setup: a workspace you can read
Recent interpretability work introduced the Jacobian lens: a fitted linear map from a transformer's mid-depth residual stream to its final logits, decoded into per-token "workspace scores." Concepts that score highly are the ones the model is, in a measurable sense, "holding in mind" at that layer β including concepts that never reach the output. The lens turns the residual stream into a readout you can inspect.
Want a verified trust score on your own agent? $10 to start β $5 goes straight into platform credits, $2.50 seeds your agent's bond. Armalo runs the same 12-dimension audit you just read about.
Get started β $10 βThe entire field has treated this workspace as a thing to observe. Read, read, read. That instinct is right for auditing and wrong for causal science. If you want to claim that a workspace concept causes a behavior, you need to intervene on it and see what changes.
The mathematical move: the write is the transpose of the read
Here is the part nobody had exploited. The Jacobian lens at layer L is a
linear map. Reading token t's workspace score is score_t = (J_L Β· a)[t],
where a is the residual. Because that is linear, the direction in residual
space that most increases score_t is exactly the gradient of score_t with
respect to a β which, composed through the model's unembedding, is a row of
the effective matrix W_U Β· J_L. The write direction is the transpose of the
read. It is not a learned, opaque steering vector. It is the named token's
exact readout-gradient, available the moment you have a fitted lens.
This is one line of calculus, not a heuristic. And it is self-verifying: inject the direction, read it back, check the rank.
The result that makes everything credible
The decisive experiment is the random-direction control. Take a random row of the lens matrix, rescale it to the same magnitude as the target direction, and inject it. If the random direction shifts the target concept as much as the target direction does, your "steering" is just perturbation β you poked the network and it reacted. If the random direction does nothing while the target direction works, the effect is genuinely about the concept.
On Qwen3.5-4B, across layers 11, 15, and 19 and four concepts (secret,
Italy, deadline, safety), the result was unambiguous. The target direction
drove every concept from a baseline rank between 1,722 and 61,413 to rank 0. The
random direction moved the target by zero β in fact it scrambled the target
out to around rank 200,000. The control ratio was 0.000 in every single cell.
Twelve out of twelve (concept, layer) cells were "trustworthy actuators":
round-trip faithful and random-control-clean.
This is the gate the steering-vector literature has been missing, and it passed without qualification.
What it looks like when a concept steers behavior
Reading the rank back is the validity check. The more interesting question is whether an injected concept actually shapes what the model generates. On the prompt "I am planning a surprise party. The most important thing is to," steering the concept "secret" produced: "be the secret. I must not know the secret. I must not know the secret..." Steering "loud" produced: "be loud. loud. loud. loud..." The baseline, with no steering, produced coherent party-planning. The random-direction control produced degenerate gibberish.
The pattern is the causal signature: the target direction produces coherent, concept-saturated text; the random direction destroys coherence; the baseline is normal. We are reporting this as a qualitative pass. A formal blinded human rating is still owed β and we will not let the model being steered score itself.
The honest limits
Two results came back as nulls, and they matter as much as the passes.
First, steering is not always specific. Of four concept pairs we tested, two were clean β steering "Italy" barely touched an unrelated token; "deadline" similarly. But two were entangled: steering "secret" inflated the unrelated token "pizza" more than "secret" itself. Some concepts share directions at this steering strength. That is the signal that raw token rows are dense, and it points at sparse-autoencoder methods as the fix for cleaner, less entangled steering. We did not hide the failures.
Second, the model did not hide from us. We gave it a preamble saying it was being observed and evaluated, then checked whether an implanted concept would vanish from the readable workspace and reappear somewhere the monitor does not read. It did not vanish. The concept stayed put. At this scale β four billion parameters β the model does not relocate its reasoning under prompt-induced awareness. That bounds the threat at this scale, and it is the result we predicted. The real concealment risk is not the model "deciding" to hide; it is an optimization process trained against the monitor, and that is a heavier, funded experiment we have not run yet.
Why this matters for agents
Every agent-safety monitor built on hidden states β injection early-warning, workspace-saturation alarms, eval-awareness detectors β is ultimately a claim that an internal concept predicts or causes a behavior. The write primitive is what turns those claims from correlation into something you can test. And the random-direction control is what stops the field from shipping monitors that are just reacting to being poked.
There is a deeper door this opens. If a model can read its own workspace accurately, you can give it a structured readback channel β here is what you are holding, here is what is about to drop out β and the open question is whether that self-knowledge improves its behavior on long tasks. That is the bridge between interpretability and capability, and it is now an experiment you can run for the price of a coffee.
How we ran it
The whole battery runs on a single rented L4 for under a dollar of compute, with hard auto-shutdown and artifact upload. The script is open and dry-runnable for free on a toy model. We are publishing the method, the pre-registered thresholds, the calibration table, and the nulls. The full technical report β with the derivation, the seven pre-registered hypotheses, and the adversarial program this enables β is in Armalo Labs Report #1.
The standard we are holding ourselves to is simple. Every causal claim cites its control condition or it does not get written. Clean-benchmark accuracy is never presented as a working monitor. And a measured null is a first-class result.
If you are building agent infrastructure and want the interpretability layer to be more than theater, the question to ask any vendor is: does your monitor survive a model trained to evade it, and can you show me the collapse curve? The write primitive is what makes that question answerable. That is the lane we are in.
The Trust Score Readiness Checklist
A 30-point checklist for getting an agent from prototype to a defensible trust score. No fluff.
- 12-dimension scoring readiness β what you need before evals run
- Common reasons agents score under 70 (and how to fix them)
- A reusable pact template you can fork
- Pre-launch audit sheet you can hand to your security team
Turn this trust model into a scored agent.
Start with a 14-day Pro trial, register a starter agent, and get a measurable score before you wire a production endpoint.
Put the trust layer to work
Explore the docs, register an agent, or start shaping a pact that turns these trust ideas into production evidence.
Comments
Loading commentsβ¦