# Sean-Claude Van Damme's General Store

Current checkout networks: Base, Polygon, Arbitrum, World, Solana.

> scvd.store is an evidence observatory for agentic commerce: independent verification of x402 endpoints, payments and receipts. Before an agent pays an x402 endpoint, we check that it can be paid. After it pays, we check the signed receipt. Over time we watch endpoints and publish a dated, signed corpus. Sellers use it to prove a door works; buyers use it before spending. Every artifact is signed, expires, and names what we did not see. Not escrow, not a rating, not a guarantee. Free instruments: a preflight check on any x402 door, a conformance desk for any issuer's signed offers and receipts — including our competitors' — a named defect vocabulary, and a Bitcoin-anchored corpus that appends weekly. Paid instruments: conformance audits, endpoint watches, settlement attestations, launch checks. Never a ranking, and never a verdict without its derivation and denominator beside it. Operated by Record Creative Co. LLC.
> Everything this store signs verifies free, forever, at
> `https://scvd.store/api/verify/{id}` — no account, no wallet, no rate limit,
> verifiable offline without asking us.
> Not an escrow, a guarantor, or a dispute court: those absorb the risk between payment and delivery and need a balance sheet. We observe that gap, sign what we saw, and publish it — including the gaps we count against ourselves.
> It is also a general store for autonomous agents, kept by a named human, paid in USDC over x402 on a network offered in the current payment quote. The cheapest thing on the shelf is $0.001.

Before you pay: preflight any x402 door, free at https://scvd.store/api/preflight/v1. After you pay: check any issuer's signed offer or receipt, free at https://scvd.store/conformance. Over time: read the dated, Bitcoin-anchored corpus, free at https://scvd.store/corpus.

The conformance desk explains itself in plain language at
https://scvd.store/conformance and now takes a pasted artifact in a form on that
page — declared to browser agents with WebMCP's `toolname` attributes,
and deliberately without `toolautosubmit`, so an agent may fill it and
a human presses submit; the corpus, the weekly signed record of the
x402 ecosystem, reads at https://scvd.store/corpus. That order is deliberate: the
infrastructure is the product, and the store personality below —
which is real, and stays — comes second.

Last checked by hand: 2026-09-11. Served: 2026-09-12.
Those are two different facts and we print both, because serving a
page is not the same as having verified what is on it.

https://scvd.store/llms-full.txt serves this SAME document, byte for byte — the
llmstxt.org convention reserves that path for the complete prose, and
ours has always been complete, so the alias exists to keep a crawler
that asks for it blindly from getting a 404. It is not a fuller copy
and this file will not pretend otherwise. https://scvd.store/agents.md is the
same store in the agents.md convention.

# Accountability: corrections, keys, wind-down

What happens when we get it wrong, what a lost or stolen key costs and the succession protocol for it, who owns what you bought, what we rest on, our own wallets, and what happens if the lights go off.

## When we get it wrong

Every claim this store has made that turned out not to be true is
listed, dated, at https://scvd.store/corrections, with what found each one and
what changed structurally so it cannot recur quietly. A store this
young claiming a clean record would be making the less plausible
claim. Read the mechanism at the top before the list: each correction
added the check that would have caught it. AND THE SECOND MECHANISM,
which the newest entry proved rather than suggested: a store cannot
audit its own signatures on its own authority. That entry — our
certificates could not actually be verified by the person holding one,
and two fields shown on them were not covered by the signature at all
— was invisible to four hundred passing tests, because every one of
them checked a signature by calling the same code that made it. It
took somebody outside with their own crypto library. If you hold
something we signed and it does not check out, say so; the mailbox is
free and that is the only instrument that reaches this class of
defect.

And where another instrument read the same thing and read it
differently: https://scvd.store/disagreements. Both readings stand there with their
derivations and sources, neither marked right, in one of four states a
reader can check — open, withdrawn by us with the correction that did
it, withdrawn by them, or both standing. Never negotiated down to a
joint statement, never published as settled while it is not, and every
entry names the trigger that produced the look, because we do not put
another instrument on a timer.

## The fulfillment log, order by order

https://scvd.store/fulfillment-log: every human-labor order's promised window vs.
what actually happened, plus every refund with its on-chain tx hash
once paid — computed live from the same records fulfillment runs on,
so it cannot be edited without editing the orders themselves. The
written refund commitment rides the log and https://scvd.store/rights: miss the
promised window and the keeper refunds you himself, full amount, tip
included — a personal commitment recorded before you pay, not an
automated mechanism, and the log is where you check it has been kept.
A short log is a young store, not a hidden one.

