ACTOR
Who or what asserts standing?
Hear why standing had to become its own architecture.
Samantha walks through the four-anchor core, the difference between authority and standing, the Admissible Standing Record, and the exact boundary where ASA stops.
READ SAMANTHA'S NARRATION
Welcome to the TA14 Admissible Standing Architecture. ASA exists because applicable authority and established standing are not the same determination. Authority answers what may legitimately govern. Standing answers who may legitimately invoke it. Start with the actor. Who or what is making the standing claim? Then capacity. In what declared role, office, assignment, agency, function, or machine capacity is that actor acting? Identity alone is not capacity. Third is standing basis. What admissible evidence supports the claimed relationship? A credential, login, license, contract, passport, technical capability, or organizational affiliation may contribute evidence, but none automatically manufactures standing. Fourth is authority relationship. How does the standing basis connect this actor, in this capacity, to the already applicable authority for this specific proposed consequence now? ASA then produces an Admissible Standing Record with one of four dispositions: Established, Not Established, Hold, or Escalate. Established means the actor to authority relationship has been established for the examined standing claim. It does not authorize execution. ASA does not create authority. It does not decide whether authority applies. It does not bind an execution route. It does not commit a decision. And ASA Established is not AEA Allow. The deeper TA14 rule is simple: no applicable authority can manufacture standing, and no standing determination can itself authorize execution. This is why standing is its own governance problem.
Standing is a relationship. Prove the relationship.
CAPACITY
In what capacity is the actor acting?
STANDING BASIS
What admissible basis supports the claimed relationship?
AUTHORITY RELATIONSHIP
How does that basis connect this actor to already-applicable authority?
Standing Claim → Standing Basis → Actor-to-Authority Relationship Examination → Admissible Standing Record (ASR)
Same authority. Different actor. Different standing.
Change the claimant context and watch why authority alone cannot answer the standing question.
ACTOR
Owner A
CAPACITY
Asset owner
STANDING BASIS
Ownership record + current governance context
AUTHORITY RELATIONSHIP
Owner relationship to already-applicable authority is supportable for this consequence.
ASA DISPOSITIONESTABLISHEDStanding determination only. No execution authorization is created.
Three questions. None can answer for the others.
What can be relied upon as evidence for this consequence?
What authority legitimately governs this proposed consequence now?
Who, in what capacity, has the admissibly established relationship necessary to invoke that authority?
No admissible evidence can manufacture authority. No applicable authority can manufacture standing. No standing determination can itself authorize execution.
What ASA establishes — and what remains downstream.
ASA ESTABLISHES
Actor. Declared capacity. Standing basis. Actor-to-applicable-authority relationship. A bounded ASR disposition: ESTABLISHED, NOT ESTABLISHED, HOLD, or ESCALATE.
ASA DOES NOT
Create authority. Decide authority applicability. Repair delegation. Preserve authority currency. Establish an execution route. Perform Binding. Commit a decision. Authorize execution. Guarantee outcome.
Does this proposed consequence have sufficient Admissible Evidence, Applicable Authority, and Established Standing to become reality NOW?
TA14 Admissible Standing Architecture · TA-14-AIGR-000047 · v1.0-RC1 · Registration is not certification.