Developed across a working company.

HAI’s internal reference deployment connects company information, departmental workflows and operational controls across multiple machines. It developed through successive stages of source integration, working methods, access controls, monitoring and verification. HAI Seed brings that foundation to other companies, with the initial scope agreed around their sources, people and priorities.

HAI Seed starts by reading approved information, analysing it and preparing work for review. A connected deployment adds company-system connections and supervised routines, workflow by workflow. The examples below describe the internal reference deployment; each customer setup is scoped separately.

Validation across the company’s AI work.

A successful run is only one piece of evidence. Sources, outputs, access, delivery and follow-through need separate checks.

The reference deployment was examined across four machines and the workflows they supported. Its validation covered registration, adversarial testing, fixes and later manual re-checks.

  1. 1

    Establish what is running

    Map scheduled work, sources, recipients and responsibilities. Identify stale jobs and the controls that apply to each route.

  2. 2

    Trace the work end to end

    Look beyond a successful process exit. Inspect the input, the produced output and whether it reached the intended recipient.

  3. 3

    Challenge the assumptions

    Check stale or missing inputs, machine-specific controls and differences between written rules and the running system.

  4. 4

    Record and address findings

    Keep a finding tied to its evidence. Change affected controls and repeat the relevant checks.

  5. 5

    Re-check the checker

    Return to original records and test the audit’s conclusions. Correct findings when the evidence does not support them.

The published September record

On 2 September 2026, an adversarial audit completed 311 evaluations across four machines and recorded 102 findings. Examples included jobs that reported success while producing incorrect output or reaching nobody. The affected controls were changed during that week.

On 20 September 2026, 20 findings were sampled and manually re-checked against the original logs. 19 held; one was an error in the audit. The checker had reported an alert as missing after reading blocked attempts, although a later entry recorded delivery. That finding was corrected and the checker changed to inspect the final delivery state.

This is a dated record of the internal AI deployment, including the audit’s own correction. It is not a claim that every finding was closed or that every customer installation has the same controls.

Green is not the same as right.

Eight jobs, all finished without error. The audit went further: it opened the output and checked the source and delivery records. Explore what those checks revealed.

Illustrative jobs. The three failures are real findings from the 2 September audit, with names removed. Runs in your browser; nothing is sent.

A sequence of operational workstreams.

  1. April

    Knowledge base. Company mail, chat and documents made searchable in one place.

  2. May

    Core functions. Enquiry handling, quote drafting, onboarding paperwork, live reads of the ERP and the accounts, a decision queue for the responsible people.

  3. 31 May

    Governance. A registry of every running job, a gate on outbound email, written operating rules.

  4. June

    Quality gates. A sanity check on every draft, alerts when a data feed stops, a supervisor over the functions.

  5. July

    Stop controls and census. One master stop, plus a check that every acting job is registered to it. A census of all jobs, with stale ones retired. An automatic-send pilot under explicit grants. Regression evaluations.

  6. August

    Hardening. A fail-closed stop rule, a dedicated customer-facing machine, the records function rebuilt, employee starter packages, operating rules reconciled with the running system.

  7. 2 Sep

    Adversarial audit. 311 evaluations across all four machines.

  8. 20 Sep

    Manual re-verification. 20 audit findings re-checked by hand against the original logs.

Functions in the reference implementation.

In this reference deployment, HAI reads source systems, prepares drafts, runs checks and sends authorised follow-ups. Process owners keep approval. Customer workflows are selected, configured and validated separately.

Enquiries and quotes

Read incoming requests, price them against stock and history, and draft quotes. Approved offers can send automatically under set rules, with manual-only control for any customer.

Purchasing

Track purchase requirements, request supplier offers, and record each offer in the system.

Finance

Read cash, receivable and payable balances from their source systems, with bank data taking precedence over book records.

People

Handle staff questions and paperwork. Sensitive records require explicit access scope; a job title alone is not an access grant.

Market

Read market and regional sources each morning and report only the items that changed, with the source next to each.

Meetings

Convert recordings into minutes and track the follow-ups. Attendance is taken from the recording, not the invitation.

Marketing

Extract publishable signals from internal meetings, with figures and names removed and a verification note on each item.

Knowledge

