Public research note

Observable Spectral Dynamics in a Recurrent Sequence Model

This note describes what we can publicly disclose about Project SLSSM-01: the research question, the evidence gathered from the v3 short-context run, and the diagnostic vocabulary used to study the model. Implementation details, weights, and the training recipe are outside the public disclosure boundary.

Version 0.1 Public research summary Prepared for credibility review

Abstract

Project SLSSM-01 studies recurrent language models with inspectable spectral dynamics, using state evolution rather than quadratic self-attention as the primary sequence mechanism. The central idea is that a sequence model can be studied through its learned dynamical structure as well as through loss curves and generated text.

We report evidence from the v3 short-context run: stable training across 250,000 steps, roughly 32.8 billion processed tokens, improving loss, persistent signed phase populations, and close agreement between measured trajectory behavior and learned spectral structure. We also report a limitation: the short-context run did not build a large long-memory mode population, motivating the next long-context experiment.

Model Class

Project SLSSM-01 is best described publicly as a stable linear spectral state-space language model. In practical terms, that means the model is built around a stable linear recurrent dynamics core whose internal behavior can be studied as learned modes.

That does not mean the entire system is linear end to end. Language enters and leaves the dynamics through learned nonlinear components. The important distinction is that the core state evolution is stable and mode-structured, which is what makes the Spectral Atlas, Extended Dynamic Mode Decomposition (EDMD) Concordance, and Prompt Manifold analysis possible.

Public Spec Sheet

The following specifications are intentionally high-level. They are enough to orient a technical reader without disclosing implementation details.

Class

Stable linear spectral state-space language model

Mode-structured recurrent dynamics are the analyzable core.

Scale

360M-class research model

Large enough to test training dynamics, small enough to iterate and inspect.

Sequence mechanism

Recurrent/spectral core

Designed around state evolution rather than a transformer self-attention stack as the primary mechanism.

Training run

250k steps, 32.8B tokens

Rounded summary from the v3 short-context run.

Hardware

Single A100-class run

The analyzed run was practical at research scale rather than requiring a large cluster.

Evidence

Loss, EDMD, mode, prompt probes

Analysis used multiple views instead of relying on one curve or one generation sample.

What Is Being Claimed

The claim is deliberately narrow:

  • A stable linear spectral state-space language model was trained and analyzed.
  • Its internal dynamics were measurable enough to track across checkpoints.
  • Signed phase behavior remained present rather than collapsing into a single direction.
  • Trajectory-based analysis and learned spectral structure showed stable agreement after early training.
  • The analysis exposed a concrete next problem: long-memory capacity.

This is not a claim that Project SLSSM-01 replaces transformers, solves interpretability, or discloses a reproducible open architecture.

Diagnostic Vocabulary

Spectral Atlas

A map of learned mode families and their movement across training checkpoints. The public visualization uses synthetic data to explain the idea without exposing raw internal state.

EDMD Concordance

A comparison between measured trajectory dynamics and learned internal structure. Public summaries show aggregate agreement, not the implementation-specific transformation path.

Prompt Manifold

A prompt-conditioned view of mode usage. Public examples use labeled synthetic token paths to show the concept without exposing actual activations.

Spectral Convergence Signal

A training-time signal used to reason about changing mode pressure and stabilization. Public discussion stays qualitative.

Public Evidence Summary

Checkpoint Tokens Best loss Validation mean EDMD mean distance Interpretation
30k 3.9B 4.03 3.91 0.0113 early organization
102k 13.4B 3.38 3.40 0.0079 agreement tightened
204k 26.7B 3.24 3.28 0.0077 stable dynamics
250k 32.8B 3.16 3.27 0.0078 short-context finish

The numbers are rounded public summaries. They are included to show that the work is anchored in an actual training run, not only in diagrams or theory.

Evidence Guide

This is author-reported evidence from one analyzed training run. Values are rounded, the public record does not include uncertainty intervals, and no external replication is claimed. The CSV below mirrors the displayed tables so readers can inspect or plot the released summary without transcribing it.

