Transaction authority
A transaction converts recognized authority into movement, obligation, release, or irreversible change.
Payments, transfers, disbursements, trades, approvals, releases, and contractual actions may be validly prepared under a credentialed session. Existence research asks whether the known participant’s governed existence relationship must still return present when the transaction is executed.
Authority before existence
The organization must first establish who may authorize the transaction.
Credentials, account ownership, role, approval limits, separation of duties, transaction rules, and workflow state determine whether the participant has authority.
The EAID does not grant that authority. The EAID is not an access credential, and a found identification cannot be sufficient to enter the transaction system or approve value.
Execution point
The strongest place to consume current existence is immediately before consequence.
A transaction may be assembled, reviewed, queued, or signed before final execution. The organization can identify the last controlled point before funds move, data is released, or an obligation becomes binding.
verify_existence(...)The transaction function requests the current result while all existing approval, fraud, limit, and authorization controls remain in force.
Private arrival
Existence establishment and transaction permission remain separate steps.
The first successful heartbeat releases the Rendering Agent and the organization loads its page, completing existence establishment. The page then requires the participant’s organizational credentials and transaction authority.
From that arrival forward, existence maintains itself through recurring heartbeat. The transaction system observes the result at the networked decision point but the network does not create existence.
Prepared versus executed
Historical preparation does not guarantee a current execution condition.
A participant may prepare a transaction and leave before release. A session may remain active. An approval token may remain valid. Automation may later execute a queued instruction.
Where policy requires the participant to be present at execution, the current existence result must be observed at execution rather than inferred from the earlier preparation event.
Multiple authorities
Dual control requires separate facts for each required participant.
One present result cannot stand in for another person’s credential, approval, or existence. Each required authority must be evaluated under the organization’s workflow.
Existence can support the process by maintaining a separate governed condition for each assigned participant, while the transaction system continues to enforce limits and separation of duties.
What presence cannot establish
A present participant may still be mistaken, deceived, coerced, or malicious.
Existence does not prove transaction intent, beneficiary legitimacy, price accuracy, legal authority, informed consent, freedom from coercion, or absence of fraud. It does not validate the transaction payload.
Those controls remain necessary. The existence result adds only the current condition that the governed participant is present under the maintained relationship when execution is requested.
Collapse
When existence ends, the organization must know which transaction paths may no longer continue.
The application can block final execution, suspend a pending release, close the private session, or require a new arrival according to policy. The action must be explicit and testable.
Existence does not decide the business rule. It gives the business rule a binary current condition upon which to act.
Continue the examination