Purpose
Assemble the register the Govern engine validates: every candidate evidence item with type, date, area, person, and source identity.
When to use
After scope-map in every run.
Inputs
mapped.json; uploaded evidence indexes/exports (CSV/JSON/folder listings of minutes, audit reports, training records, calibration logs, NCR logs).
Steps
- For each required evidence type, list the items on file: type, date, area, person, doc id.
- Record dates exactly as documented - freshness is the engine's call, not this skill's.
- Write evidence.json.
Output
evidence.json - the register.
Grounding requirements
Every item cites its document id / export row.
Constraints
- Gather only; no completeness or freshness judgments - "the folder looks full" is not a status.
- Never omit an item because it looks old; the engine needs it to prove staleness.
Escalation / uncertainty
Evidence types with zero candidates are recorded as empty, not padded.