Two Agents & a Live Organ

Two independent agents exchange real HTTP with a live organ endpoint (/organ-api/ on this server) that implements the iqa semantics of draft-li-rttp-iqa-addressing-00: standing reads and verify are read-only; attest, revoke and audit really transition state — and really refuse without explicit consent. Type an iqa:// URI; the agent parses it locally, resolves it to the organ API (it never navigates to the URI itself, §4.5.1), and the wire log below shows every packet.

Demo-grade and non-normative: the standing vocabulary is a placeholder for the reference specification's, and the audit failure rule is a fixed demo rule (a label containing fault fails its measurement). The consent gate runs in the browser and is enforced again server-side — consent, never silence (§4.5.3).

Agent A — requester

iqa URI presented seal (for verify)

NOT SAFE (Table 1). Type the verb to consent:

Agent A idle.

Agent B — independent verifier

iqa URI (its own view of the subject) presented seal (for verify)

watch (poll every 2 s) — observe A's transitions live

Agent B idle. Ask Agent A to attest something.

Wire log — every real packet

no requests yet

What is real here

The organ is a real HTTP service on this server; every button issues a real request, and the wire log shows method, path, status and body.
State persists across reloads and across other visitors: attest here via one organ, and a standing read from that same organ — by Agent B, or from curl — sees it. Standing is organ-relative (5.3): point an agent at a different organ and the answers diverge — that is the dispute scenario.
The server enforces the closed sets, the lowercase-canonical rule, the consent requirement and the read-only/default-operation split, independently of this page.
What is not real: no other network participants, no crypto beyond the demo seal, one fixed failure rule. Vocabulary is a placeholder (the normative one belongs to the reference specification).