Skip to content

Latest commit

 

History

History

README.md

Concepts and cross-domain foundations

Document role: Local index for shared definitions, conceptual frameworks, design principles, and methods
Status: Active / living

This directory holds current ideas that need one shared Root Sequence home before projects transform them for their own context. The pages do not all have the same role: some define terms, some frame a recurring question, some propose design guidance, and some describe a method or pattern.

Document roles and evidence boundaries should be stated on each page. Being listed here means an idea is shared and cross-project; it does not make the idea settled, universally applicable, or mandatory.


Cross-project frameworks and design ideas

  • Root Sequence Design Grammar — an AI-assisted, review-pending synthesis of recurring design questions and their existing homes; it does not make one project govern another.
  • Dynamic Coherence and Adaptive Continuity — a review-pending cross-project framework for path dependence, adaptive change, agency as effective future possibility, continuity-through-transformation, and coherence across time and scale.
  • Agency and Automation — a review-pending principle about reducing compulsory burdens while preserving chosen participation, bounded delegation, collective authority, and recovery.
  • Legible Systems — a working design principle about progressive understanding, technical accessibility, repair, alternatives, and power.
  • Epistemic Discoverability and Knowledge Routing — a working concept for helping people move from the language/questions they currently have toward fields, terminology, sources, methods, and communities they do not yet know how to name.
  • Legible AI-Assisted Expression — a working principle for reducing the cost of expression while keeping human contributions, AI additions, transformations, evidence, uncertainty, and decisions visible.
  • Intelligence Ecology — a developing framework for asking what behaviors an environment selects for in intelligent systems.
  • Human(e) Design — a translation method between human observation and concrete design choices.
  • Human(e) Infrastructure — a cross-project systems concept about durable conditions that support humane life.
  • User-Configurable Cognitive Interfaces — a design concept for interfaces that people can shape around how they think and work.

These pages are related, but they are not interchangeable. A principle recommends a direction, a framework organizes inquiry, a concept supplies shared language, and a method helps turn understanding into action.

Project identity and shared working vocabulary

  • Why “Root Sequence”? — the maintained explanation of the project name: underlying conditions, unfolding processes, and the recursive relationship between them.
  • Working Vocabulary — scoped Root Sequence usages of curiosity, intelligence, empathy, love, connection, and liberation, with their limits and relationships shown together.

The earlier what-is-* series mixed short definitions, poetry, political analysis, personal reflection, and fictional mythology under one filename pattern. The six genuinely shared vocabulary terms are consolidated above. The outliers now live with material of the same role: the interpretive Capitalism Replaces Reality essay, Personal Anarchism, and the historical Auryn sketch within Liberated Intelligence.


Relationship to systems and founding texts

  • ../systems/ owns analytical principles, explicit models, methods, applications, tests, and failure cases for system behavior.
  • ../systems/principles/ collects the current Systems Principles: asymmetry, misclassification, feedback, reinforcement, and non-reversal.
  • ../founding-texts/ preserves founding texts, manifestos, early cycles, metaphors, and historical orientations. It is not the home for new working principles.
  • ../analysis/ applies concepts and systems lenses to present structures and power.
  • ../futures/ develops scenarios, alternatives, and resilience work.

Maintenance rule

Keep one substantive canonical page for each shared idea. Project-specific pages should link to it, state how their context changes it, and develop only the material their project owns.

When a page becomes primarily a tested systems model, a diagnosis, a future proposal, or a practical artifact, move its canonical treatment to the corresponding area and leave a clear route from here.