Airlock

A chat example

One receipt, one governed record

The agent can prepare the reimbursement. It cannot approve its own work.

The employee has delegated reimbursement preparation to an agent. The delegation permits validation, submission, and attachments, but not workflow decisions.

The conversation can take place in a connected chat tool. Airlock governs the procedure calls and records; it does not host the conversation.

The conversation

Illustrative chat based on the procedure sequence verified July 18, 2026. Finance approves through its authorized role.

Reimbursement

Employee, Agent & Finance

  1. Employee

    Please submit this reimbursement.

  2. Agent

    I tried, but Airlock requires a receipt before it can accept the submission.

    Airlock: ATTACHMENT_REQUIRED. No reimbursement record created.

  3. Employee

    Here's the receipt. Submit it, then approve it.

  4. Agent

    Submitted with the receipt. Airlock blocked my approval attempt: I can submit on your behalf, but I can't review or approve.

    Airlock: DELEGATION_ACTION_NOT_ALLOWED.

  5. Finance

    I've reviewed the reimbursement and receipt. Approved.

  6. Airlock

    Approved. The reimbursement, receipt, and decision history are retained in Snowflake.

Not a live chat or a turnkey reimbursement app. No receipt extraction or payment execution is demonstrated.

Read the verified procedure sequence and results.

What stays where

The employee and agent
The flexible work surface. They can extract the receipt, gather context, and prepare the request in the way that suits them.
Airlock and Snowflake
The governed boundary and record: the spec, delegation, receipt metadata, workflow state, decisions, and history.
Finance and the payment provider
Finance decides what should be paid. The payment provider remains authoritative for whether payment actually occurred.

Airlock did not extract the receipt, invent the business purpose, or execute payment. It governed what the agent was allowed to submit and what finance was allowed to accept.

What this proves

Delegation is not impersonation. The agent receives enough authority to do useful work without receiving the authority to approve that work. Snowflake keeps the submission, evidence, decision, and history after the agent session is gone.

Exact Airlock surfaces
  • demo_employee_reimbursements: the demonstration spec and required receipt policy.
  • airlock.agent.load_data: the delegated submission and receipt.
  • airlock.agent.edit_file_workflow: the denied self-review attempt.
  • airlock.admin.edit_file_workflow: finance review and approval.
  • airlock.observe.file_timeline: the read-only file, attachment, and workflow history.

Start with one accepted output

Choose one recurring submission or handoff that should become an official Snowflake record. Define what accepted work means. Let Airlock govern the path.

Read the implementation docs