Skip to content

Section 2 identity-eviction hypothesis tested: prefixing the trained identity does NOT reopen the gate (0/40); any ~30-token tail text does, on both quant builds #18

Description

@Blackwellboy

A community-reported wire-level result proposed that the Laguna thinking collapse under long system prompts is a pure prefix prior: any caller system prompt evicts the template's trained default identity, and restoring that identity as the literal first line restores thinking (reported 6 to 7 of 8 under a 40K agent prompt that fired 0/8 bare). Since every condition in the C0-C9 grid that section 2 is built on replaced the default identity by construction, the two accounts (instruction dose vs identity eviction) were confounded in our published data. We unconfounded them.

Setup. Laguna S 2.1 3.25bpw hybrid (vLLM, poolside_v1 parser) as the gated model; Qwen3.6-35B-A3B NVFP4 as the ungated control. C6 (10-rule block, our published 3/40 crater) and C7 (full agent prompt, 24/40) byte-identical from the gate-study driver; four variants each: as-published, trained identity prepended as the literal first line, identity appended at the end, identity present but spliced mid-sentence. The identity string was taken verbatim from the serving checkpoint's chat_template.jinja default system message (byte-identical between the hybrid and NVFP4 checkpoints). 4 task types x 10 samples per cell = 320 turns/lane, single-turn throughout (so the #16 history-rendering mechanism cannot be a confound), thinking enabled, ceiling 4096, model-card sampling. 0 transport errors.

Result (Laguna, fired / 40):

variant C6 C7
published 5 17
identity prefix 0 17
identity suffix 18 24
identity spliced 2 20

Qwen control: 320/320 fired regardless of variant, so there is no general prefix-prior effect of this text on an ungated model.

Reading.

  1. On this build the prefix-prior account fails at its critical cell: identity-first ahead of C6 fired 0/40 (directionally worse than published, p about 0.055), and C7 was unmoved (17 to 17). The firing-axis numbers the rebuilt section 2 (merged in Laguna §2: the thinking gate is two axes, not one dose curve (closes #11) #12) is built on are unaffected. The community effect looks stack-specific (different CLI/proxy path, vLLM 0.25.1, NVFP4-TP1/FP8-TP2), and that report itself found FP8 and NVFP4 have different thinking policies, so build/quant scoping belongs next to any section 2 citation; ours is a third build.
  2. New nuance we did not predict, now replicated interleaved on BOTH quant builds: a tail effect that is POSITION-GENERIC, not identity-specific. In the first (blocked) run the identity text at the END of C6 tripled firing (5/40 to 18/40). A dedicated interleaved control (4 variants x 4 tasks x 10 samples, per-quartet shuffled order, token-band-matched suffixes) then showed ANY matched tail text does the same: bare C6 0/40 vs identity-suffix 13/40, neutral filler 14/40, topical text 10/40 (every suffix vs bare p <= 0.001; identity vs neutral p = 1.0; pooled any-suffix vs bare p = 6.0e-06). The same interleaved design then replicated on the NVFP4 build, the build the section 2 curve was measured on, with byte-identical filler strings, re-token-matched on that tokenizer: bare 2/40 vs identity 17/40 / neutral 10/40 / topical 11/40 (every suffix vs bare p <= 0.025; identity vs either filler NS at n=40), and the bare cell replicates the published 3/40 crater (p = 1). Restoration magnitudes match across builds almost exactly (identity tail 17 vs 18 per 40, p = 1). Same instruction dose, ~30 extra tokens of anything. Dose remains the primary axis; system-prompt tail composition is a real secondary axis on this family, and the identity text carries no special weight in it on either build.
  3. Template mechanics worth a section 2 footnote either way: any caller system message replaces the trained default identity, and an explicitly empty system message opts out of the default entirely. So "no system prompt" and "any system prompt" differ by more than instruction content on every stack.

A synthesis point for the two-axis model. The C7 identity arms are the second independent case of an intervention raising or holding firing while suppressing depth. Identity presence at C7 held firing flat or up (17/40 published, 17 to 24/40 across the identity arms) while collapsing fired-turn depth from a median of 1080 reasoning tokens to 120 to 200; the tools result had the same shape (C7 to C8: firing 60 to 72 percent, median tokens 745 to 282). Two unrelated interventions now move the two axes in opposite directions, which we read as independent confirmation that the two-axis decomposition section 2 was rebuilt on (whether it fires versus how deep it goes) is the right one; a single dose axis cannot produce either datapoint. The tail-composition controls add a softer third instance of the same dissociation: with firing statistically flat across the three matched suffixes, the identity suffix produced the shallowest fired turns relative to neutral filler on both builds (median 656 vs 809 reasoning tokens on the hybrid, 573 vs 782.5 on NVFP4), so identity text again trades depth away without buying firing. Caveats stated plainly: fired n per cell is 10 to 17, the comparison was not preregistered, and the topical suffix does not hold a consistent ordering across builds (1015 on hybrid, 391 on NVFP4), so we offer this as a consistent direction on the identity-versus-neutral contrast, not a third confirmed case at the strength of the first two.

Raw JSONL, drivers, and writeups: https://github.com/Blackwellboy/laguna-s21-lab/tree/main/identity-prefix (n=640 main grid, n=320 hybrid interleaved suffix control, n=160 NVFP4 interleaved replication; per-turn firing/reasoning-tokens/finish-path logged; three-way cross-build table in the study doc). Latency fields in the main-grid raw logs are flagged polluted (a concurrent study shared the lanes at low concurrency); both interleaved controls ran on idle/exclusive lanes; firing counts are unaffected throughout.

Credit for the originating observation: reported publicly on X; cited as community-reported here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions