GitHub

Interactive guide / 12

Define your first factory line.

Start with one bounded engineering outcome. Define its evidence, authority, deterministic checks, and human control boundaries. FDLC begins with the work—not the agent.

Output
Factory Definition
Steps
05
Privacy
Browser only
Start the builderSee a completed example →
Step 1 of 5

Choose a bounded class, then state the concrete result.

Required before continuing
  • Choose a work type.
  • Describe a specific engineering outcome.
Design → qualification

A definition is intent. A version is a qualified runtime.

This design-to-qualification handoff sits within FDLC’s governing lifecycle. It produces a qualified factory composition; software delivery still follows intent → planning → execution → evidence → verification → approval → release → outcomes → learning.

  1. You + AI-FDE

    Factory Definition

    Describe the workflow, capabilities, authority, and evidence required.

    Reviewable intent

  2. Accountable human FDE

    Review and approve

    Confirm the design and the authority being delegated.

    Explicit approval

  3. Mission Control

    Validate and qualify

    Check the submitted intent and qualify the exact runtime composition.

    Evidence gate

  4. Mission Control

    Factory Version

    Identify the immutable qualified composition. Release and execution still require authorization.

    Qualified runtime

This builder creates a conceptual definition. It does not submit to Mission Control or authorize execution.

What should I do next?

A Factory Definition is governed intent, not an executed factory.

Explore AI-FDE →Inspect Mission Control →Read intent and specification engineering →