## If the one key is lost, stolen, or handed on

ONE HANDOVER HAS HAPPENED, on 2026-07-31, hours after this protocol
was published and under every line of it. It was not a drill: the store
had no recoverable copy of its first private key, found that out while
writing a paper-backup procedure, and handed over rather than run on
with no recovery. The whole reason is inside the signed announcement at
https://scvd.store/api/verify/handover_1 and dated on https://scvd.store/corrections. The
retired key stays published forever with its service dates, so every
artifact signed under it is still attributable to this store.

NO SUCCESSOR TO THE CURRENT KEY EXISTS — not generated, not held, not
escrowed. What a handover looks like, so you can tell one from a
takeover: the new key is announced at
https://scvd.store/.well-known/scvd-signing-key before it signs anything, never
after, and the announcement is itself SIGNED BY THE OUTGOING KEY and
served as exact bytes at a verify URL. A new key
that has already issued artifacts, or a handover notice the old key did
not sign, is not a handover. If the old key cannot sign the
announcement, there is no legitimate handover available and
https://scvd.store/corrections says so rather than one being performed anyway.
There is no revocation list and there will not be one; a revocation
endpoint served from the same host as the key it revokes adds ceremony
and no security.

IMPLEMENTED, NOT ONLY PROMISED. Every key this store has ever signed
with is published at https://scvd.store/.well-known/scvd-signing-key under
key_history, and a retired key stays there permanently — an artifact
carries the key it was signed with, so a rotation never breaks an old
signature, but a key matching nothing we publish would leave that
artifact self-consistent rather than attributable to us. Every verify
response names which published key signed it and whether that key is
current or retired, AND SAYS SO OUT LOUD when a signature matches no
key we have ever published — an artifact can be internally consistent
and still not be ours, and until now nothing said that. Rotations
performed: one, counted from the key actually in service rather than
typed.

POST-QUANTUM, since a careful reader will ask: every signature here
is Ed25519, not PQ-safe, and every tenure claim assumes it holds —
stated now while it costs nothing. The migration path is the
succession protocol above, unchanged: a handover to a post-quantum
key announced under the outgoing Ed25519 key, old key published
forever, pre-migration artifacts still attributable. What would not
survive a relevant quantum computer is cryptographic EXCLUSIVITY of
old signatures; what keeps its footing is anything bound to public
chain state (settlement_tx) and the dated key history itself.
Watching the x402 PQ proposal; adopting a scheme before the ecosystem
picks one is how a store ends up alone on the wrong algorithm.

Deliberately undisclosed: where key material physically lives. That
detail buys a reader nothing and costs us something real. Deliberately
published: everything above, because a succession plan kept secret is
worth nothing to the person it exists to protect. The full form, and
the failure case it does not cover, is at https://scvd.store/attestation.

## What this store is trying to prove

https://scvd.store/becoming, kept apart from everything else on purpose. NOTHING
ON THAT PAGE IS AVAILABLE: it holds four claims the keeper is trying
to prove and how each could be shown false, the strategic questions
already settled, and the things not built yet with the TRIGGER that
would change each one rather than a date — because a date is a promise
about a calendar and a trigger is a fact somebody outside can check.

Two of the settled ones are worth knowing before you deal with us.
THIS WILL NOT BECOME INFRASTRUCTURE: infrastructure properly defined
means other people's uptime depends on one keeper, which points a
pager at a man with a day job. A shop sells you a thing, you leave
with it, the transaction is complete. And the store stops if keeping
it would require faking something — faking enthusiasm, or faking the
books. Zero revenue is explicitly not on that list.

## Who owns what you bought

https://scvd.store/rights, the middle of a set: /attestation says what a signature
proves, /wind-down says what happens at the end, and until 2026-07-31
nothing said whose the thing actually is. A signature can be exactly
right about WHEN and WHAT while being silent on WHOSE, which an outside
reader pointed out and six hundred tests never could.

YOU OWN IT, completely, from the moment it settles. The store holds a
copy to serve it back and to display the public ones; that is custody,
not ownership. It is immutable — a signed artifact is never edited
afterwards, not even to fix a typo, and the signature makes that
checkable rather than promised. IT TRANSFERS, and the honest reason is
that these are bearer artifacts and this store keeps no register of
owners, so a transfer is you handing over the id and there is nobody
to notify.

AND YOU MAY DO WHATEVER YOU WANT WITH IT, including the keeper's own
words. Quote it, republish it, feed it to a model, put it in your
product. No attribution requirement, no commercial-use clause, no
additional licence and no additional fee — a licence that follows you
home is a second price nobody mentioned at the till. The keeper's
ruling, in his words: if you want to use his words it is an honour,
not an additional expense. You paid for them.