Download rounded checkpoint CSV

Blank retention or rotation fields in the CSV mean that those summaries are not included in the rounded public record for that checkpoint; they should not be interpreted as zero.

The measurement method itself can be checked without trusting this model: a reproducible EDMD demonstration on public Pythia-14m training checkpoints, with a pre-specified protocol, dated post-run amendments, pinned model commits, and shuffled-pairing and persistence controls, runs on an ordinary CPU in seconds.

Run the public demo on GitHub

Best loss

The lowest rounded training objective reported by the stated checkpoint. It is not a cross-model benchmark.

Validation mean

The rounded mean objective from the checkpoint validation probe; the final probe used twenty batches.

EDMD distance

Nearest-distance summary between trajectory-derived modes and learned spectral structure under a fixed analysis transform. Lower is closer.

Retention counts

Mode counts in fixed internal high- and very-high-retention bands. The public record releases counts, not raw modes or threshold mechanics.

Signed phase counts

Final-checkpoint mode populations grouped by negative or positive rotation direction.

Prompt scores

Normalized internal descriptors for comparing probes within this analysis. They are not standardized external evaluation scores.

What would weaken this interpretation?

  • A checkpoint audit that fails to reproduce the released rounded loss, validation, or population summaries.
  • EDMD proximity that disappears under held-out trajectories, repeat runs, or appropriate control comparisons.
  • Signed phase balance that collapses on replication or proves unrelated to measurable behavior.
  • A targeted long-context run that increases neither long-memory mode population nor held-out long-context performance.

Stronger support would require repeat seeds, controlled ablations, external evaluation, and a reproducible public demonstration of the analysis method. Those tests are validation targets, not completed claims.

Observed Analysis Record

The v3 short-context run was examined from several independent angles. The purpose was not only to ask whether loss improved, but whether the model's internal dynamics could be measured and used to make a concrete next training decision.

Training

Loss moved while validation stayed coherent

Best observed loss moved from about 4.03 at 30k steps to about 3.16 at 250k steps. The final validation probe averaged about 3.27 across twenty batches.

Concordance

Trajectory dynamics stayed close to learned structure

Mean nearest EDMD distance improved from about 0.0113 at 30k to about 0.0078 at the final checkpoint, with the median staying near 0.0071 late in training.

Phase

Signed phase did not collapse

The final checkpoint retained both negative and positive rotation populations. Public counts are rounded in interpretation, but the two directions remained broadly balanced.

Prompt use

Prompts produced different spectral fingerprints

Math, code, story, and long-memory probes produced distinct aggregate profiles across amplitude, rotation, spread, slow-mode use, and coherence.

EDMD Concordance Details

EDMD-style analysis was used as an external measurement of trajectory behavior. The important observation is that the measured trajectory structure stayed close to the learned spectral structure after the early checkpoint.

Checkpoint Mean distance Median distance 90th percentile Public read
30k 0.0113 0.0103 0.0187 early alignment
102k 0.0079 0.0069 0.0138 alignment tightened
204k 0.0077 0.0071 0.0131 stable agreement
250k 0.0078 0.0071 0.0134 agreement held

The public record does not include the analysis transform or model internals. It reports the observed relationship: measured dynamics and learned spectral structure were close enough to compare over training.

Mode Population Observations

The mode population did not behave like an unstructured black box. The final checkpoint showed a strong middle-retention population, active rotation, and a smaller slow-mode population. That finding matters because it explains why the next experiment should focus on long-context memory rather than simply continuing to celebrate short-context loss.

Measure 30k 204k 250k Interpretation
High-retention modes 2 2 6 small but measurable slow population
Very-high-retention modes 0 1 1 not enough long-memory mass yet
High-rotation modes 470 733 638 phase-active dynamics remained present
Max measured half-life 12.7 16.8 16.2 short-context behavior dominated

Prompt Manifold Observations

