B.4:4 - Solution
Use the Canonical Evolution Loop to connect the parts of repeated adaptation needed by the question. Recover the subject and its continuity rule, then identify the activities, results and dependencies. Keep proposed steps distinct from phases that occurred; use B.4:4.2 when a claim needs dated Work.
Start from the available observations and results. If they answer the receiving question, return that result without requiring another phase. Keep the subject and use when those grounds support doing so. If a needed premise remains unresolved, state that limit and the contribution still needed. Develop a change or gather further evidence when the remaining decision requires it, reusing adequate results whose conditions still hold.
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 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 episteme or epistemes involved under C.2.1. Assert an EpistemeEditionRelation only when its historical-continuation conditions obtain. State replacement or another direct relation only when its grounds obtain; retain any unresolved continuity question. |
| 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 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 open, state that question rather than hiding it behind the word evolution.
B.4:4.2 - Separate the changed subject from the acting side
Name the acting participant separately from the subject being changed. A System performs each piece of Work. The changed subject, performing System, dated Work, Method enacted by that Work, and result remain distinct. Practitioner prose can 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 dated U.Work occurrence, first recover every 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 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 distinct participants, and establish their parthood in the containing holon independently. Use an external System when the case has one. Apply the same Work-admission and conditional attribution rules above to either acting side.
State authority, responsibility, permission, acceptance, or admission through its predicate, 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. Identify the activities and result dependencies needed for the transition; qualify particular Work claims under B.4:4.2.
| Phase | Question | Output and boundary |
|---|---|---|
| 1. Operate | How is the current subject operating or being used? | Name the current use or operation and any records that exist. Monitoring may occur, but a record does not establish an observation, comparison, or change. |
| 2. Observe | What do records, measurements, testimony, or other evidence show for the use? | Identify the observation, comparison or interpretation and who carried it out when that matters. State the observed basis, finding, hypothesis or unclear cue under the result or evidence rule, including what remains unresolved. A sufficient observation result can finish the question before a change is selected. |
| 3. Refine | What change, if any, does the receiving use need, and what identity relation would it have? | Develop or select a candidate change when needed. Establish the grounds required for its intended use, reusing applicable results and performing any needed revision or tests. State a continuity, successor, substitution, refinement or edition relation only when its endpoints exist and its conditions obtain; otherwise retain the identity question or intended treatment. A selected candidate does not establish availability for renewed use. |
| 4. Deploy | How was the selected change made available for use? | Identify the deployment activity and what it established—for example, a changed or produced entity, publication, configuration, release or availability—under the rule for that fact. Acceptance, admission and later use remain separate claims. |
State transition conditions:
- Operate -> Observe: a named cue, question, monitoring result, or review need requires interpretation.
- Observe -> Refine: the remaining question requires considering a change, and an observed basis or routed cue supports forming that change question.
- Refine -> Deploy: one candidate is selected, the conditions required for that deployment are met, 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 exist; otherwise keep the question open until the change or production has occurred.
- Deploy -> Operate: renewed operation or use begins; availability 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 a preserve-worthy cue needs publication while its interpretation remains open, A.16.1 supplies a PreArticulationCuePack. Use B.4.1 after stabilization when a recipient needs possible continuations or a route choice made explicit. Its routed result can return to Refine or enter another subject pattern when that pattern’s entry conditions hold.
Keep the account proportional. A local answer can identify the current subject, observed basis, what occurred, the supported identity conclusion or open question, and the next use or contribution still needed. A sufficient answer need not complete another phase. Expand to a complete cycle trace when a relying decision, assurance case, audit or later replay needs it; retain missing phases as missing.
Didactic Note: four practical questions
- Operate: What subject is operating or being used now?
- Observe: What has use shown, and who made the observation or interpretation when that matters?
- Refine: What change is being considered, and would it continue or replace the subject?
- Deploy: How was the selected change made available, and what separately established fact now supports the next use?
The gain is a readable connection from an observed basis to a change and back to use, preserving the subject’s identity, the activities and results, and their grounds.