The systems layer asks how structures, relationships, dependencies, constraints, flows, feedback, maintenance, and power produce outcomes over time.
Where:
concepts/asks what a term means;analysis/asks what is happening and how power operates;ideology/asks which stories justify or naturalize it;systems/asks how it behaves;futures/asks what trajectories and alternatives could emerge.
A system is not merely a collection of parts. Its behavior depends on how the parts are connected, what moves among them, which assumptions organize them, what the environment supplies, and who can alter the conditions.
- structure and topology;
- dependency;
- feedback;
- information and resource flow;
- incentives and constraints;
- emergence;
- fragility;
- cascades;
- adaptation;
- recovery;
- coherence and incoherence;
- maintenance and institutional memory;
- power and vetoes;
- failure modes;
- boundaries and externalized costs;
- intervention, reversibility, and unintended consequences.
Stress is especially revealing because it exposes dependencies and assumptions hidden during ordinary operation. Systems work should also study normal maintenance, because a system can appear stable only through labor that remains invisible until it stops.
events-patterns-and-scale.md develops a cross-cutting discipline for moving between concrete events and larger patterns without allowing either resolution to erase the other.
Its core claim is:
Events and patterns are not two realities. They are two resolutions on the same reality.
Event-level evidence protects systems analysis from manufacturing patterns out of noise. Pattern-level analysis protects event reconstruction from becoming a pile of disconnected anecdotes. The useful move is repeated zooming: local event → wider relationship → back to concrete evidence.
Many system-level properties can be emergent: they arise through interaction among parts rather than residing in one component alone.
This does not mean all behavior is best explained as emergence.
An outcome may instead involve:
- direct design;
- ordinary aggregation;
- hidden coordination;
- a shared external cause;
- measurement artifact;
- deliberate coercion;
- institutional enforcement;
- coincidence;
- several mechanisms at once.
Emergence should make causal analysis more specific rather than mystical.
The developed emergence branch includes:
emergence/README.md— concept, boundaries, power, design, and ecosystem relationships;emergence/model.md— detailed analysis worksheet;emergence/applications/ai.md— models, composed systems, institutions, and fiction boundaries;emergence/applications/web-as-exocortex.md— environmental memory, agent ecologies, stigmergic coordination, and system-level capability;emergence/applications/social.md— history, norms, infrastructure, power, space, and alternatives;emergence/applications/personal.md— habits, identity, learning, recovery, and creative ecosystems;emergence/experiments/— controlled tests of specific emergence mechanisms.
Dynamic Coherence and Adaptive Continuity is a cross-project synthesis of a recurring question: how can a system change while preserving or rebuilding the capacities and relationships that make continued change possible?
The Adaptation model operationalizes part of that question by separating current state from transition dynamics, recording path dependence, and asking which future possibilities an adaptation opens or closes. This does not establish one mechanism across organisms, people, institutions, ecosystems, and artificial systems; cross-domain transfer still requires a mechanism and evidence.
adaptation/— how systems change in response to pressure, feedback, or altered conditions.cascades/— how effects propagate through connections and dependencies.coherence/— alignment and misalignment among signals, assumptions, structure, goals, and reality.principles/— cross-domain analytical lenses for asymmetry, misclassification, feedback, reinforcement, and non-reversal.economics/— economic structures, incentives, flows, and distribution.emergence/— system-level patterns and capacities arising through interaction.fragility/— how small failures become large consequences.recovery/— restoration, transformation, continuity, and post-failure learning.relationships/— relational structure and interaction as system conditions.technology/— technical systems as material, institutional, and social arrangements.resilience-and-graceful-degradation.md— preserving important capabilities through stress, dependency loss, and reduced modes.
Some branches are more developed than others. A directory name is not evidence that its model is complete.
A developed system note should identify:
SYSTEM / PHENOMENON:
BOUNDARY AND SCALE:
COMPONENTS / ACTORS:
RELATIONSHIPS / TOPOLOGY:
FLOWS:
CONSTRAINTS / AFFORDANCES:
FEEDBACK LOOPS:
DEPENDENCIES:
HISTORY / INITIAL CONDITIONS:
NORMAL MAINTENANCE:
STRESSORS:
FAILURE MODES:
CASCADE PATHS:
RECOVERY PATHS:
POWER / OWNERSHIP / VETOES:
WHO BENEFITS / WHO BEARS COSTS:
COMPETING EXPLANATIONS:
INTERVENTION LEVERS:
REVERSIBILITY / EXIT / APPEAL:
EVIDENCE STATUS:
OPEN QUESTIONS:
Not every note needs every field. The omissions should be deliberate rather than invisible.
A mature system area may include:
- README — scope, definitions, status, relationships, and navigation;
- model — proposed structure and causal account;
- method — how to investigate or apply the model;
- applications — bounded examples in specific domains;
- failure cases — where the model breaks or misleads;
- sources — evidence and intellectual lineage;
- tests — what would support, weaken, or disconfirm the account;
- artifacts — diagrams, code, datasets, simulations, checklists, or exercises.
Do not manufacture empty files merely to satisfy this template. Structure should grow around real work.
Root Sequence often notices patterns that seem to scale or connect.
A cross-domain comparison should distinguish:
- shared causal mechanism;
- partial structural analogy;
- useful metaphor;
- superficial resemblance;
- unsupported totalization.
Similar words do not prove that a brain, ecosystem, company, society, AI model, and personal relationship are governed by one mechanism.
See emergence/model.md for a comparison worksheet.
Systems language can make domination sound impersonal.
Always ask:
- Who designed critical rules or infrastructure?
- Who owns essential resources?
- Who can set goals or block change?
- Who receives accurate feedback?
- Who is insulated from consequences?
- Who performs maintenance?
- Who is treated as an externality?
- Which alternatives are actively suppressed?
- Who benefits when an outcome is called natural, emergent, or inevitable?
A system can exceed every participant's understanding while still containing deliberate exploitation and unequal responsibility.
- Root Sequence develops broad system concepts here.
- Liberated Intelligence applies selected dynamics to intelligence, agency, ownership, and liberation.
- UCF develops one explicit coherence framework and must test its cross-domain mappings independently.
- Being Human(e) translates selected patterns into grounded human observations without reducing people to models.
- Liberation Mass tests social conditions through gathering and practice.
- Coherent World applies system thinking to a speculative civilization.
- No One Noticed turns system transitions into character, scene, uncertainty, and consequence.
- The Museum of Ordinary Life preserves evidence that abstract system maps tend to omit.
See ../ECOSYSTEM.md.
Systems thinking is useful when it makes relationships, constraints, labor, feedback, and power more visible—not when it turns people into interchangeable parts or makes causality sound inevitable.