An Evidence Pack is a structured Hoist export designed for an agent, human reviewer, or audit trail. The current public create_evidence_pack path is a prelaunch sample: every ABR, GST, VIN, and PPSR row is fixture or unsearched and is not a source result, verification, certificate, or clearance. Supported current checks return source-cited Evidence Cards instead.
What an Evidence Pack contains
- Verdict: a fixture-derived summary, not a source-backed clearance
- Source rows: one explicitly fixture or unsearched entry per represented source; a row does not mean the source was consulted (see Source check)
- Timestamps: when the sample was assembled; source freshness remains unavailable where no source was queried
- Certificate metadata: no current sample includes an official PPSR certificate
- Risk flags: fixture-derived review prompts, not source-backed findings (see Risk flag)
- Confidence: a sample contract field, not confidence in a current source picture
- Human review items: actions that cannot be resolved from source data alone (see Human review item)
- Due Diligence Record: not produced by the current Evidence Pack sample export; no current source-backed workflow or PPSR call produces a Due Diligence Record PDF (see Due Diligence Record)
Evidence Pack vs Due Diligence Record
The current Evidence Pack is a persisted prelaunch sample export. The separate create_due_diligence_pack path returns a non-persisted sample JSON object; it does not produce a Due Diligence Record PDF. An AFSA search certificate is a separate official source artefact produced for a PPSR search run through AFSA. Hoist currently returns no PPSR certificate and does not present a sample PDF as one.
Why agents need this
AI agents cannot reliably reason about whether a transaction is safe, legal, or financeable using only their training data. Australian registers are authoritative sources that change in real time. Supported Hoist checks therefore return source-cited Evidence Cards. The current Evidence Pack export only demonstrates a future structured record shape and must not be treated as current register evidence.
The sample export makes fields such as review prompts and next actions easy to inspect without implying that its fixture or unsearched rows came from a live source.
How Hoist uses this
Available Hoist Connector verification tools return source-cited Evidence Cards through MCP, API, or CLI. The separate Evidence Pack export is a prelaunch sample with fixture or unsearched rows. The schema reserves future PPSR fields, but PPSR preview and paid search are not currently customer-accessible and do not return an Evidence Pack, price, result, or certificate.
Sample responses use sample data and are marked that way. Approved access can enable supported available sources such as ABN; it does not turn sample exports into source evidence or unlock PPSR preview or paid search.
What Hoist does not infer
The current Evidence Pack sample reports fixture or unsearched rows and cannot support a real-world clearance decision. Source-cited Evidence Cards from supported checks also do not conclude that a transaction is safe, approved, or compliant. Hoist does not currently return a clean or adverse PPSR result.
Related terms
- Source check: an actual verification step or an explicitly fixture/unsearched row, as labelled by provenance.
- Risk flag: a discrepancy or anomaly surfaced by available source checks or sample data.
- Human review item: an action within an Evidence Pack that requires human judgment to resolve.
- Due Diligence Record: Hoist's own PDF for supported workflows, not an AFSA certificate.
- Hoist Connector: the agent-facing access layer (MCP, API, CLI).
- PPSR: a future Hoist contract; preview and paid search are currently unavailable.
- ABN: business identifier verified by available ABN source checks.
- NPII: AFSA's National Personal Insolvency Index, a separate person-insolvency register that is not currently enabled as a Hoist source.