Bid & Evidence Infrastructure

RFP Evidence Desk

Type in your tender's requirement lines, drop the OpenChainGraph artifacts and chain exports that answer them, and get a requirement-by-requirement evidence annex: each row shows its matched artifact, its verified hash and signature state, or an explicit "narrative response, no artifact" marker. Built for government-payments procurement, but the requirement categories are generic; nothing here names a jurisdiction, ministry, or scheme.

⚠ This page assembles artifacts you already hold; it does not parse or extract from your tender document, does not compute a coverage score, and does not host, monitor, or store any transaction data. Every input stays in this browser tab and is gone on reload.
Client-Side Zero PII Extends Shipped Kernels Print-Ready Annex
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Add a requirement row from your tender

Read your tender yourself and type its requirement lines in below, one at a time. This tool never parses or ingests a tender file; a tender is third-party text and reading it is your call, not this page's.

Requirement rows (0)
No requirement rows yet. Add your tender's requirements above.
Drop or paste an OCG artifact or chain export
Drag one JSON file here, or click to choose
Assemble the evidence annex

Joins the requirement rows from tab 1 against the artifacts verified in tab 2, matched by category. A requirement with no matching artifact renders as unmatched, unless you tagged it "narrative"; it is never silently dropped.

§27 approval records (optional, read-only)

This page mints no approval, signs nothing, and runs no queue; SPEC.md §27.0 scope limit. It only displays records you supply and checks whether a role/subject pair clears a threshold of distinct identities.

Drag one JSON file here, or click to choose