Status: Non-normative research program. Its hypotheses remain under investigation unless and until accepted through the GSM Change Proposal process.

1. Program mandate

Systemics is the paradigm. GSM is a candidate systemics model — a generative, definition-centric embodiment under test, not the paradigm itself.

This program investigates one question:

What must a generative systemics model represent so that organization, purpose, regulation, observation, and adaptation remain accountable — including whether current GSM primitives, roles, and grammar are sufficient, excessive, or incomplete?

Current GSM is the baseline candidate, not a freeze. Research may propose adding, splitting, merging, relocating, or withdrawing primitives, roles, or grammar when the systemic consequences are explicit. A result that cannot state its relation to purpose, variety, operational closure, recursion, or viability is not ready, whether or not it fits current GSM.

The program seeks an explicit causal model without assuming its taxonomy. It treats the governance chain as an explicit research object and uses teleology as a flexible test, not as a causal category.

The following remain outside the mandate:

  • quality scoring, ranking, or treating any Quality formula as adopted;
  • a survey of systemics or governance theories for its own sake;
  • implementation architecture, runtime topology, or processor design.

2. Program quality criteria

A chapter, case, or decision is adequate only when it satisfies these criteria. They define program quality; they are not additional research objects.

ID Criterion Test
C1 Scientific method fidelity Observation, problem, question, hypothesis, and finding remain distinct. The baseline records current knowledge only.
C2 Intent–problem–question alignment Intent frames the theme. Problems determine questions. Questions do not smuggle answers.
C3 Falsifiability Every live hypothesis names a discriminating test, a counterexample class, and a stop condition.
C4 Evidence adequacy Claims rest on cited artifacts, executed cases, or formal derivation. Method menus are not evidence.
C5 Internal consistency Frontmatter, maps, chapters, and decisions do not pre-answer what the protocol keeps open.
C6 Systemics paradigm fidelity Inquiry and results are judged first against the systemics accounts. Current GSM is the candidate model, not the paradigm and not a freeze.
C7 Level separation Research method is not modeled as a GSM relation. Production, authorization, scope, and activation stay distinct unless a finding unifies them.
C8 Decision hygiene One decision is one fork. Duplicates are merged. Status is not a record role. Resolution requirements are usable.
C9 Placement discipline Core GSM, GSM ontology, or derived view is a result of tests, not a recurring paragraph.
C10 Formalization discipline Formal objects appear only when they constrain inquiry. Inventories do not replace results.
C11 Workstream economy Each chapter owns one explanatory burden. Overlap is declared, not recopied.
C12 Program actionability A next investigator can run the next test without inventing the method.

Passing C1–C12 makes the program scientifically usable. It does not make a result normative.

3. Research workstreams

Each workstream owns one burden. Other chapters may depend on it; they do not repeat it.

Workstream Systemic burden Does not own
Causal Model Organization, purpose, function, and viability evaluations; which relations to keep, add, or reject Role topology, DNA production occurrence
Governance Chain Regulation, feedback, variety, and operational closure as an explicit chain Relation taxonomy, production identity
DNA Production Autopoietic production of DNA and lifecycle handoff Chain roles
Cases Executed discriminating examples Decision ownership
Decision Register Authoritative forks Inquiry narrative

4. Research protocol

Each thematic chapter uses the same research logic. Its top-level sections follow this order:

  1. Research intent and scope: why the inquiry exists, what domain it covers, and what remains outside its boundary.
  2. Current state of knowledge: only what authoritative GSM artifacts explicitly represent, what they make derivable, and what existing GSM ontology artifacts already define.
  3. Phenomena and research problems: numbered P-xx-n records of observed phenomena, conceptual tensions, or representational gaps relative to that current state. Absence from GSM belongs here, not in the baseline.
  4. Research questions: numbered Q-xx-n questions derived from stated problems. A question cites the problem it reduces.
  5. Candidate classifications and hypotheses: numbered H-xx-n alternatives. Each hypothesis cites a question and names one falsifier.
  6. Method and evidence: numbered E-xx-n evidence, including executed cases from the corpus. Evaluation menus without execution are not evidence.
  7. Findings and representation implications: numbered F-xx-n results supported by stated evidence, including negative or inconclusive results. Placement is compared only for findings that constrain representation.
  8. Decisions and dependencies: every normative fork links to the Decision Register.

