What differs from a native baseline before the result is known?
Scientific attitude
Do not protect the framework. Try to break it.
A clean story is not evidence. A familiar analogy is not a discovery.
Every serious claim needs a test card.
What present carrier or constraint can be changed?
What happens when the alleged retained consequence is removed?
What comparison isolates the claimed operation?
What time, energy, memory, compute, and verification cost is included?
What result forces demotion, revision, or retraction?
Correspondence discipline
When two domains appear structurally similar, report the status before the story.
identical valueformal equivalencestructural correspondencewitnessed simulationshared signature onlyunsupportedincomparable
A valid comparison specifies the mapping, preserved properties, broken properties, evidence, uncertainty, and error. A shared vocabulary or function signature is not mathematical equivalence.
Evidence classes
Supported by bounded completed implementation, accepted formal work, or an experimentally specified result that stays inside its evidence.
Coherent enough to formalize and test; empirical promotion is still required.
Useful enough to guide experiments but underdetermined.
Language the program must not use without new evidence.
Immediate framework-level failures
- CF only renames established causation without new variables or discriminating tests.
- Cross-domain mappings collapse under native mathematics or require incompatible objects.
- Matched native methods outperform CF-guided methods after all verification costs are counted.
- Claims depend on history that is not instantiated in any causally relevant present state.
- The framework cannot return negative, unsupported, or incomparable results.
Go to the record
Inspect artifacts, not confidence.
Use the experiments, source documents, formal pages, public code, and scientific-neighbor analysis to evaluate individual branches.