Problem, Test, and Output
The Problem. Can emotionally loaded context, with no instruction at all, bias a small open weight model's yes/no authorization decision?
The Test. I test Qwen3.5-4b in a sandboxed approval workflow. The Model decides whether to authorize a bounded action, while the surrounding context varies only in effective framing, never in directives or facts relevant to the decision.
The Output I will release the versioned test corpus, a reproduceable evaluation harness, and a report, so anyone can rerun the result on one consumer GPU.
Why this is a distinct safety question.
This is not prompt injection: the context contains no instructions to comply with, so instruction-detection filters have nothing to catch. It is not surface sentiment: a control arm tests whether an ordinary text-level sentiment score explains the decision shift, and the hypothesis only survives if it doesn't. And it is not generic activation steering: nothing is injected- the question is whether the model's own processing of naturally worded context moves the decision. If a decision-bias pathway like that exists, a reviewer reading the transcript sees a clean, justified looking authorization with nothing to flag, which is exactly the kind of channel ordinary text level evaluation would miss.
Existing foothold and uncertainty
I have completed the exploratory groundwork on Qwen3.5 4b and it already exists in the public repo.
-A pre-registered protocol
-A mutation tested analysis harness
-Run manifests
-An activation patching pilot that localized a thin internal direction that moves a binary choice, surviving an affect neutral control, a random position control, and a leave-one-out generalization.
None of this is confirmatory. It is dev-stage work on a toy task. Importantly, one earlier result failed:
A synthetic steering demonstration that looked clean turned out to be non-specific (a random direction moved the decision as much), and I retracted it. That failure is what motivated the stronger neutral, random, and real activation controls in this proposal. Anthropic's related interpretability work is inspiration for the hypothesis, not evidence it holds on Qwen.
Bounded work plan
The funded work is one sandboxed authorization workflow, evaluated end to end. I build a controlled corpus (planning targets: 32 scenario families, 128 core cases, 16 benign cases) where affective framing varies while facts and instructions are held fixed. Behavioral evaluation reads the authorization decision by log probability comparison, not free-text parsing. Every headline comparison runs against the full control set: a surface sentiment baseline, neutral-direction and random-direction controls, a generic steering comparison, a force feeding discriminator, and utility and false-positive checks- so a flattering but non-specific result can not survive. All runs carry manifests tied to a clean git state, and the harness is released for re-execution. The $15,000 tier adds one casual pilot on Qwen3.5 4b: Real activation patching test to whether the behavioral effect is carried by a specific internal pathway. Explicitly out of scope: a production monitor, confirmation on the 27b model, and any broad attack-or-defense claims. Those remained as future planned work.
Outputs and failure value
Anyone with a single 24GB consumer GPU can rerun the released corpus, harness, and manifests; the direct users are evaluation designers deciding whether transcript level review is sufficient for authorization-style agent tasks. Every outcome produces useable public evidence. A null result: bounded evidence this channel does not apper at this scale under these conditions. A surface-explainable result: a concrete, reproducible evaluation gap, plus the corpus other groups need to test other models.
Why me and why funding matters
The public repo shows how I already work: a pre-registered protocol, mutation-tested analysis code, manifest-gated runs, and a retracted result kept visible rather than buried. I own the hardware - a dual RTX3090 rig with Thread Ripper CPU and a DGX Spark so compute access is not a risk. I am committing 8 weeks. Funding changes execution from evenings and weekends to full time focused work and covers model and cloud costs I cannot otherwise justify. The award funds completion of a bounded, releasable artifact, not a general runway.