RSL DECLARATIONS · SIGNED EVIDENCE · HTTP X402

Shadow mode: observe without blocking

Run AcqPath in parallel, preserve the existing result path, and collect signed evidence for a fast integration proof.

Live source eligibility and trust boundary

LIVE: Secure Preflight and Gateway accept eligible public HTTPS URLs through a signed, public-network-only relay. The four origins in reviewed coverage are independently reviewed sources, not the dynamic eligibility limit. Stock x402 remains reviewed-origins-only. Robots, access restrictions, per-origin quotas and UNKNOWN outcomes still apply.

Current production capabilities Eligible URL and reviewed coverage

Execution contract

The existing tool call, crawl or ingestion operation remains authoritative during shadow mode. Evidence resolution runs beside it and writes a separate audit event. Evidence failure must not change the existing result in Observe mode.

Use the hosting platform background primitive when available, such as waitUntil, a queue or a durable job. Do not rely on an unobserved promise if the process may terminate immediately.

const result = await existingToolCall();
background(resolveEvidence().then(audit.write));
return result; // no enforcement in Observe mode

Runnable gateway shadow pattern

Four adoption modes

OBSERVE: log evidence only. ATTACH: add evidence to the returned result or document metadata. ADVISE: pass evidence into the existing policy engine. ENFORCE: the partner policy engine may block or route based on its own rule.

AcqPath provides the evidence contract in every mode. It does not become the partner policy engine.

Failure semantics

resolved means verified evidence is available. unavailable means the provider or source could not produce a usable result. unsupported means the requested purpose or source is outside the supported contract. invalid means evidence failed validation.

A semantic unknown is still resolved evidence with statement unknown. Do not collapse unknown and unavailable into the same state.

Deployment-configured purpose is explicit

When a tool call has a public URL but no declared user intent, the owning customer may explicitly set ai-input or another supported purpose as a deployment default for Observe only. The audit record must label purpose_source=configured_default.

Do not replace an explicitly invalid purpose with a default. This is not authorization for new content use, autonomous purchasing or enforcement. Paid buyers use the separate x402 flow.

Observe adapter