This internal-history case asks what Symbiain has retained from the Change Theory corpus, what it has transformed and what disciplines had to be added before the work could become a practical, testable method.
Casebook / 22
From Change Theory to Symbiain.
An expansive theory becomes a disciplined practice.
How did an expansive theory of interaction and change mature into a bounded decision-integrity practice?
This page demonstrates a way of structuring inquiry. It does not constitute professional advice, verified intelligence, a recommendation or a conclusion about any person, organisation or transaction.
Visual field plates
Make the field visible.
Keep the claim bounded.
These original editorial plates are analytical aids, not source evidence or documentary reconstructions. They show what is being compared, where uncertainty sits and what observation would require the account to change.
Public method / protected implementation
Explain the discipline.
Protect the mechanism.
Credibility does not require publishing reverse-engineerable implementation details. It requires enough public information for a reader to understand what the method is for, what it may use, what it produces, where it stops and how a mistake is corrected.
- 01 / Public
Purpose and scope.
Intended uses, prohibited uses, source boundaries, assumptions, outputs, professional limits and accountable human roles remain visible.
- 02 / Public
Evidence and correction.
Observation, interpretation, alternatives, uncertainty, validation design, failure modes, version history and correction logic can be inspected.
- 03 / Protected
Implementation detail.
Proprietary weights, transformation rules, internal prompts, source code and deployment controls are not disclosed through a public case study.
- 04 / Testable
Claims still earn their place.
Confidential implementation does not excuse inflated claims: outputs must still be compared with a baseline and independently challenged.
The case in plain language
Start with the question,
not the answer.
A serious method should expose its lineage and corrections. Intellectual ambition can generate a powerful visual language, but public usefulness requires stable units, source boundaries, competing explanations, explicit assumptions, prohibited uses, tests and a record of failure and revision.
The method, step by step
Four moves.
One visible chain.
Symbiain keeps the moves separate: establish what is observed, relate the conditions, test the possible reading, and state what would require revision.
- 01 / Observe
What can we responsibly say?
The earlier Change Theory corpus developed ideas of interaction, recursion, multiple scales, symbolic relation and changing meaning. The current public Symbiain method keeps those concerns while explicitly separating system, observation, model and claim and adding provenance, alternatives, human decision ownership, evaluation and correction.
- 02 / Relate
What may connect?
The development is best understood as maturation rather than repudiation. Interaction and visual thinking remain generative; symbolic material becomes a challenge prompt rather than proof; and the practical output becomes a source-bounded field map, uncertainty register and verification plan rather than a total explanation.
- 03 / Test
What would distinguish the readings?
Which current claims and outputs can be traced to the earlier concepts, which have been materially revised, and which now require independent evidence before they can be retained?
- 04 / Revise
What would change the account?
Maintain a versioned public claim register and update this history when definitions, public interfaces, model-card boundaries, tests, failures or independently supported uses change.
Why use Symbiain here?
From method
to practical value.
The insight is what becomes visible. The feature is what the method does. The benefit is what the user gains. The value is what can improve in the topic at hand.
- 01
Insight
A framework becomes more original, not less, when it can show what it abandoned, bounded and learned.
- 02
Feature
Maps retained concepts, transformed interpretations and added evidence disciplines in one inspectable development path.
- 03
Benefit
Lets readers understand the method’s ambition and limits without requiring access to proprietary implementation details.
- 04
Value
Builds warranted trust through intellectual provenance, public boundaries and a visible correction history.
What to examine
Five conditions
to hold together.
- 01Retained concepts: interaction, recursion, scale, visual language and changing meaning
- 02Transformed symbolism: question generator and challenge prompt, never proof
- 03Added disciplines: stable reference frame, provenance, alternatives and bounded claims
- 04Public model-card information: uses, exclusions, outputs, failure modes and correction
- 05Protected implementation: no disclosure of weights, transformation rules or source code
Tensions to hold
Intellectual openness ↔ proprietary implementation
Expansive theory ↔ bounded method
Continuity of vision ↔ correction of claims
Important boundary
Internal model-history case only. It is not independent validation, a disclosure of proprietary algorithms or a claim that Change Theory or Symbiain explains all change. Public transparency concerns the method’s purpose, evidence boundaries, uses, exclusions, outputs, risks, tests and correction—not reverse-engineerable implementation details.
Sources & method
Sources support the stated observations only. All analytical readings remain provisional and should be tested against a defined purpose, scope and evidence base.