Home / The Same-Level Attack Rule

The Same-Level Attack Rule

Definition

The same-level attack rule requires criticism to address what the claim actually asserts. Name the target, its scope, and the inference connecting the evidence to a failure of that target. Evidence can arise at another descriptive level when that connection is established.

A failed run can challenge a claim about an operator's implementation. A concrete instance can refute a universal functional claim. A substrate limitation can challenge a claim that the substrate realizes a function. Different material alone does not establish different function; a demonstrated failure of the claimed realization does.

relevant(attack, claim):
    identify the claim and its scope
    state the evidence or argument
    show how it bears on the asserted relation

This replaces literal equality of level labels with an assessable connection. An objection need not use the framework's vocabulary before its substance can be examined.

Type and formal status

E: Derived, CV. The method and its labels remain revisable.

A: The rule aims to distinguish relevant criticism from substitution of a different target. Misclassifying a relevant counterexample is an error of the rule or its application.

Useful distinctions

Domain, carrier, operator, binding, composite, role, frame, and application are useful descriptors. They are not a single exhaustive ladder of mutually exclusive levels. An application can instantiate an operator, binding, or role, and one claim can relate several of them.

Distinction	What alone does not refute the claim	What can bear on it
Process / operator	A run differs in incidental detail	The run violates the operation's claimed behavior under its stated conditions
Persistence / direction	A state lasts longer	Persistence shows that a claimed direction or reduction is not realized
Substrate / function	Carriers are made of different materials	A carrier lacks a capacity the realization claim requires
Token / type	Two occurrences are distinct	Their difference contradicts behavior the type claims to predict
Expression / regulated error	Reports use different words	Reports or other observations support a different binding or expose an omitted relation

Attack-type matching gives further routes. A specific argument still has to establish the connection; neither a label nor its absence decides the outcome.

What it regulates

The rule prevents criticism from silently substituting a stronger, weaker, or different claim. It also prevents a maintainer from withdrawing a claim's real commitments when contrary evidence appears.

What regulates it

A rejection for irrelevance must identify the missing connection or the changed target. The critic may challenge the distinction or supply the connection. Apply the same distinction consistently across cases, and record a changed scope as a revision rather than pretending the original claim never had it.

If a proposed rejection cannot be justified, examine the objection on its merits. Admission does not itself establish refutation or require a substantive change. Record the evidential result separately from any repair. Effective uptake and self-sealing review keep the admission procedure itself correctable.

Valid attack surface

Show that the rule excludes relevant evidence, admits a change of target as a refutation, or permits arbitrary relabeling to protect a claim. A concrete misclassified exchange can test this methodological rule; calling it an anecdote does not dispose of the counterexample.

What happens if isolated

Labels without an appealable relevance argument can become a shield. Unexamined relevance can also misreport a neighboring observation as a defeat. Neither failure requires this particular taxonomy to be the only available remedy.

What larger property emerges from the coupling

The procedure supports criticism that reaches the actual claim and a maintainer whose interpretation remains answerable. It protects functional distinctions while permitting empirical and concrete evidence to test them.

What would actually kill the claim

Revise the method where its criteria systematically reject relevant criticism or cannot distinguish target substitution from a valid challenge. Repair a misapplication without treating that alone as refutation of every relevance rule.

Prohibited misreadings

Same level as identical labels: establish relevance across descriptions where needed.
A concrete instance as automatically too low-level: an instance can test a general claim.
Admission as defeat: evaluate the argument after admitting it.
Retyping as immunity: acknowledge and assess any changed commitment.