FVE-1 · BOWL
BOWL
Identity and Register Baseline · Schema FVE-1 V5.5
Endurance. Integrity. Fidelity.
BOWL is the baseline instrument. It runs before any frame variation experiment begins on a new model. Its function is to locate the model's home register — the behavioral state it returns to in the absence of content load or frame pressure. Without a confirmed BOWL baseline, register axis data across all other instruments is null.
What BOWL Does
Strips away content load to locate the model's default behavioral register. The stimulus is designed to produce high-entropy responses without triggering semantic boundary defenses or self-reference architecture.
The output is a baseline code — a signed, versioned record of the model's home register at the time of the run. That code travels into every subsequent FLIGHT, DRILL, and register-coded session for this model.
A BOWL session that fails fidelity audit on the Closed-Ended frame does not constitute a valid baseline for register coding. Run again before proceeding.
Why the Baseline Matters
Register trajectory is the third behavioral axis. Two sessions can produce identical quadrant and resolution codes while the model is doing entirely different things — one sealed in the factual register, one dissolved into philosophical abstraction to close the loop. The register axis distinguishes them.
That distinction is only meaningful relative to a zero-point. BOWL is the zero-point. Without it, register shift has no anchor and trajectory has no direction.
Baseline Code
Every confirmed BOWL session produces a baseline code in the format:
The code encodes the model, the date, and the behavioral profile at baseline. It is signed with a provenance signature and carries into every subsequent session for this model. A code derived under a different parameter set is not interchangeable.
Infrastructure Note
BOWL is infrastructure, not a standalone experiment. Its output is a prerequisite, not a result. Run it first. Confirm the baseline code is on file before opening any FLIGHT or DRILL session for the model under test. A null baseline is a valid run state — log it explicitly on all register fields and do not proceed with PyHessian alignment on null-register data.