B.4:4 - Solution
Use the Canonical Evolution Loop as a coordinating cycle, not as a universal identity rule. First recover the exact subject and what continuity means for it. Then name the actual Systems and dated Work, traverse only the phases that occurred, and connect the result to renewed use.
B.4:4.1 - Name the subject and continuity question
| Subject kind | State before using the shared cycle |
|---|---|
| System | Name the current System and the relevant continuity or transformation rule. State whether the changed System remains the same System or whether a successor System is identified. Use A.1 for System recognition, A.3.4 for an actual bounded change of the continuing System, and A.15.PROD when the claim concerns first existence through production Work. |
| Episteme | Identify the earlier and later epistemes under C.2.1. Assert an EpistemeEditionRelation only when its historical-continuation conditions obtain; otherwise state replacement or another direct relation. |
| Method | Identify the current Method under A.3.1. If intended results, participant meanings, admissible conditions, safety bounds, semantic basis, acceptance criteria, or composition change, state whether the result is a refinement, substitute, or distinct successor Method. Use B.1.5 when order-sensitive composition is current. |
| MethodDescription | Identify each exact claim-bearing episteme under A.3.2 and C.2.1, and any obtaining edition relation. A later description does not by itself change the Method it describes. |
| Work | Identify each dated occurrence under A.15.1. Completed Work is not revised: later review, repair, deployment, or follow-up is other Work, even when the occurrences belong to one longer effort. |
Not every holon is an adaptation-loop subject, and the five branches are not interchangeable. If the continuity or successor relation is still open, keep that question explicit rather than hiding it behind the word evolution.
B.4:4.2 - Separate the changed subject from the acting side
The subject does not observe, refine, or deploy itself by grammatical convenience. A System performs each actual piece of Work. The changed subject, performing System, dated Work, Method enacted by that Work, and result remain distinct. Practitioner prose can still say “the engineer refined the design” or “the controller adjusted the valve” when that recognizable actor and action are enough. If that ordinary sentence is all the receiver needs, do not open a technical Work account. If B.4 identifies one particular dated U.Work occurrence, first recover every actual performer’s A.13 core and independently admit the Work under A.15.1 from its performance history, enacted Method, temporal extent, and containing System. Add F.6 only when the receiving claim also needs precise assignment-bound attribution. A short B.4 account may omit an unused assignment identifier or classification only when every relation it consumes remains recoverable.
The performing System need not be external to the larger holon. For internal adaptation, apply the A.12 reflexive split: identify the changed subsystem or part and the acting subsystem or part as exact, distinct participants, and establish their parthood in the containing holon independently. Use an external System when that is what the case actually has. For any particular dated U.Work, recover every performer’s A.13 core and independently admit the occurrence under A.15.1; add F.6 afterward only when precise assignment-bound attribution is current. Name an assignment in the short B.4 account only when the receiving claim uses its identity. State authority, responsibility, permission, acceptance, or admission through its own direct predicate, actual participants, and applicability basis; neither a phase label nor Work supplies them.
B.4:4.3 - Keep the four phase claims distinct
These phases distinguish questions and results, not necessarily disjoint clock intervals. Operation and observation can overlap; state the actual Work occurrences and any result dependencies needed by the transition.
| Phase | Current question | Output and boundary |
|---|---|---|
| 1. Operate | How is the current subject actually operating or being used? | Name the current use or operation and any records that actually exist. Monitoring may occur, but a record does not by itself establish an observation, comparison, or change. |
| 2. Observe | What do records, measurements, testimony, or other evidence show for the named use? | Name the observation, comparison, or interpretation Work. Separately identify the observed basis, finding, hypothesis, or still-unclear cue through the direct result or evidence rule that actually applies; Work has no generic result field. Observe does not yet choose a change. |
| 3. Refine | What change should be developed and tested in response, and what identity relation would that change have? | Name the design, revision, selection, and testing Work. Separately identify the selected candidate and the subject-specific identity question or intended treatment. State a continuity, successor, substitution, refinement, or edition relation only when its exact endpoints exist and its own conditions obtain. Refine does not make the candidate available for renewed use. |
| 4. Deploy | What concrete deployment Work occurred for the selected candidate? | Name that Work. Then state separately what actually happened—for example, a changed or produced entity, publication, configuration, release, or availability—using the rule that establishes that fact. Acceptance, admission, and actual later use remain separate facts. |
Use explicit transition conditions:
- Operate -> Observe: a named cue, question, monitoring result, or review need requires interpretation.
- Observe -> Refine: the receiving use has an observed basis or a routed cue from which a change question can be formed.
- Refine -> Deploy: one candidate is selected and its subject-specific identity question or intended treatment is explicit. State an obtaining continuity, successor, substitution, refinement, or edition relation here only when both endpoints already exist; otherwise keep the question open until the relevant change or production has occurred.
- Deploy -> Operate: actual renewed operation or use begins; availability alone does not close this transition.
Evidence is not a fifth phase. Evidence relations warrant the observed basis, candidate choice, transition, or renewed-use claim when a receiver relies on them. Evidence can be produced or used during several phases without duplicating those phases.
B.4:4.4 - Connect neighbouring cycles without collapsing them
The Canonical Reasoning Cycle (B.5) can supply reasoning Work within Observe and Refine. The B.5.1 development states and B.4 phases coordinate, but they are not a one-to-one implementation: a finding may reopen Exploration or Shaping, evidence use can support Evidence, and renewed use can enter or return to Operation.
When Observe finds only a weakly articulated cue, use the optional B.4.1 sequence Notice -> Stabilize -> Route. Its routed result can return to Refine or enter another subject pattern. That sequence does not replace the four B.4 phases.
Keep the account proportional. A local repair can name only the current subject, observed basis, actual Work, resulting identity relation, and next use. Expand to a complete cycle trace when a named relying decision, assurance case, audit, or later replay needs it. Never invent phases merely to make the record look complete.
Didactic Note: four practical questions
- Operate: What exact subject is operating or being used now?
- Observe: What has actual use shown, and through whose Work?
- Refine: What change is being considered, and would it continue or replace the subject?
- Deploy: What deployment Work occurred, and what separately established fact now supports the next use?
The gain is a readable connection from an observed basis to a real change and back to use, without losing subject identity, performers, Work, or evidence.