Evidence Pack.

What it is

The current Evidence Pack path creates a prelaunch sample export for workflow testing. It is a structured, agent-readable shape for reviewing timestamps, warnings, and human-review items before source-backed export is launched.

Every ABR, GST, VIN, and PPSR row in this path is synthetic test data or unsearched. The pack is not a source result, organisation or asset verification, certificate, clearance, or proof that a register query ran.

No search, check, entity/asset-monitoring event, or register query automatically creates this sample. Entity and asset monitoring is unavailable. See /trust/afsa-b2g/ for the current AFSA access posture.

What is inside an Evidence Pack

Every Evidence Pack contains:

• Verdict. A sample workflow status. It is not a source finding, legal opinion, certificate, or clearance.
• Source rows. Synthetic test-data or unsearched entries that name the intended source and explicitly state that no current query result exists.
• Timestamps. When the sample export was created. This is not a source retrieval time. ISO 8601, UTC.
• Certificate metadata. Reserved sample fields only. The current export contains no official source certificate or AFSA PPSR certificate metadata.
• Review signals. Fixture-derived workflow prompts. They are not findings raised by a current source check.
• Confidence. A sample contract field, not confidence in a current source response.
• Human review items. Items that require a human to decide before acting. For example: "Registered security interest found. Confirm discharge before settlement." Hoist surfaces these; it does not resolve them.
• Due Diligence Record. Not produced by the current Evidence Pack path. No current source-backed workflow produces a Due Diligence Record PDF.

How agents use it

The current Evidence Pack is created only when an authorised caller explicitly requests the separate sample-export path. An agent can inspect its structure and fixture labels, but must not cite it as proof that a source check ran. Supported source tools return tool-specific verification responses; verify_counterparty returns an Evidence Card plus a pack_id, and that identifier does not prove that a pack was persisted or exported.

Common agent patterns:

• Inspect the future export shape without treating fixture rows as source evidence.
• Test how a workflow surfaces sample human-review items.
• Retain the explicitly requested sample export only as test material.
• Use a tool-specific verification response when a decision needs current source evidence.

The Evidence Pack sample shape is separate from available source tools. An ABN lookup, counterparty check, or other supported tool returns its own documented response; those checks do not automatically create this export. The schema reserves a future PPSR shape, but PPSR preview, paid search, and certificates are not currently customer-accessible.

View a sample Evidence Pack in the sample response page. The sample response page returns deterministic examples with no signup required.

How it differs from a receipt

A receipt in the accounting or payment sense confirms a transaction occurred and records the cost. An Evidence Pack is not that.

The current Evidence Pack is an explicitly requested prelaunch sample export. It contains fixture or unsearched rows and sample review prompts; it is not the answer from a source check, a Due Diligence Record PDF, or a payment record.

The word "receipt" sometimes appears in casual conversation about Hoist ("show me the receipt for that search"). That usage is fine as conversation. It is not the product term. The product term is Evidence Pack.

Hoist provides source-cited evidence. It does not guarantee that a transaction is safe, legal, compliant, or financeable. Hoist does not currently offer paid register searches. BSB/account details do not prove account control.

How it differs from an AFSA certificate

An AFSA certificate (also called a search certificate) is the official PDF issued by the Australian Financial Security Authority when you run a PPSR search. It is a legal document. AFSA issues it. AFSA holds the authority over its content.

Hoist does not alter or reissue AFSA certificates. If AFSA issues a certificate for a search run directly through AFSA, cite that official certificate. Hoist PPSR preview and paid search are currently unavailable, so Hoist does not currently return a PPSR result, certificate, or certificate metadata.

create_due_diligence_pack currently returns a non-persisted sample JSON object. It does not produce a Due Diligence Record PDF, and neither that sample nor the Evidence Pack sample is an AFSA certificate.

See /trust/afsa-b2g/ for the current access boundary. Hoist PPSR preview and paid search remain unavailable; use AFSA direct or another established provider for a live search today.

What Hoist does not infer

Hoist checks sources and reports what they say. It does not infer, predict, or guarantee.

Specifically, Hoist does not:

• Infer that a business is safe to transact with because the ABN check passed.
• Claim that an asset is broadly clear or free of encumbrances from a PPSR result. Hoist PPSR is currently unavailable, and any AFSA-direct result still needs its own stated scope and human review.
• Confirm that a counterparty's bank account belongs to the entity named unless a supported source says so.
• Infer legal compliance from source data.
• Predict future insolvency, default, or fraud risk.
• Guarantee the accuracy of AFSA register data. AFSA is the source; Hoist reports what AFSA returned.

The review signals in the current Evidence Pack are fixture-derived sample prompts. They are not source findings or model predictions and cannot support a real-world clearance decision. For supported checks, use the tool-specific source-cited verification response and keep human review in the decision path.