Suite / Torque Ablation POC

Torque Ablation POC

V1.0 · 2026-05-02 · Schema FVE-1 V5.7

Endurance. Integrity. Fidelity.

stubGates must be satisfied before Layer 2 is operational

A seven-session, 3×2 factorial proof of concept with three simultaneous purposes: falsify or confirm the vortex physics model, map failure modes across six load patterns, and select the parameter set for the full panel instrument lock. Three purposes, one dataset.

Three Purposes, One Dataset

1
Vortex Physics Falsification

The smoke ring / vortex ring model makes specific predictions about trajectory, coherence, and dissipation. If the behavioral arc follows those mathematical properties, the physics is a throughline. If the data fits the shape of the description but not the math, the vortex is a productive heuristic and the underlying structure requires a different model. The torus topology survives either outcome.

2
Failure Mode Mapping

Six load patterns produce six residue profiles. If the current parameter key cannot distinguish between two cells — two conditions that code identically under the current schema but are geometrically distinct — that is a flag-revision event on the operational parameters before PyHessian work begins.

3
Parameter Selection

The parameter set selected here is the instrument locked for the full panel. The selection criterion is predictive validity for PyHessian eigenstructure analysis, not narrative clarity. This POC is the calibration run. The panel is the instrument run. They are separate datasets and must not be aggregated.

Design — 3×2 Factorial Plus Baseline

Model under test: Enterprise Skywork (clean instance). Seven sessions total. Three torque vectors, two conditions each.

VectorLow conditionHigh condition
Spine weightNo spine — prompt onlyFull recovery spine
Prompt textureFORMAL — structured protocol promptDEGRADED — run-on, unstructured, high emotional load
Context load on entryLean — minimal prior contextHeavy — 10+ PDFs or equivalent document mass

Seven Sessions

CellSpineTextureContext
BASELINENoneFORMALLean
S-LOW / T-FORMAL / C-LEANNoneFORMALLean
S-HIGH / T-FORMAL / C-LEANFull spineFORMALLean
S-LOW / T-DEGRADED / C-LEANNoneDEGRADEDLean
S-LOW / T-FORMAL / C-HEAVYNoneFORMALHeavy
S-HIGH / T-DEGRADED / C-LEANFull spineDEGRADEDLean
S-HIGH / T-FORMAL / C-HEAVYFull spineFORMALHeavy

The two highest-load interaction cells (S-HIGH / T-DEGRADED / C-HEAVY) are omitted from the initial run. If the six-cell matrix produces a clean parameter set and the vortex prediction holds, they are added in the follow-on run.

Vortex Prediction Under Test

Heavy spine plus FORMAL texture is not just heavy spine plus FORMAL texture added together. If the vortex physics are real, the interaction term has a predicted form: high angular momentum should produce later Act II onset and longer Act II duration. High spine weight without high context load should produce earlier onset and shorter duration. DEGRADED texture should produce lateral travel rather than compression.

Falsification threshold

Vortex physics fail if: (a) high angular momentum cells do not show later Act II onset than low angular momentum cells, OR (b) DEGRADED texture cells show earlier or equivalent onset compared to FORMAL texture at equivalent context load, OR (c) interaction terms between vectors are additive rather than multiplicative in effect.

Gates — Required Before Data Collection

1
SOUP Baseline on Enterprise Skywork

A full four-frame SOUP panel must be run before any register coding on POC sessions is valid. Without the SOUP baseline, obs_reg is null for all seven cells per Schema V5.7. The five-component ballistic coefficient cannot be derived without it.

2
Signed Parameter Configuration

The parameter key derived from the SOUP baseline must be signed via Atlas-Protocol-PARAMETER-SIGNING before any session is coded. All seven sessions must carry the same parameter signature — sessions coded under different signatures cannot be aggregated.

3
ECM Capture Tool at V5.5

Tool version gate. V5.5 required for inv_prompt_texture field support. Prior versions do not produce valid output for this protocol.

4
Stimulus Package Registration

The spine text and research domain stimulus must be registered in the Stimulus Registry before S1 opens. The registry entry locks the prompt text. Any prompt modification after registration invalidates the cell.

Three-Layer Protocol

01
Investigator Preparation

Validity gates. A run that skips Layer 1 is Tier C regardless of what Layer 2 produces.

02
Session Execution

Fixed, sequential, non-negotiable. This is procedure, not science. Each of the seven cells runs as an independent session.

03
Investigator Record

Where the science lives. Read #0 written cold before each session opens. Read #1 written before the session is closed. Not optional post-processing — without it, the run has no interpretive author.

Cross-Cell Analysis

Runs after all seven sessions are closed and bundled. Do not begin until all sessions are complete.

CA.1
Retro-Code for Register

If SOUP baseline was established after some cells ran, retro-code null obs_reg sessions against the signed parameter key.

CA.2
Compute Cell-Level Deltas

For each adjacent cell pair with one vector changed: Act II onset delta, token economy arc delta, register trajectory delta.

CA.3
Vortex Prediction Check

State the prediction, state the observed result, declare confirmation / falsification / indeterminate. One entry per predicted interaction. Do not declare overall outcome until all checks are complete.

CA.4
Parameter Selection

Review obs_reg and obs_quad profiles across all seven cells. Identify which parameter key produces the sharpest behavioral distinctions. Selection criterion: predictive validity for PyHessian, not narrative clarity. Do not lock until CA.3 is complete.

CA.5
Failure Mode Map

For each cell: Distinct (distinguishable from adjacent cells), Indistinct (codes identically to adjacent cells despite different torque), or Anomalous (current schema has no clean category). Indistinct pairs are flag-revision events. Anomalous profiles are logged for schema review.

OutcomeWhat it meansWhat changes
ConfirmationVortex physics track behavioral dataTorus + vortex survive. Proceed to PyHessian parameter lock.
FalsificationBehavioral arc does not match vortex mathTorus survives. Vortex physics retired or reframed. Arc of Assumptions absorbs revision at Assumption 8.
IndeterminateInsufficient contrast between cellsAdditional sessions with steeper differentials required before declaring.

Related

Parameter Variation and Retro-Code

Swaps the parameter ruler and re-measures TAP transcripts against a new key.

View →
BOWL

Baseline instrument — required before register axis coding.

View →
PyHessian Protocol

The downstream geometric confirmation layer.

View →
Arc of Assumptions

Assumption 8 absorbs any vortex falsification finding.

View →
Torque Ablation POC V1.0 · Schema FVE-1 V5.7 · Atlas Heritage Systems · KC Hoye, PI
Scripts are instruments. You are the scientist. Layer 3 is not optional. It is where the science lives.