Agent Trust Gate™ · P3-M154

Verified Agent Standing before GatePass.

First prove who or what is asking, whom it represents and why it has standing. Then decide whether its exact action may proceed.

No verified agent identity. No verified principal. No valid delegation. No standing to request a GatePass.
Safe synthetic page: fixed fixture records only. No credentials, uploads, personal data, analytics, cookies, network API, remote execution, real agent contact, company verification, payment or settlement.

Claimed requester

Standing decision

Ready

    Deterministic verification checks

    Principal and delegation

    Exact current request

    Machine-readable standing view

    
        

    GatePass precondition

    
        

    What this demonstrates

    ATG locally demonstrates how a requester can prove control of a registered software-agent identity, present signed evidence of its accountable principal and delegated authority, and bind the exact request to that standing before GatePass evaluation begins.

    The browser renders fixed review records. Run the repository CLI to execute the deterministic Ed25519 fixture verification and existing canonical exact-action GatePass evaluation:

    npm run demo:agent-standing
    npm run demo:agent-standing -- --summary-only
    npm run demo:agent-standing -- --scenario valid_organisation_sponsored_agent
    npm run demo:agent-standing -- --json
    npm run test:agent-standing

    Read the evidence model and claims boundary · For agents and operators · Prepare a safe scenario · Return to Agent Trust Gate™

    Claims boundary

    Agent Standing is a precondition, not a safety certificate. A fixture signature proves fixture-key control and signed-data integrity; it does not make every assertion factually true.

    P3-M154 does not prove that software is intelligent or conscious, prove unassisted message composition, prove complete autonomy, verify a real individual or company, provide production organisational identity assurance, provide live WebAuthn, SSO, enterprise credential or identity integration, provide production runtime or hardware attestation, certify honesty, safety or compliance, issue legal identity, execute actions, process payments, authorise settlement, contact agents or operate a hosted identity service.

    S5 runtime attestation is a future/high-assurance category only. This local demonstrator derives at most S4 and claims no production attestation.