Store mail, chat, meeting and deal records in separate access-controlled logs, so restricted material is excluded from shared summaries.

Controls

Verify recipients, apply the lowest permission in any group, screen payment language, keep the ERP read-only by default, and audit the layer's own output.

Controls.

Recipient verification

A message must name its recipient in two independent places, and both must match, or it is not sent.

Scope gate

Outbound drafts are classified, every recipient including copies is checked, and the lowest permission in the group applies.

Payment language

Messages containing payment or bank instructions are held unless explicitly released, and every decision is logged.

Figure freshness

A financial figure is re-pulled from its source when the draft is written. If the source is stale, the figure is withheld.

ERP access

Read-only by default. Only approved quoting functions write, to their own records, through one audited path.

Outbound channels.

In the reference implementation HAI sends through four outbound channels. Each has explicit authorisation, controls, logs and a way to stop it. A new company starts with none, and adds a channel only when it approves it.

  1. 1

    Internal email. Capped per recipient per day and in total, screened for confidential content, listed in a daily digest.

  2. 2

    Customer quotes. Enabled only while an explicit arming file is present. A price floor applies to every quote. Any account can be set to manual only.

  3. 3

    Marketplace submissions. Separate stop control.

  4. 4

    Public stock listings. Explicit arming, daily cap, separate pause.

One master stop covers all four channels.

Two fixed rules: HAI does not sign documents and does not move money. Stop events report to the responsible person through a separate path.

How it is wired.

Nine inputs, one operating layer, six recipient groups, four outbound channels.

How the operating layer is wired Nine inputs on the left feed one operating layer governed by four rules. On the right, six recipients. Four outbound channels, each gated, all covered by one master stop. The layer does not sign documents and does not move money. INPUTS Approved mailboxes WhatsApp working groups ERP: stock, quotes, orders Accounting and bank feeds Parts marketplaces Calendars and meetings Shared documents Fleet and market data Its own decision log Operating layer: four rules 1 Related signals groupedone report, relationship stated 2 Routed to the process ownerdecision items only 3 Figures from the system of recordfailed source check: item withheld 4 Recorded recipient, recorded actionsproposal, approval, execution, confirmation KNOWLEDGE ingested, deduplicated, dated. Facts with a source outrank text. CONTROLS monitoring, recipient verification, scope gate, payment-language guard, ERP read-only by default, self-audit. FIXED RULES Does not sign documents. Does not move money. Stop events report to the responsible person through a separate path. RECIPIENTS Owner: daily summary Sales: priced, checked quotes Purchasing: items to chase Finance: source-fresh figures Marketing: publishable signals People: privacy-restricted OUTBOUND CHANNELS each authorised, gated, logged, revocable Internal email, capped Customer quotes Marketplace submissions Public stock listings ONE MASTER STOP COVERS ALL FOUR
  1. 1

    Related signals are grouped. Items that belong together are reported in one place, with the relationship stated.

  2. 2

    Decision items go to the recorded process owner. Items that need no decision are not sent.

  3. 3

    Figures come from the named system of record. They are pulled when the report is created. When a source check fails, the item is withheld and marked for correction.

  4. 4

    Each recommendation has a recorded recipient. Actions are recorded as proposal, approval, execution and confirmation.

Registry figures of the reference implementation.

As of 20 September 2026. These describe the internal deployment, not what every new customer gets.

219
scheduled jobs running on four machines, including jobs that monitor other jobs.
313
jobs registered over the project's life, 33 retired.
40
capabilities, each tied to a credential and a policy.
38
written policies.
202
schedules.
16
internal delivery channels.
4
outbound channels.
1
master stop.

The experience becomes your starting point.

HAI Seed carries the methods developed through real operational work into a deployment shaped for your company.

The foundation includes company context, reviewed working methods and explicit responsibilities. From there, the chosen sources, role environments, tools and validation steps are scoped with your team.

For a new company, the deployment process covers discovery, source and access review, knowledge and rules, workflow configuration, validation and handover. It can expand into additional roles and dedicated machines as useful work is established.

Explore the deployment stages

Plan your HAI setup.

One important workflow, the teams involved and the sources behind it. We will help define the starting scope.

Get in touch