New, returning, or overloaded? Read START-HERE.md for the smallest useful map.
UCF is an exploratory framework for asking how systems hold together, interact, fragment, adapt, and recover. It compares patterns across domains while testing whether those comparisons are useful or misleading.
Ecosystem role: optional analytical framework within Root Sequence.
Owns: UCF definitions, models, terminology, tests, critiques, and applications.
Does not own: general systems theory, ethics, community governance, intelligence ethics, fictional canon, or the conclusions of other projects.
Current work: proposed v1.1 model reconciliation, AI-assisted and awaiting author review. This is not a validated universal theory or a reviewed release.
- Proposed model v1.1: definitions, four layers, optional state labels, and failure criteria.
- Booking-service example: a worked synthetic example with runnable code and limitations.
- Claims register, evidence rules and checked sources, and glossary.
- Reconciliation record: what changed, what remains unresolved, and how this connects to the living paper.
- Documentation index, Idea Trails, and contribution guide.
The earlier overview is preserved in full. The v1 model remains unchanged as an earlier formulation. Revision is visible rather than retroactively attributed to those documents.
Can a small vocabulary of assumptions, dependencies, information flow, boundaries, feedback, and adaptation help examine otherwise different systems?
Structural similarity is a reason to investigate, not proof of a shared causal mechanism. A domain may need its own definitions, resist comparison, or show that UCF adds nothing. The word “Universal” names an ambition under examination, not a demonstrated result.
The existing model distinguishes internal, inter-agent, systemic, and temporal analysis. The proposed revision keeps these layers and asks for a separate account at each relevant scale: what works, under which assumptions, with which effects on dependencies and affected parties, and for how long?
The separate labels Chaos, Tension, Flow, and Unity remain optional hypotheses about patterns, not obligatory developmental stages. Several labels may apply at once, or none may help. Tension can convey useful disagreement. Flow need not mean maximum efficiency. Unity means coordination with differentiation in the working vocabulary, not a final state, common consciousness, or a requirement to eliminate boundaries.
The worked example currently finds the layers more specific than the state labels. That is an editorial finding about one constructed case, not evidence that one taxonomy works across domains.
Agreement, predictability, integration, or centralized information does not by itself establish legitimate authority. A functioning arrangement may still impose unacceptable purposes or burdens. Record functional fit, effects across the assessed boundary, and normative objections separately.
Do not treat disagreement, autonomy, selective disclosure, redundancy, refusal, or protective separation as defects merely because they reduce synchronization. Nor should every disruption be called deterioration: sometimes an existing pattern needs to end. No architecture receives an automatic endorsement for being centralized or decentralized.
Optimization can remain a bounded tool. UCF does not authorize a single score for people, institutions, consciousness, or moral worth.
Use systems thinking, domain research, comparative analysis, formalization where possible, counterexamples, and visible revision. Mark established domain results, proposed definitions, hypotheses, interpretations, and fictional examples separately. Evidence for a source theory is not evidence for a UCF extrapolation.
For each application, specify boundaries, observations, alternatives, privacy needs, and what would count against the proposed explanation. Compare against a competent existing method before claiming added value. Negative results belong in the record.
Community Infrastructure may provide bounded design cases involving coordination, stewardship, federation, and maintenance. Liberated Intelligence raises questions about multi-agent behavior without delegating agency or moral status to UCF. Being Human(e) can expose where a model overlooks lived consequences. Liberation Mass is a gathering practice, not a population required to converge toward a state label.
Coherent World can use UCF as one design lens; No One Noticed can generate questions through fiction. Neither supplies empirical validation. The broader Root Sequence living paper draws on UCF alongside other research rather than becoming a UCF whitepaper. See the cross-project reconciliation.
models/: model versions, cross-intelligence notes, and constructed tests.docs/foundations/: literature and conceptual material requiring claim-level evidence review, not a certified empirical layer.docs/domains/: applications to biology, cognition, AI, society, experience, ethics, language, art, technology, ecology, physics, collapse, and consciousness research.docs/speculation/: explicitly unproven extensions, including hybrid and mesh intelligence.docs/interpretation/: meaning, agency, time, and philosophical interpretations.docs/archive/: preserved earlier wording with its historical status.publications/: existing publication material; a filename or version does not certify review.related-frameworks/: adjacent-framework material; source and comparison quality still need review.
There is no site/ or assets/ directory at the audited base revision. This change creates neither and does not deploy a website.
The priority is to compare definitions and methods on bounded cases, examine how cross-scale effects conflict, test whether the state vocabulary adds clarity, and finish the foundations/publications evidence audit. The existing issue #1 remains the tracker. The changelog distinguishes proposed, tested, and unresolved work.
Research, code, counterexamples, alternative definitions, diagrams, translations, critique, and accessible explanations are welcome. UCF may be narrowed or rejected where it stops helping. See CONTRIBUTING.md.
CC0, as recorded in LICENSE. The citation metadata identifies the project; cite an exact Git revision and do not infer scientific validation or paper-author approval from it.