WTKRESEARCH + ENGINEERING

PUBLISHED REFERENCE MATERIAL

Follow the claim to its evidence.

Start with a research question, inspect the proposed architecture, then separate implementation observations from validation evidence and open gaps. Publication here does not make a pattern true.

WTK / TARGET-STATE FLOW

Governed artifact lifecycle

Implemented
GOVERNING CLAIM

Creation, qualification, promotion, projection, deployment, operation, rollback, quarantine, and retirement are different states.

BUILD → QUALIFY → PROMOTE → PROJECT → OPERATE → INVALIDATE
  1. 01
    CandidateStructure exists, but readiness is not inferred.
  2. 02
    QualificationEvidence is evaluated against a declared scope.
  3. 03
    PromotionAn accountable authority permits projection.
  4. 04
    OperationDrift, failure, and revocation can narrow readiness.
FOLLOW PRIMARY FLOWLEFT / TOP→RIGHT / BOTTOM
READ THE FLOW

Find every transition that requires evidence or authority, then identify the explicit paths for remediation, invalidation, quarantine, and rollback.

  1. 01

    Lifecycle states are not interchangeable labels.

  2. 02

    Qualification precedes promotion.

  3. 03

    Projection never changes the canonical package.

  4. 04

    Failure paths remain visible after deployment.

WTK IMPLEMENTATION OBSERVATION

WTK separates candidate packages, evaluation readiness, qualification, promotion, deployment projection, invalidation, and remediation.

REMAINS UNPROVEN

Long-duration drift detection, revocation propagation, fleet rollback, and policy migration require sustained operational trials.

FALSIFICATION PRESSURE

Long-term drift · Human trust

CANONICAL SOURCEdiagrams/artifact-lifecycle.mmd

Topology and labels are source-controlled. Presentation is supplied by the site renderer.