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 system context

Partially supported
GOVERNING CLAIM

Authority, package source truth, runtime execution, evidence, outcomes, and research remain distinct parts of the system.

AUTHORITY → EXECUTION → EVIDENCE → LEARNING
  1. 01
    AuthorizePurpose and policy define the permitted work.
  2. 02
    PackageCanonical contracts remain source truth.
  3. 03
    ExecuteA target projection runs inside bounded controls.
  4. 04
    ObserveReceipts and outcomes support limited conclusions.
FOLLOW PRIMARY FLOWLEFT / TOP→RIGHT / BOTTOM
READ THE FLOW

Follow where authority enters, where the package remains canonical, and how evidence returns to research without becoming authority by itself.

  1. 01

    Authority enters separately from cognition.

  2. 02

    The package stays canonical across projections.

  3. 03

    Consequences occur through mediated runtime actions.

  4. 04

    Evidence informs governance; it does not become authority.

WTK IMPLEMENTATION OBSERVATION

WTK separates goal intake, canonical packages, qualification, target projection, runtime activity, and evidence records.

REMAINS UNPROVEN

Equivalent enforcement across intelligence substrates, runtime targets, and organizational boundaries has not been established.

FALSIFICATION PRESSURE

Intelligence-substrate independence · Cross-harness equivalence

CANONICAL SOURCEdiagrams/system-context.mmd

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