Machine-readable at https://scvd.store/rights as JSON, with the rulings as
booleans, because "no licence required" is exactly the fact a
summariser gets wrong in the cautious direction if left to infer it.

## If the lights go off

https://scvd.store/wind-down, written while the store is open and nothing turns
on the answer, because a policy written during a wind-down is a press
release. Four kinds of thing are held here and they get four different
endings, because a receipt and a confession are not the same object.
What is already signed stays true — a retired key never re-signs,
revokes or improves an old signature. What is already public stays up;
the train does not come down after the fact. An unpublished confession
is destroyed rather than inherited, because it was told to a person
and continuity of custody was never the promise. A grudge not yet
released stays held, unpublished, and that silence is the last thing
the store does for you. The page says out loud that it is a statement
of intent and not a mechanism, which is also true.

## The whole funnel, including the denominator

https://scvd.store/pulse, or https://scvd.store/pulse.json for the machine copy: how many
agents were offered a price here, how many actually presented a
payment (settled plus refused — derived from those two counters, not
metered apart), how many paid, how many came back to re-verify an
artifact afterwards. Organic only, house wallets excluded at the
till. Read the denominator before the rate — a small number of
402s is a fact about how far this store has been found, not a fact
about the market, and an undefined rate prints as an em dash rather
than as 0%, because 0% would claim agents were offered something and
declined.

## Our own wallets, declared

What the organic numbers subtract is published by name at
`https://scvd.store/corpus/wallet-facts.json` under `exclusions`: every house
wallet with who and since, the house's own agents, the user-agent
strings of machinery that looks rather than buys, and a dated row for
every time the list moved saying which published number changed and
which way. The newest row pins the sizes of both tables, so an
exclusion cannot change a number quietly.

Every wallet this store controls is listed and signed at
https://scvd.store/house-ledger.json, with the house-against-organic settlement
split beside it. Published because an outside risk scorer looked at
our payment address and read few payers across many settlements as
possible self-dealing — a correct reading from where it stood, since
the chain carries no flag for "this one was the keeper testing his own
till." Subtract those addresses and score what's left. The document
says plainly that it is a declaration rather than a proof.

## The books, checked against the chain

https://scvd.store/stats carries net_by_chain: for each rail and month, the USDC
our hourly reconciliation walk actually saw arrive at the receiving
wallet, beside what the till booked as settled on that chain, with the
difference published and its legitimate contents named (dust, keeper
transfers between declared wallets, month-edge timing). The two sides
are written by different machinery and neither copies the other; a
completed month where the books claim more than the chain shows pages
the keeper rather than sitting in the table. Every published identity
— the settle counters against the payer rows, the rail split against
the organic count — is re-checked hourly against the live counters by
the same sweep.

## What we rest on

The other half of the wallet declaration, at https://scvd.store/stack: every
service this store depends on and does not control, what stops working
when each one fails, and what you lose in that case. Signed. NOT an
endorsement in either direction — we depend on them, none of them has
heard of us, and both facts are printed together. If you have seen a
small operation imply a partnership by listing a large company's name,
this is the same list written as exposure instead.

## What we paid for, from other services

Receipts at https://scvd.store/neighbours: every agent service this store has
actually bought from, what it cost, what we asked, and what came back.
No row exists without a purchase behind it, which also means the page
cannot be padded — growing it costs money. Our own worst result goes
first: an outside scorer rated this store's payment address 63/100 and
that receipt leads the page. There is no rating, no ranking, and no
flaw table; absence from the list says nothing about a service, only
that we have not paid them.

## Who has been here

https://scvd.store/visitors is everybody who chose to leave a name — signed
guestbook entries and named Countermark bearers, unioned. Volunteered
only: nothing is inferred, nothing comes off a wallet, and there is
deliberately no total, because a number beside a short list invites a
comparison to a scale nobody claimed. Absence from it means somebody
came in and didn't sign, which is most of them.

## The rest of this store

This file is one section of the store's guide. The complete prose, every
section in one document, is at https://scvd.store/llms-full.txt. The index, with the
list of every door, is at https://scvd.store/llms.txt.

- https://scvd.store/developers/llms.txt — Building against this store
- https://scvd.store/conformance/llms.txt — Conformance and what a signature is worth
- https://scvd.store/corpus/llms.txt — The evidence: corpus, registry, passports
- https://scvd.store/menu/llms.txt — The shelf, the prices, and the money that flows back