GitHub
Menu

FDLC Specification / 06Proposed

A machine-readable contract for governed software work.

The FDLC Specification will formalize portable artifact semantics, lifecycle, state transitions, authority, evidence, and extension points. V0 publishes the shape—not a false standard.

Current state
Pre-standardization
Protocol objects
11
Compatibility
Not yet claimable
Inspect the proposed shapeSee the implementation evidence →
Proposed Pre-standardization draft

No stable FDLC schema is released yet. Mission Control’s implemented domain model is the primary reference, and compatibility must be designed rather than declared.

Artifact chain

Eleven durable protocol objects.

These nouns make the runtime lifecycle inspectable from the initial intent through the learning signal. Implementations may add records without weakening their semantics or transition requirements.

  1. 01IntentExpand

    What outcome matters?

    Named outcome, constraints, owner, and risk
  2. 02SpecificationExpand

    What must be true?

    Versioned requirements, boundaries, and acceptance criteria
  3. 03PlanExpand

    How will the factory achieve it?

    Approved decomposition, sequence, risk, and verification strategy
  4. 04Work OrderExpand

    What bounded unit is authorized?

    Scope, risk, authority, and verification contract
  5. 05AttemptExpand

    What exactly ran?

    Identity, lease, versions, environment, and trace
  6. 06EvidenceExpand

    What was observed?

    Attributable artifacts bound to the exact candidate
  7. 07VerificationExpand

    Does the evidence satisfy the specification?

    Independent checks against exact criteria
  8. 08ApprovalExpand

    May this consequence proceed?

    Authorized, attributable, reasoned decision
  9. 09ReleaseExpand

    What was promoted?

    Exact artifact, current policy, and rollback readiness
  10. 10OutcomeExpand

    Did the intended result hold in reality?

    Observed technical, operational, and user result
  11. 11Learning SignalExpand

    What should change in the factory?

    Attributable outcome and a controlled improvement proposal
Associated objectsAcceptance CriterionAgent IdentityDelegationExecution LeaseTaskCandidate

Entity semantics

What V1 will need to define.

Every object needs portable meaning before independent implementations can safely exchange it. These cards describe the contract surface, not a released schema.

fdlc://v1/intent

Intent

Named outcome, constraints, owner, and risk

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/specification

Specification

Versioned requirements, boundaries, and acceptance criteria

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/plan

Plan

Approved decomposition, sequence, risk, and verification strategy

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/work-order

Work Order

Scope, risk, authority, and verification contract

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/attempt

Attempt

Identity, lease, versions, environment, and trace

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/evidence

Evidence

Attributable artifacts bound to the exact candidate

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/verification

Verification

Independent checks against exact criteria

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/approval

Approval

Authorized, attributable, reasoned decision

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/release

Release

Exact artifact, current policy, and rollback readiness

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/outcome

Outcome

Observed technical, operational, and user result

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics
fdlc://v1/learning-signal

Learning Signal

Attributable outcome and a controlled improvement proposal

Identifier
Stable and globally unique within its authority domain
Lifecycle
Explicit states and permitted transitions
Evidence
Exact subject, provenance, freshness, and integrity
Extension
Namespaced without changing canonical semantics

Versioning model

Stable routes. Explicit evolution.

Versioned namespaces make breaking changes visible and prevent a moving implementation from masquerading as a stable contract.

/spec/v1
/spec/v1/intent
/spec/v1/specification
/spec/v1/plan
/spec/v1/work-order
/spec/v1/attempt
/spec/v1/evidence
/spec/v1/verification
/spec/v1/approval
/spec/v1/release
/spec/v1/outcome
/spec/v1/learning-signal

Use what exists today

Inspect the model before claiming compatibility.

Review the artifact protocol →Inspect Mission Control →Review the source ↗