SealedRFQ — Sealed bids. AI scores. Arc awards.

Audit RFQ № 3 ANCHORED · MEMO NOT HELD HERE

An award has to cite a decision anchored on-chain before it. This page re-hashes the published memo and compares it with that anchor, so a rationale edited after the fact fails the check instead of simply reading well. Anyone can repeat it: canonicalise the memo (RFC 8785), take its SHA-256, and read the attestation from the contract.

Decision anchored, memo held elsewherenothing is wrong here

The chain records that a award recommendation was anchored, and the award had to cite it. This agent does not hold the memo behind that hash — the decision came from a different operator, or from one of the demo scripts, and each keeps its own memos.

That does not make the decision unverifiable. Ask whoever produced it for the memo and check it below: the hash on-chain settles the argument, not who hosts the document.

Verify your own copyhashed in your browser; nothing is sent anywhere

Anchored hash0x48d0f8717470df8a212f26ed…

Verificationre-hashed, not re-read

Anchored hash0x48d0f8717470df8a212f26ed…

Anchored by0x90aD2B03…

Modelmock-rubric-v1

Anchor txopen ↗

Why this existsleast privilege, by design

The evaluator can score and anchor but cannot award. The awarder can award, but only the bidder named in an anchored recommendation. Neither can rewrite the reasoning afterwards, because the hash was fixed before the award existed.