The design you agreed to is the design that ships.

The fault

The decision was clear in the room. Then it became a game of telephone.

It started in a meeting. It became an ADR. It got summarized in Slack, re-explained to a developer six weeks later, and arrived in production as something different from what was agreed to. The gap between the design you agreed to and the code you shipped has never been instrumented.

1. 01

   Meeting

   said aloud

2. 02

   ADR

   written down

3. 03

   Slack

   summarized

4. 04

   Confluence

   re-explained

5. 05

   Production

   drifted

6. The cost

   $1.3M–3.9M

   per year · the gap

And the gap used to be a human cost — six weeks, slow drift, catchable. AI agents now read your codebase, generate PRs against it, and execute changes at machine speed. They compound the drift faster than your team can catch it. This is not a future risk. It is a current condition.

The shift

You have tried storage. You have not tried memory.

A wiki is a closet. A search index is a flashlight. A context window is a goldfish. They surface the past; they do not preserve it, accumulate it, or stay accountable to their own reasoning. Memory has three properties — non-negotiable.

1. 01

   Continuous

   Every decision joins one growing record. No fresh chats, no resetting context, no starting over because the last person left.

2. 02

   Reasoned

   The why travels with the what, always. A specification without its reasoning is just an opinion.

3. 03

   Accountable

   Every downstream artifact — spec, test, plan, code, audit — cites its memory of origin. Lineage is the substrate.

Eight stations carry a decision from intent to proof. Beneath them, one substrate holds the reasoning each station must read before it acts. Every name carries the quiet endorsement — by complai.

1. 01

   Sift

   Intent → spec

   Turns ambiguous, partial intent into a structured, reasoned, citable specification.

   UPSTREAM

2. 02

   Moment

   Spec → behavior

   Captures the behavioral fingerprint of the decision — DDD's missing temporal dimension.

   OPEN · STANDALONE

3. 03

   Facet

   Behavior → tests

   Generates the test surface — the falsification criteria — from the behavior, before code exists.

   VISUAL

4. 04

   Codex

   Rules, applied

   Makes compliance load-bearing inside the work — applied to spec, behavior, and tests.

   COMPLIANCE

5. 05

   Forge

   Chain → work

   Turns the decision into sequenced, constrained, agent-ready work that cites its origin.

   EXECUTION

6. 06

   Trace

   Decision → cascade

   Surfaces what a decision threatens — upstream and downstream — the moment it lands.

   GRAPH

7. 07

   Proof

   Ship → evidence

   Answers "did the decision survive?" with a proof, not a postmortem. Violations never block.

   CONFORMANCE

8. 08

   Glean

   Prod → memory

   Feeds what production teaches back into the chain, so the org's intelligence compounds.

   LEARNING

In lived time

Six weeks when memory is rebuilt. Six minutes when memory is walked.

What changes when the chain holds

1. The architect's loop

   The workshop becomes the chain. Same rigor, no ceremony.

   3–6 wk → < 1 day

2. The methodology

   Rigor outlives the team. Quality stops depending on who's in the room.

   12 ppl → 1 + AI

3. The audit

   Compliance becomes a derivative. The auditor reads what the chain already wrote.

   4–6 mo → 30 hr

4. The artifacts

   N documents collapse to one canvas, read by every role before code.

   N docs → 1 canvas

One signature, many voices

The children keep their voice. Complai is the maker's mark beneath it.

Two of the nine — flmnt and Moment — run standalone, open-source, under the mmmnt org. Each owns its own colour and character. The house stays neutral and signs quietly beneath.

How to engage · enterprise only

Start with one specification. Everything else compounds.

We engage by running a real specification against your domain — your services, your business rules, your audit surface — and showing you the chain executing on day one. Terms are quoted against the cost we displace, not seats.

1. 01 · 60 min

   Discovery call

   We map your highest-cost decision drift, scoped to one product domain.

2. 02 · ≤ 1 day

   Live specification

   A converged spec, on one of your real services, before lunch.

3. 03 · 2–4 weeks

   Pilot deployment

   One initiative, end to end, full chain — drift instrumented.