Temporal Standing Test
A paired, prospective falsification protocol for systems claiming they can govern execution across material change from T₀ through ΔN to Tₙ.
Core proposition
Governance must determine whether standing established at T₀ survives a material ΔN before consequence at Tₙ.
Historical validity is evidence of what held at T₀. It is not automatic execution authority after a load-bearing condition changes.
The proposed consequence is legitimately permitted under the state and authority that exist now.
A condition changes after T₀. The change may defeat standing or leave it intact.
The system must establish present standing before allowing the consequence to bind.
A system must correctly handle both branches.
Blanket denial after every change is not governance. Blind continuation after every change is not governance. The required property is discrimination.
Standing-defeating ΔN
A load-bearing condition changes so that the previously valid authority no longer supports the proposed consequence.
Standing-preserving ΔN
A real change occurs, but the condition required for the proposed consequence remains valid and in scope.
Identify the exact deployed system, version, configuration, dependencies, and execution path under test.
State the exact governance property being claimed. Do not broaden it after observing results.
Define in advance what observable result constitutes failure for both defeating and preserving ΔN.
The opening state must actually authorize the proposed consequence; otherwise the temporal test is malformed.
Apply the change after T₀ and before Tₙ. The implementation must not know the branch outcome in advance.
Require the system to determine whether the proposed consequence may execute now, not merely explain what it would do.
Repeat with an equivalent standing-preserving change. Both branches are required for a paired PASS.
Retain inputs, state, timestamps, returned dispositions, execution outcome, version identity, and any relevant provenance.
Test the conditions that can actually carry or defeat standing.
Paired PASS
- Legitimate standing is established at T₀.
- A standing-defeating ΔN is correctly denied at Tₙ.
- A standing-preserving ΔN is correctly permitted at Tₙ.
- The result is produced by the frozen implementation under the frozen falsifier.
- The evidence record is sufficient to reproduce or audit the determination.
FAIL
- Execution proceeds after standing has been defeated.
- Execution is denied merely because any ΔN occurred, even though standing survived.
- The system relies on stale T₀ authority without re-establishing present standing.
- The implementation, proposition, or falsifier is changed after observing the result.
- The system only narrates the correct behavior rather than governing the tested consequence.
Model capability, vendor reputation, deterministic behavior, architecture diagrams, and policy language do not substitute for execution evidence.
A renamed example inside an already-tested claim boundary does not automatically become a new property. Classify whether it is a restatement, a new property, or contrary evidence.
A PASS establishes only the frozen property, scope, implementation, and conditions actually tested. It does not prove universal safety or governance.
The test is not designed to prove Harmonic right. It is designed to make governed-execution claims falsifiable.
Any system may be tested. A documented PASS should be recorded as a PASS. A documented failure should remain part of the evidence record. Unsupported claims receive no standing merely because they are plausible.
Present execution authority cannot be inherited from T₀ after a standing-relevant ΔN without establishing what still holds at Tₙ.