FPF Reference

Explore → Shape → Evidence → Operate

Pattern B.5.1 · Stable Part B - Trans-disciplinary Reasoning Cluster

Every successful innovation, from a new piece of software to a scientific theory, follows a predictable evolution (state transitions). It begins as a fuzzy idea, is gradually given a clear structure, is tested against reality, and finally, is put into operational use. Without a shared map of this lifecycle, teams often get stuck: developers might endlessly refine a structure without testing it, while analysts might gather evidence for an idea that has not yet been clearly defined.

Keywords

  • development cycle
  • lifecycle
  • state machine
  • Explore
  • Shape
  • Evidence
  • Operate.

Relations

B.5.1builds onCanonical Reasoning Cycle
B.5.1route stepMethod Quartet Harmonisation
B.5.1outline parentCanonical Reasoning Cycle
B.5.1outline next siblingAbductive Loop

Content

Problem Frame

Every successful innovation, from a new piece of software to a scientific theory, follows a predictable evolution (state transitions). It begins as a fuzzy idea, is gradually given a clear structure, is tested against reality, and finally, is put into operational use. Without a shared map of this lifecycle, teams often get stuck: developers might endlessly refine a structure without testing it, while analysts might gather evidence for an idea that has not yet been clearly defined.

Problem

How do we provide a simple, universal state machine that guides an artifact's journey from a raw concept to a reliable, operational holon? This pattern defines the four canonical states of this journey, providing a clear roadmap for teams and a stable framework for project management.

Solution

FPF defines a four-state development cycle model for any artifact (U.Episteme or U.System). An artifact transitions from one state to the next as it accumulates rigor and evidence. This state machine is driven by the Canonical Reasoning Cycle (Pattern B.5).

The Four States of an Artifact's Lifecycle:

StateCore ActivityManager's View: What It MeansDriven by Phase of Reasoning CycleTypical AssuranceLevel
1. ExplorationGenerating possibilities. The focus is on brainstorming, questioning assumptions, and generating multiple, often competing, hypotheses."We are in the 'what if' phase. All ideas are on the table. We are looking for a plausible path forward."Abduction (Pattern B.5.2)L0
2. ShapingDefining a single, coherent form. The most promising hypothesis from the exploration phase is selected and given a rigorous, internally consistent structure."We've chosen our direction. Now we are building the blueprint, defining the architecture, and ensuring all the pieces fit together logically."DeductionL0 → L1 (if formalization counts as TA)
3. EvidenceTesting against reality. The shaped artifact is subjected to rigorous empirical or formal tests to validate its claims and measure its performance."The blueprint is done. Now we are at the proving ground. Does it actually work? We are running the tests and gathering the data."InductionL1 → L2
4. OperationDeploying and monitoring in a live environment. The validated artifact is put into production, where it performs its intended function and is monitored for ongoing reliability."It's live. The system is in service, delivering value, and we are monitoring its health and performance."Continuous Induction (Monitoring)L2 (maintained)

Didactic Note for Managers: Aligning States with Your Project Plan

This state machine is not an abstract theory; it maps directly to the familiar phases of any well-run project.

  • Exploration is your R&D or initial discovery sprint.
  • Shaping is your design and architecture phase.
  • Evidence is your QA, testing, and V&V phase.
  • Operation is the live deployment and maintenance phase.

By using these four states, you can instantly communicate to your team and stakeholders exactly where an artifact is in its state transition, what the current focus is, and what needs to happen to move to the next stage.

Conformance Checklist

  • CC-B5.1.1 (State Explicitness): Every artifact in a project MUST be tagged with its current state from the set {Exploration, Shaping, Evidence, Operation}.
  • CC-B5.1.2 (Sequential Progression): An artifact SHALL progress through the states in sequence. Skipping a state (e.g., moving directly from Exploration to Evidence without Shaping) is a process violation and must be explicitly justified in the artifact's rationale.
  • CC-B5.1.3 (Reasoning Cycle Alignment): The transition between states MUST be triggered by the completion of the corresponding phase of the Canonical Reasoning Cycle (Pattern B.5). For example, the transition from Shaping to Evidence requires the completion of the deductive analysis.

Consequences

BenefitsTrade-offs / Mitigations
Clear Project Visibility: The state machine provides a simple, shared language for tracking the maturity of every artifact in a project.Risk of Bureaucracy: If applied too rigidly, the state machine could feel like a waterfall process. Mitigation: The cycle is meant to be rapid and iterative. A single artifact might cycle through all four states within a single sprint. The goal is clarity, not ceremony.
Improved Focus: Each state has a clear primary activity, which helps teams focus their efforts and avoid common pitfalls like premature optimization or untested designs.-
Reduces "It's Done" Ambiguity: The states provide a precise definition of "done" for each phase. An artifact is not "done" with Shaping until its structure is coherent and its consequences are deduced.-

Rationale

This pattern operationalizes the Principle of State Explicitness (P-9). By giving every artifact a clear, unambiguous state, FPF transforms the often-chaotic process of innovation into a structured, manageable, and auditable development cycle. This state machine provides the "scaffolding" upon which the more detailed cognitive work of the Canonical Reasoning Cycle is performed, ensuring that every idea is systematically guided from a speculative guess to a reliable operational reality.

Relations

  • Is driven by: B.5 Canonical Reasoning Cycle.
  • Organizes the progression of: B.3.3 Assurance Subtypes & Levels.
  • Provides the states for: B.4 Canonical Evolution Loop.

B.5.1:End