Agentic Product Lifecycle

How we assure quality, and when

Every concern stays covered when agents do the building, and judgement stays with people. Nothing waits until the end.

In our product lifecycle agents do most of the building, so quality is built into the work rather than run as a phase 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 what needs judgement: a review, an exploratory pass, a sign-off. Some checks, such as an external penetration test, we apply where an engagement warrants them, and each says when.

  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-observe

    Machine
    Where agreed

What is covered

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