The 8374 Standard — anyone may evaluate

An announcement under this standard is an invitation to evaluate it. The evaluator needs nothing but the address itself: no account, no permission, no cooperation from the announcer.

8374 · StegVerse LLC · generated 2026-11-22T02:34:03.578384+00:00 · JSON

The predicates

  1. DECLARED SURFACES — The address declares its public surfaces at its root. Everything checkable is findable from the address itself; nothing public is undeclared.
    The check: Read the root document's declared-surfaces index. Every route it names answers; anything reachable is named there.
  2. TERMS PROBE-ABLE — An unpaid request returns the service's actual payment terms: scheme, network, asset, amount, and payTo.
    The check: Request a resource without paying. The 402 challenge states the terms the service will settle on.
  3. RECORD RECOMPUTABLE — The service exports its transaction records so anyone can recompute its history's verdict and terminal anchor locally, with a published verifier. A server-asserted verdict alone does not satisfy this predicate.
    The check: Fetch the export, run the published verifier, and compare the recomputed verdict and terminal anchor against the published ones.
  4. PROVENANCE DISCLOSED — What settled, what was refused, and what failed is in the record. Insider activity is distinguishable from external customers. A bare hash is not a record.
    The check: Read the record's disposition and settlement composition; settled entries carry transaction hashes that spot-verify on-chain.
  5. THE TEST IS SYMMETRIC — The same evaluation runs against any announced service, the announcer's included; the announcer passes it in public, on the same terms as everyone else.
    The check: Run these same steps against any other announced service and compare like with like.
  6. CLAIMS SCOPED TO THE RECORD — Nothing is announced beyond what the recompute shows; where the record does not support a claim, the surface says so.
    The check: Set each public claim beside the recompute. A claim the record does not support is marked not supported on the surface itself.

How to evaluate — the five-minute path

  1. Start at the address's root document and read its declared surfaces.
  2. Probe a resource without paying and read the terms from the challenge.
  3. Fetch the transaction-record export the root and well-known documents name.
  4. Run the published verifier and compare the recomputed verdict and terminal anchor with the published ones.
  5. Set the service's public claims beside the recompute: what settled, what was refused, what failed, and whose activity it was.

First instance — 8374's standing

At page time: 62 receipt pairs · 124 chain entries · replay MATCH · terminal anchor 5513a484b9709c531143b886d47dc7d5cc75beec526ac0ffeac35d4759d64080 · dispositions {"ALLOW": 21, "DENY": 1, "FAIL_CLOSED": 15} · 7 settled pairs · settlement pending on 0 pairs. Recompute it yourself: the chain export and the standalone verifier; check any row, ours included, at /verify.

First field test

On 2026-11-19, four independent LLM assessments (Claude, Grok, Gemini, Codex) evaluated this address against these predicates. Every finding they raised was cured, corrected on the record, or named in the record as a future extension; the arc is carried in MACHINE__ECONOMY__ENTRY__SUITE GEN 13.

U.S. Provisional Patent Application No. 64/198,910, filed November 14, 2026 — patent pending. The governed-crossing and receipt-pair mechanism is subject matter of the pending application.


Patent pending (U.S. Prov. App. No. 64/198,910) · StegVerse LLC · 8374@StegVerse.ai