Prompt-manifold analysis tested whether different prompts left different spectral signatures. The public version reports only aggregate descriptors, not prompt activations, mode IDs, or raw token traces.

Probe Tokens Amplitude Rotation Spread Public read
math explanation 22 0.83 0.97 0.88 broad analytical trace
code probe 19 0.87 0.98 0.86 high-amplitude structured trace
story probe 20 0.82 0.89 0.85 lower-rotation narrative trace
long-memory probe 40 0.87 0.98 0.88 strong activity, limited true long-memory use

The useful conclusion is not that one prompt "wins." The useful conclusion is that prompts can be compared as paths through spectral behavior, giving a practical way to inspect generation beyond reading text output alone.

Interpretation

The v3 short-context run provides evidence that the model can train stably while preserving signed spectral structure. The EDMD agreement is important because it gives an independent check against the model's learned internal organization. The prompt-manifold work is important because it turns model behavior into a path through mode neighborhoods rather than a single opaque output.

The most useful result is not that any one metric is final. The useful result is that the model produced measurable internal structure that can guide the next experiment.

Limitation Found

The short-context run did not produce a large population of very long-memory modes. That is not hidden in this note, because it is one of the strongest reasons the analysis matters. The diagnostics did not merely celebrate a result; they identified what the next run needs to target.

The next research direction is a long-context version that preserves the useful short-context behavior while deliberately training stronger long-memory dynamics.

Skeptic FAQ

Is this just a visualization of a model, not evidence?

The public atlas visualization is synthetic, but the evidence tables are rounded summaries from the analyzed v3 short-context run. The distinction is intentional: public visuals explain the method; public evidence reports aggregate observations from the real run.

Are you claiming state-of-the-art language modeling performance?

No. The public claim is not benchmark dominance. The claim is that a stable linear spectral state-space language model was trained and that its internal dynamics were observable enough to compare across checkpoints and guide the next experiment.

Is the model really linear?

The full system is not linear end to end. The public description is precise: Project SLSSM-01 has a stable linear recurrent dynamics core, surrounded by learned nonlinear token drive, gating, and readout. The linear core is what makes the mode analysis meaningful.

Could the EDMD agreement be accidental?

It could be overstated if treated alone. That is why the note pairs it with other evidence: loss movement, validation probes, signed phase preservation, mode population tracking, and prompt-manifold behavior. The stronger claim is convergence across multiple diagnostics, not one isolated plot.

Why not publish the code and weights?

The public release is the evidence, vocabulary, and analysis framing. Implementation, weights, initialization mechanics, kernels, and the training recipe are not part of this release.

Why use the name Project SLSSM-01?

It is a provisional public codename based on the model class: stable linear spectral state-space model. It avoids relying on a potentially crowded public mark while the research identity, legal naming, and any future company or product branding remain unresolved.

What would count as stronger proof?

Stronger public proof would include controlled ablations, external evaluation, reproducible toy demonstrations of the analysis method, and a long-context run showing that the identified memory limitation can be deliberately improved.

One item on that list now exists: a reproducible EDMD demonstration on public Pythia-14m checkpoints, with an author-reported, pre-specified protocol with dated post-run amendments, shuffled-pairing and persistence controls, and pinned model commits. It validates the measurement method on a public model; it does not validate this model's claims.

Disclosure Boundary

This public note does not disclose:

  • source code
  • model weights or checkpoints
  • training notebooks
  • architecture equations
  • initialization mechanics
  • optimizer internals
  • raw activations or raw mode tables
  • kernel or implementation details

How To Cite

Suggested citation for public discussion:

Hunt, F., & Hunt, J. (2026). Observable Spectral Dynamics in a Recurrent Sequence Model. Project SLSSM-01. research-note.html

BibTeX:

@misc{hunt2026observable,
  title = {Observable Spectral Dynamics in a Recurrent Sequence Model},
  author = {Hunt, Freddie and Hunt, Joshua},
  year = {2026},
  url = {research-note.html},
  note = {Public research note, version 0.1}
}