The ecosystem · the chain

One decision, walked from intent to verified production.

Eight stations carry a decision down the chain — specification, behavior, tests, rules, plan, dependency, proof, adaptation. Beneath all of them, one substrate holds the reasoning every station must read before it acts. No link is skipped. Nothing is lost.

The chain visualised

The chain, end to end intent → verified production
  1. 01 Sift Intent → spec
  2. 02 Moment Spec → behavior
  3. 03 Facet Behavior → tests
  4. 04 Codex Rules, applied
  5. 05 Forge Chain → work
  6. 06 Trace Decision → cascade
  7. 07 Proof Ship → evidence
  8. 08 Glean Prod → memory

flmnt the reasoning substrate the why every station reads before it acts

The eight stations

each holds · each remembers

  • 01 Sift UPSTREAM

    Intent → spec

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

    Holds the specification, and what it was derived from
  • 02 Moment OPEN · STANDALONE

    Spec → behavior

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

    Holds how the system should behave, over time
  • 03 Facet VISUAL

    Behavior → tests

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

    Holds what would prove the decision wrong
  • 04 Codex COMPLIANCE

    Rules, applied

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

    Holds which rules applied to which decision, forever
  • 05 Forge EXECUTION

    Chain → work

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

    Holds the plan, and why each task exists
  • 06 Trace GRAPH

    Decision → cascade

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

    Holds the dependency graph and its lineage
  • 07 Proof CONFORMANCE

    Ship → evidence

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

    Holds the evidence, traced to the decision
  • 08 Glean LEARNING

    Prod → memory

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

    Holds what the world taught, fed back in

Two of the nine run standalone

The open pillars carry value with zero Complai dependency.

flmnt and Moment ship open-source under the mmmnt org. The community runs the full pipeline without knowing Complai exists; the platform is optional acceleration around them.

Where it sits

Every neighbour holds part of the picture. None hold the chain.

Adjacent categories each remember one slice and lose the rest. Complai holds reasoning, dependency, and consequence in one substrate — walked end to end.

How adjacent categories compare to Complai's chain.
Category What it holds What it loses
ADRs · docs Holds the decision text Loses everything downstream of it
Internal dev platforms Holds the service catalog Loses the reasoning behind every entry
GRC · audit tooling Holds the control Loses the architecture the control is checking
Observability Holds what happened Loses what was supposed to happen
Coding agents Holds the prompt and the diff Loses every prior the diff should honor
complai holds the chain — reasoning, dependency, and consequence in one substrate, walked end to end.

See one decision walk the chain.

We run a live specification against your domain and show you the chain executing on day one — your services, your rules, your audit surface.