Record prefixes are CM Causal Model, GC Governance Chain, DP DNA Production, and CASE for corpus items.

Research records use the following roles. These are not interchangeable states of one claim, and they are not Decision Register statuses:

Record role Meaning
Research intent Purpose and scope of an inquiry; frames but does not determine its findings
Baseline statement Documentary claim about what current authoritative GSM or GSM ontology artifacts represent or derive
Phenomenon Reproducibly identified behavior, pattern, consequence, or conceptual occurrence requiring explanation
Research problem Warranted discrepancy, contradiction, explanatory gap, or representational gap
Research question Bounded question whose answer would reduce the research problem
Hypothesis Testable candidate explanation, relation, classification, or solution
Evidence Documentary, formal, empirical, operational, or counterfactual material used to assess a hypothesis
Finding Result supported by the stated method and evidence, including negative or inconclusive results
Candidate outcome Finding mature enough to assess for representation and promotion

An observation is a means of producing evidence about a phenomenon. A Need or requirement is not an observation: it is a normative or design conclusion that requires an identified subject, purpose, condition, rationale, and supporting evidence.

Preferred terms in this program: Adverse condition rather than Pain; role signature, schema, or relation rather than contract, except for a GSM Change Proposal; identity, ownership, scope, activation, or operationalization rather than capital; governance chain as a research object, not as something GSM already requires. Named relation families are instruments, not an accepted taxonomy.

5. Source hypotheses

The following inputs are source hypotheses. Declarative wording is not acceptance. Each live row owns one claim. Merged rows remain visible so original wording is not lost.

ID Class Source hypothesis Bound record
SH-01 Organization A Structure is a purposed organization of Mechanisms that governs their operability and Quality. Q-CM-04, H-CM-04, GOV-D23
SH-02 Constitution A Directive that defines a purpose and the operability of that purpose constitutes a Structure. H-GC-04, GOV-D12
SH-03 Recursion A Structure may structure other Structures. Children are derivable from Directives owned by the parent. H-GC-05, GOV-D07
SH-04 Membership May a Mechanism belong to several Structures, or to none? Q-CM-05, H-CM-06, GOV-D24
SH-05 Production DNA is produced by Mechanisms and should reference the producing Mechanism. H-DP-04, GOV-D04
SH-06 Scope DNA applies to Ascriptions and should reference the Ascription it applies to. Scope is what a Directive directs and what a Norm evaluates. H-DP-05, GOV-D02
SH-07 Specialization Where a Directive applies to a Structure, a Norm applies to a Mechanism. H-DP-06, GOV-D03
SH-08 Merged Process topology of Governance, Regulation, and Supervision. Merged into SH-17. SH-17
SH-09 Merged Structure-level ownership of those roles. Merged into SH-17 as a placement variant, not a second signature. SH-17
SH-10 Generation An Operator produces a Structure from Directives and a Mechanism from Norms. A produced subject may reference the Operator Mechanism. H-GC-07, GOV-D06
SH-11 Compliance A governing Mechanism emits control consumed by a Compliance Mechanism and applied to a compliant Mechanism. H-GC-08, GOV-D05
SH-12 Autopoiesis A compliant Mechanism is ascribed by a Compliance Mechanism of its owning Structure and may reference that Compliance Mechanism. H-GC-09, GOV-D01, GOV-D20
SH-13 Identity A Structure has an identity of Directives and Norms. Identity, ownership, scope, activation, and operationalization may be several relations. GOV-D22
SH-14 Grammar Directive -> Norm -> Ascription is generative governance grammar and tempo. baseline; arrow semantics open
SH-15 Viability Value, Impact, Need, Cost, Risk, Quality, and Adverse condition belong to the viability inquiry. H-CM-02, H-CM-03, GOV-D31, GOV-D35
SH-16 Merged Method: current GSM must not freeze research. Merged into the mandate and C6. mandate; C6
SH-17 Regulation Governance, Regulation, and Supervision are generic Mechanisms: Governance emits Directives; Regulation consumes Directives and emits Norms plus feedback; Supervision evaluates Ascriptions and their behavior against those Norms and may emit Measures. Ownership may sit on Structures. H-GC-10, H-DP-07
SH-18 Tracing An explicit governance chain traces the concern chain and governance/generation causality. H-GC-11
SH-19 Derivation Those generic Mechanisms may be auto-derived from information already present in GSM. Derivation of a Mechanism is not production or activation of DNA. H-GC-12, GOV-D38
SH-20 Provenance Governance–Regulation–Supervision is inspired by Beer’s Viable System Model (S1–S5). Inspiration is not an embedding of VSM subsystems. H-GC-13

