The engineering standard

Accelerator front of house. Brakes built into the chassis.

A system that watches a payment claim or an option deadline has to be right, and has to be able to show why it is right. Governance is not a separate product on this site. It is the standard every build is held to, fitted before the first document is read.

No training on your data. No offshore routing. No orphan facts.

Sheet 01 · Why the standard exists

What is acceptable for a chatbot is not acceptable for a deadline.

Most AI tools flatten documents into text and hope the meaning survived. Tables become paragraphs. The clause number detaches from the clause. The chain back to the source page disappears, replaced by a confidence score. For a conversation, that is fine. For an option deadline, a payment claim, or anything a lawyer or adjudicator might one day read, it is not.

Sheet 02 · Fitted as standard

Five commitments, on every build.

These are not options or tiers. They are the conditions a Lumen & Lever system has to meet before it is allowed near a decision.

01 · Traceable

No orphan facts

Every output cites its source document and page. If the system makes a claim, you can open the page it came from and check it yourself.

02 · Private

Your data stays yours

Your environment or private Australian hosting. No training on your data. No offshore routing.

03 · Reviewed

The system drafts; your people decide

Named human review points before any output is relied on. The system assembles and proposes. A person signs.

04 · Audited

A record of what it did

A log of what the system read, produced and flagged, kept for the life of the engagement.

05 · Honest

Confidence is reported, not performed

Uncertain extractions are marked uncertain. The system tells you where it is sure and where it is not, rather than presenting every answer with the same confident tone.

Sheet 03 · The point

The controls are not a product we sell you.

Other firms sell governance as an engagement: a framework, a workshop, a register that sits beside the system and describes what it ought to do.

We build the controls into the system itself. They come fitted as standard, on the Proof Week build and on every build after it, at no separate line item.

Built on Sourcetrace, our document-structure engine, which preserves layout, tables, annotations and page evidence before anything reaches a model.

  • Front of house

    A working system your team uses to find money and meet deadlines.

  • In the chassis

    Traceability, privacy, review, audit and honest confidence, fitted underneath it.

  • No separate sale

    You do not buy the brakes. They are part of the build.

Sheet 04 · Next step

Hold the build to a standard you can defend.

01 · Scoping call

Thirty minutes. You describe the documents and where you suspect leakage. We tell you which lane fits and whether a Proof Week is worth your money. Sometimes it is not, and we say so.

02 · Proof Week

We sign your NDA, take a sample of documents, and build. Five days later you watch the system run on your own record.

03 · Your call

Production build, or a findings register and a handshake. No retainer, no lock-in, no deck.

Book a scoping call

Or write direct: hello@lumenandlever.com · Melbourne, Australia