Skip to main content

Proof

The requirements someone else asks of your organization, what counts as evidence for each one, and the dated record you hand over when they ask.

Proof is a framework layer, not new capture. It maps an external requirement — a statute, a state framework, a funder's terms — to records CommonGage already holds elsewhere: obligations, events, participations, expense entries. It adds no engagement data of its own; every fact it reports already lives in core or in another module.

What it tracks​

  • Checklists — a named requirement set, with the individual requirement items inside it and the authority each one comes from
  • What counts as evidence for each item — chosen from any domain the organization is entitled to, optionally narrowed by conditions, with a note explaining why it counts
  • Dated, frozen evidence snapshots — a point-in-time capture of one checklist, at one scope, that can be handed to an auditor or program officer and voided (with a reason) rather than silently replaced

What it reports​

  • For a given checklist and scope, three states per item — met, not met, or not configured — never collapsed to a simple pass or fail. "Not configured" itself distinguishes a few different reasons: nobody has said what counts yet, the module the evidence lived in is no longer enabled, or the records chosen can't be resolved site by site
  • Three measures published to Goals & Measures: total requirement items, items with a match, and items without one

Who uses it​

Org admins choose what counts as evidence for a requirement and issue snapshots. Org admins, zone coordinators, and building staff can all read the live checklist and any snapshot within their own scope — Proof is not an admin-only surface, even though configuring it is.

Why it matters​

The compliance mapping most organizations keep in institutional memory and planning documents becomes a record — produced on demand, dated, and citable, rather than reassembled by hand every reporting cycle. Proof shows what the organization's own records already prove; it does not certify or generate evidence on its own, and it never treats a gap in one module's data the same as a gap nobody has bothered to configure.