Core advances one bridge at a time. Each new capability must be connected to ancestry already earned, tested under explicit conditions, and challenged before it is allowed to support the next stage.
The method is deliberately restrictive. A promising idea is not enough. The investigation asks what is already available, what single new capability is being proposed, and whether that capability actually survives testing.
Identify exactly which previously earned ingredients may be used. Mature mechanisms that have not yet been established are withheld.
Introduce the smallest credible next transition and state clearly what new capability it is supposed to produce.
Test whether the claimed capability survives controls, perturbations, alternative explanations, ablation, or destructive challenge.
One of the central rules of Core is that a later stage cannot quietly borrow a mature capability merely because that capability would make the model work.
The proposed capability survived the stated test and may be used as ancestry within the scope actually demonstrated.
The capability survived, but only under a restricted range of conditions, parameters, or structural assumptions.
Part of the pathway remains viable, but one or more required bridges or controls are still unresolved.
The proposed mechanism did not survive the stated gate and cannot be treated as earned ancestry.
Many apparent successes disappear when a simpler explanation is tested. Core therefore tries to attack its own preferred interpretation before promoting it.
Did the proposed mechanism actually produce the result, or did the result arise from ordinary structure, hidden assumptions, parameter tuning, statistical accident, or a capability that was effectively inserted in advance?
Compare candidate states against states that are similar in ordinary structure but lack the proposed causal feature.
Remove a component or relation and determine whether the claimed higher-level behavior disappears with it.
Ask whether a simpler predictor or mechanism explains the result as well as, or better than, the preferred interpretation.
Core does not erase a failed result merely because it interrupts a promising line of thought. Failure narrows the ancestry and prevents later stages from quietly rebuilding the same rejected mechanism under a different name.
A later test may revisit an earlier failure, but the original result remains part of the record. A branch is only restored if a new mechanism, new ancestry, or stronger test materially changes the case.
The purpose of the method is not to force a predetermined answer. It is to determine how far increasingly complex behavior can be reconstructed from simpler ancestry while keeping every major transition visible enough to test.
If the final behavior is removed from our assumptions, can the ancestry still produce it?