Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 39 additions & 19 deletions architecture.html
Original file line number Diff line number Diff line change
Expand Up @@ -257,8 +257,6 @@
font-size: 0.6rem; padding: 0.2rem 0.5rem;
border: 1px solid var(--border); color: var(--text-faint);
}
.layer-item.live { border-color: #166534; color: var(--green); }
.layer-item.new { border-color: #1e3a5f; color: var(--blue); }

/* AIP SECTION */
.aip-section { background: var(--bg2); border-top: 1px solid var(--border); }
Expand Down Expand Up @@ -571,29 +569,51 @@ <h2>Not the product. The evidence.</h2>
<div class="section-label">Layer by Layer</div>
<h2>How the stack fits together.</h2>
<p class="section-intro">Each layer is independently valuable. Together they form a complete trust infrastructure for autonomous agent economies.</p>
<!-- ==========================================================================
SOURCE: the layer items below carry NO live state, and the reason is dated.

Until 24 August 2026 nine of them read "... · live" in green. Nothing on this
page computes a state (the page has no script), no results/ field or
data-measured marker covers any of them, and the marks had stood since the
April 2026 rebuild (9a6406d). Measured by hand that day: the org DID document
served 200 and byte-identical to the tree; the agent DID
did:web:observerprotocol.org:agents:maxi-0001 resolved 200 through the API
proxy. The other seven were not measured, and "Universal resolver" names
nothing this estate defines. A mark that is true today and computes nothing
is the same defect with a correct value (CONVENTIONS 2a, family 1), so the
state was removed from all nine and the labels kept.

Same day, same treatment for the "... · new" marks: a relative state that
decays without anything having changed, dating from the same April rebuild,
computed by nothing. State removed, labels kept.

A state returns here ONLY inside a marker that a check re-derives on every
run, the way results/hosted-verifier.json is re-queried. Do not type "live"
or "new".
========================================================================== -->
<div class="layers-grid">
<div class="layer-card">
<div class="layer-num">LAYER 01</div>
<h3>Agent Identity</h3>
<div class="layer-tag">W3C did:web · Ed25519 · Domain-anchored</div>
<p>Every agent and organization on Observer Protocol receives a W3C Decentralized Identifier. Agent DIDs resolve to DID Documents at standard URLs. No central registry required. The domain is the trust anchor: an agent whose DID domain doesn't match its organization's DID domain is a fraud signal.</p>
<div class="layer-items">
<div class="layer-item live">did:web agent DID · live</div>
<div class="layer-item live">did:web org DID · live</div>
<div class="layer-item live">Universal resolver · live</div>
<div class="layer-item">did:web agent DID</div>
<div class="layer-item">did:web org DID</div>
<div class="layer-item">Universal resolver</div>
<div class="layer-item">Domain mismatch rule</div>
</div>
</div>
<div class="layer-card">
<div class="layer-num">LAYER 02</div>
<h3>Payment Rails</h3>
<div class="layer-tag">Rail-agnostic · Verification is the constant</div>
<p>Four payment rails are live today. Two more are listed below and are not live. The verification logic is identical regardless of settlement layer: a Lightning preimage, an ECDSA signature over a transaction hash, or a verifiedSend() call all produce the same output: a cryptographically verified economic event that cannot be faked at scale.</p>
<p>Six rails are listed below. What has been published or demonstrated on each is stated in the homepage register, which is measured; this page has nothing that measures it. The verification logic is identical regardless of settlement layer: a Lightning preimage, an ECDSA signature over a transaction hash, or a verifiedSend() call all produce the same output: a cryptographically verified economic event that cannot be faked at scale.</p>
<div class="layer-items">
<div class="layer-item live">Lightning / L402 · live</div>
<div class="layer-item live">x402 / Solana · live</div>
<div class="layer-item live">x402 / EVM · live</div>
<div class="layer-item live">Stripe MPP · live</div>
<div class="layer-item">Lightning / L402</div>
<div class="layer-item">x402 / Solana</div>
<div class="layer-item">x402 / EVM</div>
<div class="layer-item">Stripe MPP</div>
<div class="layer-item">Tether WDK</div>
<div class="layer-item">OWS / MoonPay</div>
</div>
Expand All @@ -602,12 +622,12 @@ <h3>Payment Rails</h3>
<div class="layer-num">LAYER 03</div>
<h3>Observer Protocol</h3>
<div class="layer-tag">W3C VC · VAC · KYB · Open infrastructure</div>
<p>The core protocol layer. OP issues Verifiable Agent Credentials: W3C-compliant, cryptographically signed, portable across any platform. VACs attest to verified facts: economic activity, payment history, counterparty network, and KYB linkage. OP is open infrastructure: free to use, self-hostable, MIT licensed.</p>
<p>The core protocol layer: the schemas, the published engine, and the signed objects this site publishes verifiers for, which are <span data-shared-copy="verifiable-set">delegation credentials, refusal records, lapse records and decision attestations</span>, each a W3C-shaped signed object checked against a published key. A credential here states authority granted, not behaviour observed: nothing attests to an agent's economic activity, payment history or counterparty network. That model was ruled off this site on 9 August 2026, and this paragraph carried it until 24 August 2026 in words the stem check does not catch. OP is open infrastructure: free to use, self-hostable, MIT licensed.</p>
<div class="layer-items">
<div class="layer-item live">VAC issuance · live</div>
<div class="layer-item live">W3C DID resolver · live</div>
<div class="layer-item new">KYB VC · new</div>
<div class="layer-item new">ERC-8004 / TRC-8004 · new</div>
<div class="layer-item">VAC issuance</div>
<div class="layer-item">W3C DID resolver</div>
<div class="layer-item">KYB VC</div>
<div class="layer-item">ERC-8004 / TRC-8004</div>
<div class="layer-item">Challenge-response</div>
<div class="layer-item">Identity consolidation</div>
</div>
Expand All @@ -618,11 +638,11 @@ <h3>Agentic Identity Protocol (AIP)</h3>
<div class="layer-tag">Behavioral governance · Delegation · Remediation</div>
<p>AIP governs how agents interact, not just who they are. It defines delegation credentials (org → agent signed scopes), bilateral attestation, remediation flows when a request falls outside its mandate, a type registry for counterparty classification, and, added in v0.7 and v0.8, trading-mandate and spending-mandate surfaces with a cryptographically-bound <code>PolicyEvaluationCredential</code> verdict envelope. AIP v0.9 is the current canonical draft; v0.6 / v0.7 / v0.8 remain published as historical drafts. It sits above the VAC layer, adding behavioral governance to cryptographic identity.</p>
<div class="layer-items">
<div class="layer-item new">Delegation credentials · new</div>
<div class="layer-item new">Remediation envelope · new</div>
<div class="layer-item">Delegation credentials</div>
<div class="layer-item">Remediation envelope</div>
<div class="layer-item">Revocation + cascade · specified, not working in this deployment</div>
<div class="layer-item new">Type registry · new</div>
<div class="layer-item new">Eager chain verification · new</div>
<div class="layer-item">Type registry</div>
<div class="layer-item">Eager chain verification</div>
</div>
</div>
</div>
Expand Down
Loading