Next Project Contacts
An open fitted tool case on a dark workbench, every precision instrument seated in its own cut foam recess.

AI-native delivery

The AI engineering kit we work inside.

The tooling, review rules and guardrails we use on client code: what assistance is allowed, what has to be human-checked, and how the evidence is kept.

Contacts Technology map

Assisted engineering is now standard practice. Documenting how it is governed is not. This page describes the tools and rules our engineers work inside, published so you can hold us to them.

A fitted foam tool tray on a dark bench with precision instruments seated in cut recesses and one recess empty.

The questions this raises first

  1. What the kit contains

    • Assisted editors and review tooling, configured per project rather than per developer
    • A shared prompt and context library for this codebase, kept in the repository
    • Generated-code review rules that are stricter than our hand-written ones
    • Evaluation harnesses for any feature that calls a model
    • Cost and usage reporting, per project, visible to the account team

  2. The rules that matter to a client

    Client code and client data do not go into tools that train on them. Assistance is allowed for writing, refactoring and test generation. It is not allowed to be the last reviewer of anything. Every change is read by a named engineer before it reaches your branch, and that has not changed.

  3. Where it genuinely helps

    Tests, migrations, boilerplate, documentation, the second implementation of a pattern already agreed. Work where the shape is known and the typing is the cost.

  4. Where we keep it out

    Architecture decisions, security-sensitive code, anything touching money or personal data, and any place where a plausible-looking wrong answer is expensive to detect. QA and testing does not get more relaxed because a tool wrote the first draft — it gets less.

  5. Why we publish this

    Because the alternative is a client discovering it from a commit message. If your procurement team has a question about tooling, ask it during discovery. We answer in writing.

  6. What it is not

    It is not a productivity claim. What the kit measurably saves is on productivity gains, with the caveats attached.

    Back to the AI map.

Discuss the next step

Tell us what you want to build or improve. We reply with a plan, an indicative budget and a start date.

Contacts Browse the service map