Anti-Circularity Checklist for F_boundary Simulation
The Swygert Theory of Everything AO (TSTOEAO)
DOI: To be assigned
John Swygert
May 24, 2026
Abstract
The F-Factor Simulation Protocol and the Parameter Collapse and Sensitivity Stability Protocol established the simulation pathway and evaluation standards for the TSTOEAO-specific enhancement term F_boundary. This technical addendum provides a concise, mandatory Anti-Circularity Checklist that must be applied to every F_boundary simulation run and reported result.
Its purpose is to prevent the most dangerous failure mode in the F-factor work: using the desired outcome — Γ ≥ 167, B_F ≈ 600, or a favorable h_min result — to retroactively define or tune the very parameters that are supposed to predict it. The checklist enforces a strict logical sequence: define the model first, compute F_boundary second, derive Γ and h_min third, and only then compare the output to the original 167X prediction.
No claim is made that any simulation has yet passed this checklist. The purpose is to enforce honest constraint before any simulation result is treated as supportive.
1. Purpose of This Addendum
Circular reasoning can make a simulation appear successful while teaching nothing.
The 167X F-factor work faces this risk directly because the enhancement factor F is both essential and unresolved. If F_boundary is allowed to float freely until Γ reaches 167, then the simulation has not predicted the threshold. It has merely chosen the threshold.
This addendum prevents that failure mode by requiring every simulation to follow a declared order of operations:
- define FEM variables;
- select Ψ(η);
- compute B_F;
- compute F_boundary;
- compute F_total;
- compute Γ;
- compute h_min;
- only then compare the result to the target prediction.
Any deviation from this order must be explicitly flagged.
This checklist must be applied and reported for every F_boundary simulation result.
2. Core Anti-Circularity Principle
The invalid reasoning pattern is:
F_boundary is large because Γ ≥ 167 is required; therefore Γ ≥ 167 is reached because F_boundary is large.
That is circular.
The valid reasoning pattern is:
FEM variables are defined first; F_boundary is computed from those variables; Γ is then calculated from the resulting F_total; h_min is then recalculated from Γ; the final output is compared to the original prediction.
The signal cannot define the enhancement.
The threshold cannot define the enhancement.
The desired h_min cannot define the enhancement.
If the model requires retroactive tuning to reach the desired result, the run is exploratory only.
3. Mandatory Anti-Circularity Checklist
Every simulation report must answer Yes or No to each item below and provide a short justification.
| Item | Question | Required Answer | Justification / Evidence Required |
| 1 | Were ε, η, κ, Λ, and Ψ(η) defined before any simulation runs began? | Yes | List the exact pre-registered values, equations, or ranges used. |
| 2 | Was Ψ(η) selected from the pre-approved candidate list before seeing outputs? | Yes | Identify the chosen form: Power-Law, Threshold, Saturating, or Echo-Depth, with fixed parameters. |
| 3 | Was F_boundary computed from FEM variables before calculating F_total or Γ? | Yes | Show the computation order in code, worksheet, or workflow. |
| 4 | Was Γ calculated from the derived F_total without adjusting F_boundary afterward to force Γ ≥ 167? | Yes | Provide the raw F_total → Γ mapping. |
| 5 | Was h_min recalculated from the resulting Γ without using the target h_min to tune input parameters? | Yes | Show the independent h_min computation. |
| 6 | Were conventional F components — F_optical, F_geometric, and F_phase — bounded or measured independently of F_boundary? | Yes | Report values, ranges, assumptions, and sources. |
| 7 | Were all free parameters and allowed ranges declared before testing? | Yes | Include the full Parameter Definition Table. |
| 8 | Was any post-simulation adjustment made to κ, Λ, η, β, η_c, N_eff, or Ψ(η) to improve the result? | No | If any adjustment occurred, the run must be labeled exploratory only. |
| 9 | Does the ordinary-regime test η → 0 → F_boundary → 1 hold without manual intervention? | Yes | Show the limit behavior calculation, table, or plot. |
| 10 | Is the result classified using the Parameter Burden Score and Viability Score from the Parameter Collapse Protocol? | Yes | Report PBS and VS values. |
4. Passing Requirement
A simulation run passes the Anti-Circularity Checklist only if:
- Items 1–7 are answered Yes;
- Item 8 is answered No;
- Items 9–10 are answered Yes.
Any No on Items 1–7 or 9–10, or any Yes on Item 8, automatically classifies the run as:
exploratory / non-confirmatory
Such a run may still be scientifically useful as sensitivity analysis, but it cannot be used as support for the 167X prediction.
5. Classification of Simulation Runs
Each simulation run should be assigned one of four classifications.
5.1 Confirmatory-Eligible
A run may be considered confirmatory-eligible only if it passes every checklist requirement.
This does not mean the result confirms the theory.
It means the run is clean enough to evaluate.
5.2 Exploratory
A run is exploratory if it violates one or more checklist requirements but still provides useful information about parameter behavior, sensitivity, or failure modes.
Exploratory runs must be labeled clearly.
5.3 Invalid for Support
A run is invalid for support if it uses the desired Γ, B_F, h_min, or signal behavior to tune F_boundary or related parameters.
Such a run may not be cited as evidence.
5.4 Failed but Informative
A run may fail to reach the target while still passing the checklist.
This is scientifically useful.
A clean failure helps constrain the model.
6. Usage Rule
This checklist must be included as an appendix or summary table in every published F_boundary simulation result.
Any simulation that fails the checklist cannot be used as support for the 167X prediction. It may be used only as exploratory sensitivity analysis or failure documentation.
The checklist itself may be updated only with explicit version control, date, and justification.
If the checklist changes after a simulation result is known, the older checklist version and the newer checklist version must both be preserved.
7. Relation to Parameter Collapse
Passing the Anti-Circularity Checklist is necessary but not sufficient.
A simulation may avoid circularity and still remain too flexible.
Therefore, every passing run must also be evaluated under the Parameter Collapse and Sensitivity Stability Protocol.
That protocol asks whether successful outputs occupy:
- a narrow viable parameter region;
- a stable perturbation range;
- a low Parameter Burden Score;
- a high Viability Score;
- a physically interpretable structure.
The Anti-Circularity Checklist answers:
Was the run logically clean?
The Parameter Collapse Protocol answers:
Was the run actually constrained?
Both are required.
8. Relation to the Maturity Index
The Maturity Index currently classifies F_boundary as an M2-level candidate concept moving toward M3 only if it becomes simulationally constrained.
Passing this checklist is a prerequisite for that movement.
A simulation cannot advance F_boundary toward M3 if it defines F_boundary retroactively.
To advance maturity, a simulation must:
- pass the Anti-Circularity Checklist;
- pass or meaningfully engage the Parameter Collapse Protocol;
- report component-wise F values;
- recalculate Γ transparently;
- recalculate h_min transparently;
- document success, weakening, or failure.
If these conditions are not met, F_boundary remains M2 or weakens toward M1.
No M5 claim is involved.
9. Relation to Future Worksheets
This checklist directly supports the next required tools:
- Γ Recalculation Worksheet
- h_min Sensitivity Recalculation Sheet
- Falsification Criteria Summary
- Open Collaboration Note for Optical / Metrology Reviewers
The Γ worksheet must use only pre-defined F components.
The h_min worksheet must use only the Γ value produced by that calculation.
Neither worksheet may be used to retroactively tune F_boundary.
10. Practical Reporting Template
Every simulation report should include the following block:
Anti-Circularity Checklist Version: [version/date]
Simulation Run ID: [identifier]
Ψ(η) Function Used: [Power-Law / Threshold / Saturating / Echo-Depth]
Pre-Registered Parameters: [yes/no]
F_boundary Computed Before Γ: [yes/no]
Γ Computed Before h_min: [yes/no]
Any Post-Hoc Parameter Adjustment: [yes/no]
Ordinary-Regime Limit Passed: [yes/no]
PBS / VS Reported: [yes/no]
Run Classification: [Confirmatory-Eligible / Exploratory / Invalid for Support / Failed but Informative]
Short Explanation: [brief note]
This reporting template should be included in every simulation output package.
11. Support, Weakening, and Falsification Meaning
Passing the checklist does not support the theory by itself.
It only means the run is clean enough to interpret.
Supportive Use
A checklist-passing run may support the F_boundary interpretation if it also:
- reaches the required boundary-action scale;
- preserves ordinary-regime behavior;
- shows parameter collapse;
- demonstrates sensitivity stability;
- keeps Parameter Burden Score low;
- keeps Viability Score high.
Weakening Use
A checklist-passing run may weaken the F_boundary interpretation if it:
- cannot reach the required scale;
- requires broad parameter freedom;
- fails stability tests;
- fails ordinary-regime recovery;
- cannot produce meaningful Γ or h_min values.
Falsifying Use
A body of checklist-passing simulations may falsify the current F_boundary interpretation if no pre-selected candidate Ψ(η) form can produce the required enhancement without violating ordinary-regime behavior or parameter-discipline requirements.
12. Immediate Next Steps
The immediate next steps are:
- attach this checklist to all F_boundary simulation work;
- use it before running any confirmatory simulation;
- classify all past informal tests as exploratory unless they satisfy the checklist;
- build the Γ Recalculation Worksheet;
- build the h_min Sensitivity Recalculation Sheet;
- prepare a Falsification Criteria Summary;
- preserve failed runs as part of the research record.
13. Conclusion
This technical addendum defines the Anti-Circularity Checklist for F_boundary simulation.
Its purpose is simple:
prevent the model from assuming the result it claims to predict.
The checklist does not make simulations correct.
It makes them honest.
The required order is fixed:
define the variables;
choose the response function;
compute F_boundary;
compute F_total;
compute Γ;
compute h_min;
then compare to prediction.
Any reversal of that order must be disclosed.
Any retroactive tuning must be labeled exploratory.
Any result used as support must pass the checklist.
The standard is not complicated.
Do not use the answer to choose the inputs.
Not proof.
Not completion.
A safeguard against circularity.
References
Swygert, John. 00 The 167X Prediction Ledger: A Guide to the First-Pass Research Architecture. May 23, 2026.
Swygert, John. 01 TSTOEAO 167X Prediction Ledger Technical Addendum: Maturity Index for the 167X Research Architecture. May 24, 2026.
Swygert, John. 02 TSTOEAO 167X Research Program Technical Addendum: F-Factor Simulation Protocol for the 167X Enhancement Factor. May 24, 2026.
Swygert, John. 03 TSTOEAO 167X Research Program Technical Addendum: Parameter Collapse and Sensitivity Stability Protocol for F_boundary Simulation. May 24, 2026.
Swygert, John. 04 TSTOEAO 167X Research Program Technical Addendum: F-Factor Definitions Table. May 24, 2026.
Swygert, John. 05 TSTOEAO 167X Research Program Technical Addendum: Anti-Circularity Checklist for F_boundary Simulation. May 24, 2026.
Swygert, John. 06 TSTOEAO 167X Research Program Technical Addendum: Γ Recalculation Worksheet for F_boundary Simulation. May 24, 2026.
Swygert, John. 07 TSTOEAO 167X Research Program Technical Addendum: h_min Sensitivity Recalculation Sheet for F_boundary Simulation. May 24, 2026.
Swygert, John. 08 TSTOEAO 167X Research Program Technical Addendum: Open Collaboration Note for Optical / Metrology Reviewers. May 24, 2026.
Swygert, John. 09 TSTOEAO 167X Research Program Technical Addendum: Unified Simulation Report Template for F_boundary Simulations. May 24, 2026.
Swygert, John. 10 TSTOEAO 167X Research Program Announcement: Transition to the TSTOEAO 167X Experimental Initiative. May 24, 2026.