A government payment programme tender asks for proof: end-to-end processing, reconciliation, audit trails, identity assurance, data migration, and a clean exit. Most of that is already a signed OpenChainGraph artifact. This guide shows what already computes, what the new assurance chain closes, and how the RFP Evidence Desk turns both into a bid-ready annex, one requirement row at a time.
Nothing here branches. A step that is not wanted is simply not run, and every artifact the pack touches is something an operator generated deterministically from inputs they supplied in their own browser. This is not the procured payment platform, not a transaction dashboard, and not a hosting offer.
A person reads the tender and types each requirement into the Evidence Desk's Requirements panel, tagged by category. This step stays manual, deliberately: no parser, no extraction step, no uploaded-tender ingestion. A tender is untrusted third-party text, and parsing it is a surface this suite does not need.
The shipped government-payment-lifecycle chain covers collection, netting, disbursement, reconciliation, audit trail, and separation of duties. The government-payment-programme-assurance chain (§3 below) covers the three requirement rows that lifecycle coverage does not reach: identity assurance, data migration, and exit portability.
The Evidence Desk's Pack panel takes the resulting artifacts, checks each one's execution_hash and any signature, lays them against the requirement rows a reader tagged, and prints a bid-ready evidence annex. Every unmatched requirement renders as unmatched, never silently omitted and never rolled into a score.
Approval records minted elsewhere are displayed read-only by the desk's Sign-off panel, showing role, subject hash, acting identity, and whether a threshold is met by distinct identities. The page does not mint, sign, queue, or store any approval itself.
These requirement categories map onto shipped OpenChainGraph nodes, already bound into the government-payment-lifecycle chain. A reader supplies the tender's own language for each row inside the Evidence Desk; the categories below are generic, never a specific tender's wording.
| Requirement category | Coverage | Status |
|---|---|---|
| Collection & disbursement | Collection receipt and bulk disbursement integrity nodes, including duplicate and split-payment checks | Shipped, in chain |
| Reconciliation | Daily reconciliation attestation, including vanished-exception handling | Shipped, in chain |
| Audit trail | Audit-trail completeness across transactions and user activity | Shipped, in chain |
| Access control | Separation-of-duties matrix check | Shipped, in chain |
| Netting & multi-currency residuals | Netting and residual-handling nodes | Shipped, in chain |
| Identity & authentication for onboarding agencies | Identity-proofing assurance level | New chain, §3 |
| Historical data migration | Payment data migration completeness | New chain, §3 |
| Vendor exit & data portability | Operator exit data portability | New chain, §3 |
Some tender lines describe a property of the delivered system rather than a determination over programme data: PCI-DSS compliance, encryption in transit and at rest, multi-factor authentication, a centralised transaction dashboard, API connectivity, and training or change management are all narrative-response categories in the Evidence Desk. Cost, milestones, and references stay commercial and out of scope entirely.
Three nodes bind the parts of a payment programme's lifecycle that government-payment-lifecycle does not reach: entering the programme, migrating historical data into it, and leaving it. A linear chain, carrying no gate, so the existing composite hash preimage stays exactly as it was.
Assurance level for an onboarding agency's identity proofing, ahead of programme entry.
Open node →Whether historical payment data arrived complete once migrated from the prior system.
Open node →Whether the operator can hand programme data back in a portable form on exit.
Open node →No new kernel and no new node were needed to close these three rows: all three already computed. The chain's job is binding, not invention.
The RFP Evidence Desk is where the four moves in §1 happen. It follows the same tabbed shape as the site's other composers: a Requirements panel for typing or pasting tender lines, an Artifacts panel for dropping or pasting OCG artifacts and chain exports (each verified client-side by recomputing execution_hash), a Pack panel that joins the two and prints the bid annex, and a Sign-off panel that displays any supplied approval records read-only.
It mints no hash, holds no signing key, shows no transaction view or monitoring dashboard, stores nothing between visits, and never renders a coverage percentage or readiness score. An unmatched requirement is always shown as unmatched.