6. Systemics paradigm

These accounts are how the program thinks. They are not a late checklist and not a competing ontology. Promotion gate 2 uses the same clash tests.

Account Systemic content GSM contact Clash test
Purpose as identity Organization is identified by why it exists, not by a container label. Structure.purpose; GOV-D08 Two Structures sharing one purpose collide with purpose as unique identity.
Teleology as test Purpose, function, and rule must do distinct work. Purpose -> Function -> Rule If purpose changes and the justified evaluation or Directive does not, purpose is idle.
Requisite variety Distinct causal contributions must remain distinguishable. one Norm per qualifier versus many Mechanisms A single assertion that hides distinct contributions fails the variety test.
Operational closure / autopoiesis A System produces and evaluates the definitions that constitute it. owner-local Compliance; DNA production; GOV-D20 External Compliance with no owner-local path fails claimed self-production.
Recursion without nested Structures Recursion is DNA targeting, not subsystem containment. flat Structures; GOV-D07 A required containment hierarchy contradicts claimed flatness.
Beer as inspiration, not embedding Viable-system regulation (policy, regulation, supervision) informs G/R/S. GSM does not store S1–S5 or nested viable systems. SH-20, H-GC-13; gsm.puml VSM notes Identifying G/R/S with S1–S5, or requiring nested viable systems, imports a second topology.
Viability as derived balance Quality is value against cost and risk, not a compensating score. Quality, Value, Cost, Risk; GOV-D32 A scalar that compensates a catastrophic constraint fails viability.
Definition of the state The primary regulated variable is the definition of the state, not the state alone. DNA grammar; Ascription lifecycle A model that regulates only observed state and never definitions is not this candidate.
Emergent Systemness System is not stored. Reflexive Mechanisms yield Systemness. GOV-D01 Treating System as a primitive class without reflexive production fails emergence.

A hypothesis that cannot state how it would fail one of these tests is not ready for promotion. The same accounts constrain problem formation, not only promotion.

7. Cross-cutting method

  • Labels do not prove roles; causal signatures and topology do.
  • Definition identity and Ascription snapshot identity are not interchangeable.
  • Declared topology and observed operation are different facts.
  • Governance scope remains explicit across every Structure boundary.
  • Directive, Norm, and Ascription tempos remain distinct.

8. Promotion gates

A candidate outcome becomes eligible for a GSM Change Proposal only when it passes all applicable gates:

  1. Semantic adequacy: terms, relations, scope, direction, cardinality, and alternatives are explicit.
  2. Systemics coherence: the outcome survives the systemics paradigm.
  3. Placement: the case for core GSM, GSM ontology, or a derived view is explicit and compared with the alternatives.
  4. Formalizability: the outcome can be expressed through a metamodel, schema, expression form, derivation rule, or another testable form.
  5. Empirical and operational adequacy: executed examples, counterexamples, evidence requirements, and observable consequences are identified.
  6. Conformance impact: normative obligations and non-normative analyses are distinguished, including what would constitute failure.
  7. Traceability: supporting findings, rejected alternatives, affected GSM artifacts, and dependent decision IDs are recorded.

Passing these gates supports proposal readiness. It does not itself make a research outcome normative.

9. Critical path

Only the following decisions are Active. All other register entries remain listed but are not on the current test path.

Decision Next test
GOV-D05 CASE-01
GOV-D06 CASE-02
GOV-D17 CASE-01
GOV-D31 CASE-03
GOV-D32 Dimensional example before any Quality formula
GOV-D35 CASE-03; H-CM-03 remains open
GOV-D36 CASE-02

Table of contents

Back to top

© 2026 Poesis. All rights reserved. · Legal notice · Privacy · Cookies · Cookie settings