INTRODUCING // REFLEX Fine-tuning-as-runtime for production LLM agents — from rented prompts to owned weights. Read the thesis →
RESEARCH // THE THESIS

From rented prompts to owned weights.

Production LLM agents are overwhelmingly operated as prompted systems — everything the agent must reliably know is restated, and re-billed, on every call. Reflex moves that stable behavior into the weights.

Prompted agents bill you for reliability
they never quite deliver.

Two compounding structural failures — plus three operational barriers that keep teams locked out of fine-tuning.

F1 FAILURE // ECONOMIC

Linearly Scaling Token Economics

Stable prompt segments — tool schemas, formatting rules, few-shot exemplars — are re-transmitted and re-billed at input-token prices on every API call. The cost of behavioral reliability scales linearly with traffic volume.

0% of stable tokens re-billed on every call
F2 FAILURE // RELIABILITY

The Prompt Reliability Plateau

Even frontier function-calling agents succeed on under half of realistic tool-use tasks, with high inconsistency across identical trials. Beyond a threshold, more prompt engineering stops converting into format compliance.

<0% success on realistic tool-use tasks
THREE BARRIERS TO FINE-TUNING
ML Engineering Burden The Trust Gap Base-Model Obsolescence

Working Memory vs Muscle Memory

Any behavior that is stable, frequent, and verifiable should migrate from the context window into the weights — behind a strict evaluation gate.

RENTED // THE PROMPT

Working Memory

  • Re-read on every single call
  • Occupies context capacity
  • Incurs per-token billing, forever
  • Degrades silently on model upgrades
COST: LINEAR IN TRAFFIC
OWNED // THE WEIGHTS

Muscle Memory

  • Behavior encoded once, in weights
  • Zero marginal token cost to execute
  • Evaluation-gated before production
  • Regenerated by one-command retrain
COST: ZERO MARGINAL TOKENS

Measured, not marketed.

Four quantitative success criteria across design-partner deployments and benchmark validation. An open-source release of the SDK, training recipe, and evaluation gate accompanies validation.

See how the runtime operationalizes this.

The thesis is only as good as its enforcement mechanism.