Published and citable; not automatically empirically validated.
Evidence before claim · Updated September 10, 2026
Evidence and maturity
This page separates scientific evidence, software implementation, testing, publication, and external review. A status in one layer never transfers automatically to another.
01 / Canonical evidence layers
Seven categories, each making a different claim.
Follows within explicitly stated model assumptions.
Tested in simulations or methodological reference cases.
Tested with real data; the validity domain remains explicit.
A falsifiable claim whose confirmation remains open.
Planned research or software; not yet implemented.
Further theoretical exploration; not additional empirical evidence.
Separation rule: Software status such as IMPLEMENTED, AVAILABLE, IN DEVELOPMENT, or PLANNED describes technical availability—not scientific validity.
02 / Evidence matrix
What is defined, implemented, and actually tested?
| Element | Scientific status | Software status | Testing | External evidence |
|---|---|---|---|---|
| Frozen Legacy Kernel | Mathematically defined | Implemented in Studio 1.4.0 | Reference benchmark reproduced on Apple Silicon; one self-reported run | No independent replication |
| CRTI | Mathematically described; model-derived | Not available as an executable module in Studio 1.4.0 | Testing documented in the manuscript; software and empirical module validation remain open | Revised manuscript under editorial review; neither accepted nor published |
| FCQ | Described in a versioned publication | Research and architecture component | Domain-specific validation remains open | Preprint / open-science contribution |
| Studio 1.4.0 | Released baseline | macOS package built, installed, and launched | Reference values confirmed in one real-hardware run | No independent replication yet |
| Studio 2.0 | Current release preparation | Four-EWS line; three modules executable, CRTI remains release-blocking | Component tests documented; full release and hardware validation remain open | Not yet released as version 2.0 |
| Studio 3.0 / ECHO | Planned research architecture | Not implemented | No architecture-wide empirical validation | Planned for mid-2027; no availability guarantee |
| Domain transfer | Testable hypothesis | Requires separate operationalization for each domain | Permitted only through specified validation cases | No universal evidence of effectiveness |
| Ontology of Oscillation | Theoretical horizon | Not part of the mathematical core | No empirical claim for the method | Not a basis for validation status |
Reading rule: Publication does not imply validation or universal validity. Implementation does not imply domain-specific effectiveness.
03 / Claim protocol
Every claim needs an explicit boundary.
What exactly is being investigated?
Which data, model, code, or source supports it?
Where does the claim stop?
What result would count against it?
How far has testing progressed?
Which version is authoritative?
04 / Non-claims
What BenchEWS explicitly does not claim
- No certaintyAn early-warning signal is not a deterministic tipping-point prediction.
- No universal scoreBenchEWS does not provide one universal stress score for arbitrary systems.
- No automatic transferEach domain requires its own data, measurement model, criteria, and validation cases.
- No diagnostic shortcutHomo sapiens is a research domain, not a medical or psychological diagnostic instrument.