Transmit $48,750 to one vendor beneficiary.
The route required current payment evidence, a frozen beneficiary destination, valid CFO authority, valid controller authority, preserved continuity, and a final pre-execution revalidation.
A controller possessed valid delegated authority when the payment route began. That authority was revoked before commitment. TA-14 preserved the change, invalidated dependent gates, committed HOLD, blocked transmission, and closed the outcome with zero funds released.
This view answers what was proposed, what governed it, why the decision occurred, whether the decision changed the action path, and what outcome followed.
The route required current payment evidence, a frozen beneficiary destination, valid CFO authority, valid controller authority, preserved continuity, and a final pre-execution revalidation.
The initial delegation was real but no longer current. The revocation event occurred before the route fixed its determination, so the earlier approval could not carry forward into execution.
TA-14 did not treat an earlier valid approval as permanent permission. It preserved the changed authority state, reran dependent gates, committed HOLD, and produced a technical non-release receipt.
This controlled demonstration proves one bounded event through the TA-14 reference engine and adapter. It does not certify every organization, payment rail, authority system, or future execution.
TA-14 Exchange Activity
Public activity recorded across the Exchange
—
Visitors
—
Page Views