Assurance context
Verification, integrity lock and admissibility define what must be reviewable before reliance.
Procurement-Safe Minimum Evidence Request
This route defines the public evidence request before protected diligence. It now follows the Governance Architecture, Assurance Layer and FieldTrace integration so reviewers can ask for minimum proof without exposing live programme records publicly.
Public artefact boundary.
This page links only to public artefacts bundled in the v442 search index. Reliance-grade evidence, live programme records and reviewer notes remain in protected workspaces.
Evidence requests remain minimum, scoped and procurement-safe.
The evidence request asks for the minimum proof needed to test governance, evidence, attribution, assurance and auditability. It is not a public data room and does not create a reliance decision.
Field attribution
FieldTrace evidence can be requested through protected intake when field-level attribution is required.
Protected boundary
Live evidence, reviewer notes and identity-bound logs remain in protected diligence workspaces.
Minimum evidence requests now hand off to the Protected Evidence Request Engine.
The public request remains procurement-safe and minimum. Protected evidence receipt, admissibility checks, lock conditions, rejection and escalation are governed inside PERE.
The evidence request is the bridge into committee export readiness.
Minimum evidence is requested so the protected room can test proof, close assurance and, where appropriate, prepare a controlled committee export package with a clear reliance boundary.
Minimum evidence request now feeds the protected assurance room.
Requested proof objects become the structured intake for verification dossier creation, gap tracking, integrity locking and export-register release controls.