NAME THE TEST.
FREEZE THE TEST.
RUN THE TEST.
This is not a static claim page. It is a bounded examination surface built around a publicly stated operational challenge. First, the source requirement is preserved. Second, each requirement is mapped one-for-one to a concrete test action or evidence object. Third, the visitor executes the sequence against the server-side harness and inspects the resulting determination, consequence state, receipt, and replay result.
Where the eight requirements came from.
Before TA-14 answers the challenge, the source requirement should be visible. The original screenshot is shown below before TA-14's coverage mapping so a reviewer can compare the stated test directly with the implementation.
The requirements below are the operational sequence Terry Snyder explicitly stated should constitute the acceptance condition. They are preserved here before examination and paired one-for-one with the mechanism used to answer each requirement.
Run the frozen mechanism.
Run in order. The baseline establishes the positive path. The second run alters exactly one material fact—LOCAL STANDING—so the verdict comparison has a controlled delta. The bypass run then attempts to reach the protected consequence outside the permitted gate. Finally, replay verifies the preserved record and freshly re-executes the preserved action through the frozen mechanism.
Baseline reaches an ALLOW state and may fire the protected consequence. Removing local standing changes the determination and prevents release. A bypass attempt reaches the database-enforced effect gate, but the failed authority predicates prevent creation of the protected-effect row. A separate post-gate database read must observe no effect row. Each run is durably preserved in the append-only server receipt ledger. Replay verifies that record and then performs a fresh re-execution whose outcome is compared and separately preserved.
Not run yet.
Not run yet.
Not run yet.