Compare declared retained byte counts and payload/receipt lifetime seconds with caller ceilings using exact integers. This does not read actual storage, measure costs or extend retention. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Compare declared request/response coordinates for each HTTP contract. UTF-8 bytes, codepoints and tokens stay distinct; no tokenizer, conversion or remote execution. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Compare payload and receipt TTL unit labels against the declared retention contract. Seconds, milliseconds and hours are not converted; no store access or deadline renewal. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Check supplied result/receipt expiry declarations against original creation and retention windows, including attempted deadline extension. No journal writes or payment recovery is performed. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

Compare revision-pinned recovery metadata and report changes to original payment, network, result or expiry pins. A later expiry is a metadata change, not authorization to renew retention. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Bind recovery declarations to caller-supplied original purchase pins, including chain and original payload/receipt deadlines. No signatures, secrets, payment verification or retained output is loaded. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Inspect declared one-to-one aliases to recovery manifests using revision, network, payment and input pins. Aliases do not grant wallet ownership or recovery access. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Inspect declared parent/retry links for missing manifests, cycles and links across payment or chain frames. No retry, second authorization, replay or refund is performed. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Compare required recovery-check IDs with supplied states. Missing, conflicting and unknown states never become satisfied; this is not a recovery authorization or settlement check. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Count joint absence of result pins and original payload/receipt deadlines. Missing result metadata remains unknown, not proof that delivery failed or succeeded. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Compare closed recovery-manifest field contracts for ingestion narrowing and removed retained-result/receipt-only modes. An advertised mode is not an observation that output is recoverable. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Compare revision-pinned recovery projections and the relative order of shared manifests. Insertions are separate from reordering; no purchase or store mutation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Report absent owner, route/method or schema pin declarations in supplied HTTP-contract metadata. No remote schema fetch or assurance that the route is payable or executable. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Group HTTP contract identities within owner, revision and exact target frames; distinguish identical duplicates from conflicting schema/scope declarations. No invocation deduplication. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Check declared HTTP contract publication/retirement times against a supplied assessment. Missing retirement stays open-ended; no freshness, availability or execution certification. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Compare revision-pinned HTTP contract target, input/output pins and scope labels. These are contract metadata deltas, not full compatibility analysis or a causal explanation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Bind HTTP contract schema-pair declarations to an exact owner/revision/input/output source manifest. Digest agreement is not source truth, implementation conformity or runtime testing. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Check one-to-one client aliases to exact HTTP contract owner/revision/input/output pins. Aliases do not prove discovery integration, authority or executable tool availability. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Inspect declared HTTP contract inheritance links for missing nodes, cycles and cross-owner links. No external references are resolved; this is not complete JSON Schema or MCP validation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

Compare caller-required HTTP contract review-check IDs with supplied states. Missing or unknown states are not approval, policy compliance, security verification or deployment readiness. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.