Vealth · EcoWealth · Digital Provisioning Protocol
We keep a company's digital estate alive. Each review is sealed and anchored.
This page explains EcoWealth’s Digital Provisioning service, for companies that want their website kept discoverable, accessible, fast and readable by AI. We review it, fix it and maintain it on a loop, the way a safety program runs: scheduled, measured, never "done once." Every review we produce is sealed the moment we write it, which means a fingerprint of its exact content is recorded. The combined fingerprint of everything we have sealed is anchored onchain in a weekly batch. Sealing is immediate and the anchor follows with the next batch. The status of the current root is stated plainly below.
How the work is proved
Every review runs the same way, whatever the sector: a full-estate scan with real metrics (speed, weight, accessibility, machine-readability), credit for what is already strong, and a drafted, paste-ready fix for what is not. Security-sensitive findings go to the organization they concern. Public case studies show only what anyone can see from outside. What is public is the method and the timestamp: each artifact is hashed and anchored before it leaves our hands, so whoever receives it can prove when it was written without taking our word for it. Check any hash yourself.
What "digital provisioning" means
The full estate, measured
Every public page and subdomain, driven like a real visitor: load speed, page weight, accessibility (alt text, contrast, ADA), and whether search engines and AI assistants can actually read it.
Drafted, not just named
The exact files that close each gap (titles, sitemaps, the invisible labels search and AI read, the discovery files) written out and ready to paste. Yours whether or not you hire us.
On a loop, not once
A standing crew that ships improvements on a cadence and measures the result: the difference between a site that was built well once and one that stays sharp.
Sealed and dated
Every deliverable fingerprinted and the portfolio root anchored onchain, where it cannot be changed, so the record of what we found, and when, is independent of anyone's word.
The same discipline, pointed the other way
Everything above proves an estate is alive: measured, maintained, and sealed so the record does not depend on our word. The identical machinery answers a second question, and it is the one that is about to matter more.
Is this site safe to act on? Somebody hands a domain to the assistant they already pay for and lets it spend money. That assistant has no way to tell a real business from a convincing copy, and an assistant asked to spend on an unfamiliar domain should refuse. A lookalike can duplicate any page byte for byte. What it cannot do is forge a blockchain, a certificate log, or a signature over its own domain name.
Digital provisioning
For the owner. Every page measured, every fix drafted, every deliverable hashed and the root anchored. Proof that the estate is being kept.
The Safety Card
For the visitor and their AI. A published document of claims, each carrying the check that proves it, plus the things it openly cannot prove. Read ours at vealth.net/is-this-safe.
The rule both halves share: a card supplies claims and the procedure that tests them. It never supplies a verdict. "This site is safe" is not a statement anyone should accept, including from us, which is why the format forbids it and the checker rejects it. What a reader's own client cannot finish is shown as unfinished, never as a pass.
The format is written down as a spec with a blank template and a validator, so this is something another site publishes about itself rather than a badge we hand out. We do not certify anyone. The whole family lives at the security program: the live posture read your browser runs itself, the safety checks, the card protocol, the proof registry, and the named list of what none of it proves.
The part no one else offers: provable, immutable, first
We use the exact discipline we recommend to others, on ourselves. Every file we author is content-addressed with SHA-256; those fold into a per-engagement hash, and all of those fold into one portfolio root hash. You can reproduce any file-level hash from your own machine against a file you hold, with no wallet and no blockchain access. Our source repository is private, so an outside reader can check a file we sent them, not the whole portfolio.
Verify the file-level hashes yourself. Rehash any file we wrote and sent you with shasum -a 256 <file> and check it against the entry we quote for that file. Our provenance record is kept privately, so ask us for the entry for your file.
Onchain status, stated plainly: the portfolio grows with every new engagement, so the root above changes with it. An earlier version of this record was anchored on Regen Network’s public chain, tx B4AAAF35648102F1A77DCB55DCA6AF71C3267D313D8E64C2CE914AC33E16AA45. That anchor proves the record as it stood then. It does not cover the root shown above. Anchoring costs well under a cent and lands in the same weekly batch that seals the rest of the site's proof records. Until a batch covers a root, treat it as reproducible but not yet sealed onchain.
Honest scope: an anchor proves recorded-first and tamper-evident: that a given exact version of the record existed, authored by us, at that time. It does not claim exclusivity (others could independently find the same things) or that any company adopted anything. Provenance, stated precisely.
On privacy
Security-sensitive findings go to the organization they concern. Public case studies show only what anyone can see from outside, because a review is a gift to its subject, not a callout. What's public is the capability and the proof: that this body of work exists, to this standard, sealed and dated. Any company is welcome to be named once we're working together.
Buy it as a call
The method above is also available as four self-serve paid calls. Any agent or developer can pay per call, no signup, no conversation with us. Each answers in seconds with the artifact, and each response says plainly what it does and does not prove.
| Door | Price | What comes back |
|---|---|---|
POST /.well-known/vealth/x402-readiness | $0.10 | Can the payment registries see you as paid and discoverable? Verdict plus the exact fixes. |
POST /.well-known/vealth/agent-readiness | $0.25 | Can an agent read you, understand you, and know what you sell? Scored teardown, a fix per gap. |
POST /.well-known/vealth/agent-kit | $0.50 | Starter agent guide, agent manifest, and llms.txt built from your own public pages. |
POST /.well-known/vealth/provisioning-package | $5.00 | All three composed, plus a prioritized fix plan. The whole engagement, self-serve. |
Send {"url":"https://yoursite.com"}; the unpaid response is a standard 402 payment challenge naming the price and where to pay (USDC, a digital dollar, on the Base network, or USDG). Deterministic document scans of public signals; none of your endpoints are called, nothing is deployed to your infrastructure. The prices in this table are copies; the 402 a door itself returns is the authority, and if the two ever disagree, believe the 402.
Who this is for
A company whose digital front door (storefront, careers board, resident services, product data) is quietly costing it customers, candidates, or trust, and who wants it kept sharp on a loop. Or a partner who wants to back this work, or introduce it to a company that needs it.
Digital provisioning is concept work from public signals only, offered proof first. Some company reviews are published openly on the portfolio page, with corrections invited; every figure can be re-checked by the method it states. The portfolio root hash and its onchain anchor are reproducible from public commands. "Provable, immutable, first" means recorded-first and tamper-evident, not exclusivity, endorsement, or adoption by any named company.