How we make

How we assure quality, and when

Every change has to meet the same standard, whoever or whatever wrote it.

Because we make with agents, quality is built into the work rather than tested at the end. A build passes five moments, from the day we inherit a codebase to the day it is live, and the skill that owns each moment does its part. Machines run the checks a tool can assert. A named person does the rest: a review, an exploratory pass, a sign-off. Some checks, such as an external penetration test, we add where an engagement warrants them.

  1. At the start

    of an engagement, on what we inherit

    mxa-stack

    Machine
    Where agreed

  2. On commit

    every save-point

    mxa-verify-precommit

    Machine

  3. On pull request

    every push, and before it merges

    mxa-verify-prmxa-verify-merge

    Machine
    Person
    Where agreed

  4. Before production

    before real users

    mxa-verify-promote

    Machine
    Person
    Where agreed

  5. In production

    continuously

    mxa-monitor

    Machine
    Where agreed

What is covered

  • Code style
  • Code quality
  • Logic and components
  • Critical journeys
  • Design intent & correctness
  • Accessibility
  • Visual consistency
  • Design system
  • Motion
  • Browsers & devices
  • Performance
  • Errors & uptime
  • Search & AI visibility
  • Dependencies
  • Security