PKPEEK Docs
Docs/Evidence & Reference

Document matching and evidence versions

Resolve ambiguous acquisition associations and review new evidence versions without replacing what findings cite (EV04, EV05).

Authorized evidence reader · Contract specialist

/pdcc/reference/match
Live walkthrough · Document matching and evidence versions
/pdcc/reference/match
/pdcc/reference/versions

Resolve a document match (EV04)

A file like pilot_acceptance_results_demo.pdf might match CT-DEMO-007 (matching pilot title) or CT-DEMO-012 (overlapping program name).

  1. 1

    Open the match

    Reference › Resolve a match.

  2. 2

    Compare candidates

    Using verified identifiers and source context — not title similarity alone.

  3. 3

    Link verified candidate

    Stores actor, evidence and history.

  4. 4

    Or keep unassociated

    Leaves the file unlinked.

Heads up — Cross-tenant matching is prohibited.

Evidence versions and history (EV05)

FieldExample
EvidenceExternal research report for PLAN-026-007
Accepted version2
Incoming version3
Current baselineVersion 2 retained
ChangeDelivery assumptions revised
  • Review impact opens the changed-input review.
  • View accepted version shows what findings currently cite.
  • Prior versions keep governed access and retention independent of module state.
Note — New source content never silently replaces an accepted version.

Related guides

Evidence library and upload

Find authorized evidence versions with provenance, inspect details, and upload governed files through quarantine (EV01–EV03).

Linked work, external packages and handoffs

Register external research or planning packages, accept handoffs, review changed inputs and resolve link conflicts (M01–M14).

Document matching and extracted facts

Link official and internal documents, review extracted facts against exact pages, and keep verified facts separate from new imports (CT03).