#GMMWorks / How GMMCode works

#GMMCode Build & deliver

How GMMCode works

GMMCode is the delivery product inside #GMMWorks. Requests arrive through ITIL-style service tiers, the engagement's shape decides which specialists join the pod and which gates apply, a governance mesh checks every artefact, and everything lands in an evidence bundle you can export.

The LLM is swappable.The governance is not optional.

01 The flow

A front door, an AI pod, a governance mesh, an evidence bundle.

  • Engagement shapes for build, review, audit, documentation, migration, forensics, continuous compliance, RFPs, hotfix, maintenance, problem management and release trains. Each shape declares its roles, gates and deliverables.
  • Specialist roles including business analyst, architect, developer, SDET, reviewer, security, DBA, UI developer, release manager and SRE. No role approves its own work.
  • Works with the LLM of your choice. The LLM is swappable without touching governance, standards or the audit trail. Today it runs on AWS.
02 The gates

The build gates, in the order a story meets them.

A failed gate stops the story and routes it back with the reason on record. Work continues only when the gate passes or a person decides.

Design

Architecture, data and acceptance criteria agreed before any code.

Implementation

Built test-first. A red integrated build blocks this gate.

QA, review, security

Three independent checks of the same change, each with its own verdict.

qacode_reviewsecurity

Scope adherence

Built what the story asked for, and only that.

Release readiness

Deployable, observable and reversible.

Change authorisation

A person approves, with the evidence bundle in front of them.

03 Decisions with full context

Every role reads what the customer actually asked.

An AI role that sees only a one-line ticket guesses. In GMMCode every role decides from the full context of the work.

The customer's own words

The original request, not a paraphrase of it.

The spec and the scope

Acceptance criteria, design notes and what is out of scope.

The ticket history

Earlier verdicts, rejections, follow-ups and approvals.

The conversation

What the pod and the people have already said and decided.

04 Governance that respects the spec

Checks that cite the rule, and judge only what applies.

Every artefact goes through a mesh of specialist checkers: tools first (scanners, SBOM, licence policy), then small governance language models that must cite the standard they apply. One registry decides which checks may block a delivery.

  • 35 specialist checks run on every code change. Nine objective standards checks may block; 26 judgement checks advise.
  • In scope, or a follow-up. A finding outside the story's scope does not silently reject the work. It is recorded as a follow-up, filed in Jira, and listed to you when the work closes.
  • Provenance on every verdict: model, prompt hash, registry version and tool versions.
  • Supply chain in the bundle: OSV scanning with KEV and EPSS, a CycloneDX SBOM, licence policy.
05 Tests and integration

Built in parallel. Merged safely. Fixed properly.

The defects that hurt are the ones between features that each passed their own tests. GMMCode treats integration testing as part of delivery.

It fixes the app, not the test

When a test fails, the developer agent diagnoses the failure from the evidence (test output, logs, the diff) and fixes the application, rather than weakening the test until it passes.

Every story ships an integration test

GMMPlan writes the test plan; the QA gate refuses a story without its planned test.

A merge train

Parallel work is integrated in dependency order, and a red integrated build blocks the implementation gate.

Results on the board and in Jira

Integration results ride on the board's cards and are written back to Jira, with a project CI gate and a coverage census that can only go up.

06 Human approvals

The approval is the product.

AI does the work; people make the calls. GMMCode opens on what is waiting for you, explains it in plain words, and records your decision in a way an auditor can check.

  • Policy, not habit. Approval policies per decision type, segregation of duties enforced at decision time, quorum groups.
  • Nothing silently expires. Due times from the tenant SLA, reminders, an escalation chain, delegation and out-of-office.
  • Signed record. Every decision is pinned to the artefact version it approved and lands in the evidence bundle.
Waiting on you · 3Demo tenant · Northwind Retail
Change authorisation · NWS-25 payment retry
code_build · due in 6h · v ed1551
6 gate verdictsintegration 12/12SBOM1 follow-up filed
UI mockup v2 · Wallet top-up screen
ui_mockup_approval · revision 2 of 3
Plan: Northwind Payments, wallet top-up and refunds
plan_approval · 6 stories · 8 plan rows

Dev and test environments can auto-decide approvals; every such decision is labelled "bypassed". Production never bypasses.

07 From a live run

It approves, and it rejects.

Unedited captures from a live run: roles signing their own gates, and an architect and a code reviewer sending a change back because the design missed an edge case.

Architect and code reviewer both reject a change because the design does not define handling of invalid numeric input
Architect and code reviewer · rejected at design
Architect gives the design approval for the service request
Architect · design gate · approved
Tester approves the QA gate for the change
Tester · qa gate · approved
Developer hands the change off for QA
Developer · hand-off to qa
08 Progress by area

#GMMWorks builds itself by its own rules.

The platform's own backlog runs on the same board. Status as of 3 Oct 2026: 509 of 624 stories and bugs done (82%).

GMMPlan · planning
Requirements → Jira34/34
Legacy modernization planning21/25
Integration-test planner8/9
GMMCode · delivery
Delivery pod (core, messaging, speed)40/41
Process shapes (hotfix, maintenance, release)17/21
UI developer role11/15
Autonomous delivery (merge, CI, deploy)9/14
Specialist roles11/19
Governance and approvals
Approvals experience21/24
Role guidance from standards17/25
Quality checkers and standards16/24
Platform architecture gaps13/20
Support, experience, testing
GMMDesk with ServiceNow and Azure DevOps24/24
UI: flows, approvals-first, self-service46/49
Communications and knowledge base21/23
Full cycle on the Kanban board8/11
Integration testing, own build3/12
Integration testing as a product feature3/10

Headline counts are live from the GMMCOD, GMMUI and GMMDSK projects on 3 Oct 2026; the per-area bars are the 1 Oct 2026 snapshot. Ops, defects and self-hosting work (105 of 134 done) is left out of the chart. Integration testing is the newest work and the furthest from done.

See GMMCode on your own backlog.

A pilot starts from your Jira backlog. GMMPlan turns one requirement into stories, GMMCode builds them on your board, and you approve each gate.