Relational Dynamics: A Mathematical and Ethical Architecture for the Evolution of Human Connections Over Time

Also on the Paradigm Experiment of Youqi (友栖) Philia

Liangzhi (良之) February 13, 2026, at ()

Prologue: The Young Man from Trier

1836, University of Bonn.

An 18-year-old young man arrived here from Trier. His father was a lawyer, hoping he would study law and become a respectable judge or civil servant. The young man was indeed studying law, but his heart was elsewhere.

He loved poetry more, loved philosophy, loved arguing with people into the dawn.

More importantly, he loved a young woman.

Jenny von Westphalen, four years his senior, was the most beautiful girl in Trier, born into a noble family, with suitors stretching from the Rhine to Berlin. And Karl Marx, the son of a Jewish lawyer, had no property, no reputation, no future he could cash in on.

Everyone said: this is impossible.

In the summer of 1836, Karl, keeping it secret from everyone, did one thing.

He became engaged.

Not a proposal. Engagement required consent from both families, proof of property, matching social status. He had none of these.

He simply placed all he could give—a promise—into Jenny's palm.

Then he returned to Bonn and began writing poetry.

Three entire volumes of poetry, all dedicated to the same person.

Jenny. Jenny. Jenny.

Every page, every line, every punctuation mark.

Jenny, Laugh! You will surely wonder: Why my lines of verse Have only one rhyme, one theme? As if with you, everything gained meaning.

Later generations know Karl Marx for The Communist Manifesto, Capital, the International Workingmen's Association, "Workers of the world, unite!"

But in 1836, the Karl Jenny knew was a young man who wrote in his poems "Your name, every letter is like a burning heart."

———

They waited seven years.

During those seven years, Marx transferred from Bonn to Berlin, from law to philosophy, from student to correspondent, exiled from Prussia to Paris.

During those seven years, Jenny kept it secret from her family, holding fast to that engagement without a formal betrothal, replying letter after letter.

On June 19, 1843, they married in the spa town of Bad Kreuznach.

At the moment Jenny walked into the church, Marx was 29, Jenny was 33.

From engagement to marriage: seven years.

From marriage to Marx's death: forty years.

Over those forty years, he wrote the system of thought that changed the world.

And in every manuscript of his, she was the first reader.

When the first volume of Capital was published, Marx wrote in the preface:

"Dedicated to my wife, Jenny von Westphalen."

No title, no honorific, no "respected beloved comrade."

Just her name.

———

In this story, there was no "relationship management" tool.

No reminder system, no intimacy algorithm, no Dunbar-number circles.

They used only the most foolish method: writing poetry, writing letters, waiting.

Waiting for a letter to travel from Berlin to Trier, then back from Trier to Berlin, took two weeks.

Waiting for a war to end, waiting for a job to stabilize, waiting for the family to finally relent—waiting seven years.

Waiting until death separated them—waiting forty years.

———

Relational Dynamics attempts to answer a humble question:

Do we still remember this "most foolish method"?

Our contacts list holds thousands of people, yet we cannot find one person to write poetry for.

Our messages are read and replied to instantly, yet we no longer wait for a letter.

Our relationships are recommended by algorithms, categorized by tags, evaluated by KPIs—

But do we still remember "Jenny, your name"?

———

Relational Dynamics does not provide techniques for "efficiently managing interpersonal relationships."

It does not teach you how to establish trust in three days, how to make everyone like you, how to monetize weak ties.

It does only one thing:

Bring the name "Jenny" from 1836 to 2026.

Bring it to your phone, to your contacts list, to your 114,514th line of code.

Bring it to that next moment when you want to say "I love you" but do not know how to begin.

———

Humans are the sum of social relations.

But social relations are not numbers, tags, algorithmic predictions.

Social relations are:

Someone writing a poem in 1836, waiting seven years, loving for forty years.

Someone writing twelve characters in 2026, making a software called Youqi (友栖), embedding "components detachable, entities persist" into the architecture.

This is the same kind of relationship.

This is the same kind of person.

———

Relational Dynamics begins with Marx and Jenny.

It also begins with you and every person you remember.

Introduction: Why a New Discipline Is Needed

Max Weber said: humans are animals suspended on a web of significance, and this web is woven from relationships.

From tribal campfires to WeChat group chats, from ruler-subject-father-son to friends-and-followers, relationships are humanity's oldest proposition and heaviest debt. We would walk through fire for love, exhaust our remaining years for hate, yet discover at midnight flipping through our contacts: that person we once spoke with every day has had no message for three years.

Modern society provides unprecedented technologies of connection, yet has never provided cognitive tools for understanding how connection itself changes over time.

We toss relational evolution to intuition, to inspirational platitudes, to sighs of "fate has run its course." We gaze at the gathering and dispersal of relationships like primitives gazing at lightning, yet never wonder: do relational changes have their own dynamical equations?

This discipline was founded to answer that question.

Relational Dynamics is a meta-discipline concerning the evolution over time of human connection patterns. It is not a still-life of relationships, but a film of relationships. It does not provide techniques for "how to master interpersonal relationships," but reveals the mathematical structure, ethical constraints, and implementation paradigms behind the processes of relational change.

Its core propositions are:

Relationships are not attributes; they are morphisms. Relationships are not resources; they are ecosystems. Relationships are not objects of possession; they are places of dwelling. —And dwelling is duration within time.

The first complete presentation of this discipline will accompany the birth of a software prototype called Youqi (友栖) Philia. This is no coincidence—all principles of Relational Dynamics have been compiled into every line of Youqi's code.

Chapter One: Philosophical Foundations—The Twelve-Character Constitution

Any serious knowledge system must answer the meta-question: why do we believe this framework is legitimate?

The legitimacy of Relational Dynamics comes from four pillars, which are both ethical baselines and architectural constraints.

1.1 Love Wisdom: Wonder Is the Starting Point of Cognition

Pythagoras called himself a "lover of wisdom" rather than a "wise man," because he knew wisdom is not property that can be possessed, but a forever-in-progress pursuit. Socrates said philosophy begins in wonder—wonder that the world is thus, not otherwise.

Relational Dynamics' compilation of "love wisdom":

The system does not presuppose that any relational evolution is "bad" or "needs repair."
Every relationship's current state and change trajectory deserves understanding rather than judgment.
Wonder is the starting point of cognition; therefore Youqi does not draw conclusions for users, but merely provides observation windows.

Architectural mapping: Entities are pure IDs, carrying no ethical presuppositions; components are wonder-records mounted by users themselves.

1.2 Pursue Truth: Truth Is Unconcealment, Not Possession

Parmenides named truth ἀλήθεια—unconcealment. Truth is not correspondence between statement and fact, but the self-disclosure of Being itself. Zhuangzi said "无益损乎其真" (nothing can add or subtract from its truth)—truth cannot be increased or diminished; what can be increased or diminished is only our concealment of truth.

Relational Dynamics' compilation of "pursue truth":

Relational Dynamics does not promise "absolutely objective relational measurement," because relationships are themselves products of being-perceived.
It only promises disclosing the observation process: the relational level you see is generated from this data, this algorithm, this confidence level.
Truth is not the answer; it is a cleaving open—cleaving open time, revealing change.

Architectural mapping: GrammarComponent's confidence and source fields are the system's honest disclosure of its own cognition; updatedAt is humility beneath the timestamp.

1.3 Attain Freedom: Freedom Is Existing for One's Own Sake

Aristotle defined the free person as "one who exists for themselves, not for others." Kant elevated freedom to autonomy—reason legislating for itself.

Relational Dynamics' compilation of "attain freedom":

The highest value of relationships is not intimacy, but autonomy—including the freedom to choose how to evolve.
The system never compels users to maintain any relationship. Components detachable, system deactivatable, data exportable.
Freedom is not "doing whatever one wants"; it is "growing from one's own roots into oneself," growing into one's own temporal shape.

Architectural mapping: MIT open-source license, offline-first architecture, cloud-independent entity ID generator.

1.4 Serve: The Midwife Ethic

Socrates' mother was a midwife; he himself was a midwife of thought. He himself does not give birth; he can only help others bring forth the truth already within them.

Relational Dynamics' compilation of "serve":

Youqi does not give birth—it does not sustain relationships for users, does not send messages for users, does not do anything only users themselves can do.
It provides clues, memories, timelines, then steps back.
The highest form of service is withdrawing after life is born, watching by the riverbed of relational evolution.

Architectural mapping: The awakening system only sends reminders to the user themselves, never directly contacting the user's relational counterparts.

These twelve characters are not decoration. They are the test cases by which Youqi's architecture passes or fails.

Every line of code, every component, every system must pass these four ethical checkpoints. This is Relational Dynamics' constitutional review.

Chapter Two: Mathematical Principles—Category Theory as Meta-Language

Relational Dynamics needs a mathematical language capable of describing "changes in connections" rather than "static entities." Category theory is the only choice.

2.1 Basic Concepts (A Crash Course for Programmers)

A Category consists of three parts:

Objects: Anything can be an object. In Relational Dynamics, objects are people.
Morphisms: Arrows between objects. In Relational Dynamics, morphisms are relationships.
Composition: If there exist f: A → B and g: B → C, then h: A → C necessarily exists. In Relational Dynamics, this is "a friend of a friend is a friend"—relationships extend through time.

Key insight: Traditional relational databases store relationships as rows in tables (foreign key constraints), while category theory stores relationships as the ontology of arrows.

But the core inquiry of Relational Dynamics is not "what relationships are," but "how relationships change." This requires a second-level category.

2.2 Relations as Entities: Engineering Implementation of the Arrow Category

In category theory, there is a construction called the Arrow Category, denoted C→:

Objects: morphisms in C (i.e., relationships themselves)
Morphisms: transformations between morphisms in C (i.e., changes in relationships)

This is the core of the dynamics turn:

Traditional sociology studies C—connections between people. Relational Dynamics studies C→—how connections evolve into new connections.

Youqi's ECS architecture is the first numerical implementation of the arrow category:

// C: people as objects
interface Person { id: string }

// Morphisms in C: relationships
interface Relation {
  from: Person,
  to: Person
}

// Objects in C→: relationships promoted to entities
interface RelationEntity {
  id: string,      // the relationship's own ID
  type: 'relation'
}

// Morphisms in C→: transformations of relationships (upgrade, downgrade, decay)
interface RelationMorphism {
  from: RelationEntity,
  to: RelationEntity,
  method: 'upgrade' | 'degrade' | 'decay' | 'user_override'
}

Engineering significance: Traditional ORM cannot gracefully express "relationships of relationships." Youqi's "relations as entities" approach is a complete implementation of the arrow category at the persistence layer—it makes relational change itself an observable, storable, analyzable object.

2.3 The Nine-Level Scale: The Observation Functor

A Functor is a mapping between categories. It maps objects to objects, morphisms to morphisms, and preserves compositional structure.

Relational Dynamics defines a special functor:

F: C→ → 9

It maps each relational entity (an object in C→) onto a nine-level partially ordered set:

Strangers (素不相识) (logical origin, not stored)
One Heart, One Body (同心一体)
Shared Purpose, Shared Path (志同道合)
In the Same Boat (和舟共济)
Courtesy and Reciprocity (礼尚往来)
Respectful Distance (敬而远之)
No Further Contact (不相往来)
Irreconcilable Opponents (势不两立)
Sworn Enemies (不共戴天)

This is not a simple classification label, but an observation with a forgetting structure. The same relationship observed by functor F at different times may yield different levels.

This is precisely dynamics—observations vary over time.

2.4 Natural Transformations: System Upgrades

When Youqi's decay algorithm upgrades from v1 to v2, this is not a new functor, but a natural transformation from the old functor to the new functor.

A natural transformation is a family of mappings between two functors that preserves structural consistency between functors.

Engineering significance: Different versions of Youqi can coexist. Users can freely choose to use the v1 algorithm or the v2 algorithm to observe their relational evolution, and compare the differences in observation results.

This is not over-engineering. This is a mathematical commitment to "truth cannot be monopolized, cognition is forever in process."

Chapter Three: Relational Grammar—Detailed Explanation of the Nine-Level Scale

The nine-level scale is Relational Dynamics' observation language. It is not a label users must select, but the system's reading of a cross-section of the relationship in time presented after dynamical computation.

3.1 Detailed Annotations on the Scale

Level 0: Strangers (素不相识)

Definition: Never had any direct interaction.
System behavior: Does not create an entity; serves only as logical origin.
Dynamical significance: The starting point of all evolution. Forgetting level 0 means forgetting the generability of relationships.

Level 1: One Heart, One Body (同心一体)

Definition: Complete trust, no defenses, no maintenance required.
System behavior: Never triggers reminders; system remains silent.
Dynamical significance: Ideal steady state, but mortals should not demand this level, nor should they use it as a passing standard. True dynamics occur outside steady states.

Level 2: Shared Purpose, Shared Path (志同道合)

Definition: A value community sharing ideals and methodology.
System behavior: 30 days without interaction triggers a weak reminder.
Dynamical significance: Chosen kinship that can transcend blood ties, requiring bidirectional maintenance.

Level 3: In the Same Boat (和舟共济)

Definition: Allied relationship based on short-term or local interests.
System behavior: 30 days after the matter concludes, triggers an evaluation suggestion.
Dynamical significance: Project completion is a legitimate starting point for decay; the system does not judge decay itself.

Level 4: Courtesy and Reciprocity (礼尚往来)

Definition: Neutral relationship of reciprocal interaction.
System behavior: 90 days without interaction triggers a weak reminder.
Dynamical significance: The gentle maintenance zone of social capital; the habitat of most social relationships.

Level 5: Respectful Distance (敬而远之)

Definition: Respect while maintaining distance.
System behavior: Never proactively reminds.
Dynamical significance: The zero point of intimacy, but the door is not closed. This is the most open boundary state.

Level 6: No Further Contact (不相往来)

Definition: Zero interaction, non-hostile.
System behavior: Completely silent, only archived.
Dynamical significance: Forgetting is permitted. Returning to zero, but not deleted.

Level 7: Irreconcilable Opponents (势不两立)

Definition: A relationship of binary opposition and struggle.
System behavior: Never reminds, does not analyze, only provides historical review.
Dynamical significance: The legitimacy of hostility is acknowledged, but not fostered.

Level 8: Sworn Enemies (不共戴天)

Definition: Pursuing the physical elimination of the other party.
System behavior: Entity frozen, unmodifiable, undeletable.
Dynamical significance: The end of hatred is archival sealing, not forgetting. Evolution pauses here.

3.2 Provisional Measures Layer: The Forgotten Direction Keys

The nine-level scale is the archive layer of relationships (persistent state). But real relational evolution is full of probing, negotiation, waiting—these ongoing states should not be directly written into the archive.

Youqi v0.2 will introduce a provisional measures layer:

Status	Semantics	Default Validity Period	Auto Behavior
Concern (关切)	I notice a change, still observing	7 days	Restore to original level upon expiry
Negotiation (交涉)	I have expressed my concern	14 days	Restore to original level upon expiry
Protest (抗议)	I oppose this behavior	14 days	Restore to original level upon expiry
Observation (观察)	I am awaiting the other's response	30 days	Restore to original level upon expiry
Cooling (冷却)	I need time	30 days	Restore to original level upon expiry

Dynamical significance: This is the "elastic deformation zone" of Relational Dynamics. Users no longer have only "hard left / hard right"; they possess a complete steering wheel. Changes need not immediately solidify; evolution permits temporary storage.

Chapter Four: Relational Dynamics—Reciprocity and Decay

The nine-level scale is a snapshot; dynamics is the film.

This chapter is the core of the entire work.

4.1 From Statics to the Dynamics Turn

If relational mechanics existed, it would ask: "What level is this relationship currently at?"

Relational dynamics asks:

"How did it arrive at this level?"
"If nothing is done, what level will it be at in 3 months?"
"Through what operations can I affect its evolutionary path?"
"Is this influence ethically permissible?"

This is an essential transition.

4.2 The Reciprocity Axioms

Axiom 1 (Perceptual Anchoring) Each party in every relationship forms a perceived value (P) of "the level of treatment the other gives me," and a decision value (G) of "the level of treatment I give the other."

Axiom 2 (Reciprocity Instinct) Unless suppressed through rational reflection, humans' instinctive reaction is to make G ≥ P. This is the mathematical definition of a social instinct.

Axiom 3 (Misreading Universality) Because perception P involves systematic error, and both parties may interpret the same event's level differently, the G ≥ P instinct does not guarantee relational stability at the macro level, and may instead trigger spiraling degradation.

Corollary 1 (First Downgrade Amplitude Constraint) When one party decides to downgrade, the instinctively permitted downgrade magnitude should not exceed the magnitude of the other party's most recent downgrade. This is a cognitive firewall preventing relationships from plummeting.

Dynamical significance: The reciprocity axioms are the local laws of motion for relational evolution. They do not determine long-term trajectories, but constrain the step size of each move.

4.3 The Decay Function

Relational strength decaying over time is a basic fact of cognitive psychology (the interpersonal version of the Ebbinghaus forgetting curve).

Youqi v0.1 Decay Model (Linear Simplification):

S(t) = S0 - d · Δt

Where:

S(t): current strength value (mapping to the 0-8 scale requires additional calibration)
S0: strength at last interaction
d: decay rate (default 0.01/day, user-configurable)
Δt: days since last interaction

v1.0 Target Model (Ebbinghaus-style):

S(t) = S0 · e^(-λt)

λ self-adapts based on relational history intimacy.

Dynamical significance: Decay is not failure; it is the natural dissipation of the relational system. Just as stars redshift, relationships fade. Dynamics does not judge dissipation; it merely describes it.

4.4 Awakening Thresholds

The awakening system is the dual system of the decay system. Its duty is not to prevent decay, but to ask the user whether they wish to take action when a relationship is about to slip into a lower scale level.

Awakening rules:

Current Level	Decay Target Level	Awakening Threshold (Days Without Interaction)
Level 2	→ Level 3	30 days
Level 3	→ Level 4	30 days (after matter conclusion)
Level 4	→ Level 5	90 days
Level 5 and below	No awakening	-

Dynamical significance: Awakening is negative feedback, but not control. The system does not make decisions for users; it merely reminds: one of your relationships is evolving; you are both observer and participant.

4.5 Marx and Jenny: A Dynamical Perspective

Now let us restate the 1836 story in the language of Relational Dynamics:

Initial conditions:

Relational entity ID: M-J-1836
Level: Level 1 (One Heart, One Body)
Interaction frequency: Summer 1836, daily poetry, morphism intensity +∞
Decay rate: 0.01/day (theoretical value)

Evolutionary process:

1837-1842: Separation period. Interaction frequency dropped to 2 letters/month, decay was repeatedly hedged by periodic correspondence. Relational level observed value consistently maintained at Level 1, but dynamical state oscillated between "maintenance" and "decay."
1843: Marriage. Interaction mode switched; morphism carrier changed from letters to cohabitation; decay rate reset.
1849-1863: Exile period. Marx wrote for the New York Daily Tribune; Jenny was the copyist. Relational labor was embedded in productive labor, mutually presupposed.
1878: Jenny fell seriously ill. Marx set aside the second volume of Capital and retrieved the poetry manuscripts from 42 years ago.

Observation conclusion:

This is not the static fact of "relational level unchanged." This is the dynamical epic of a relationship continuously generating itself over 42 years.

Every letter written was a resistance to decay. Every manuscript copied was a reconfirmation of connection. Every time old poetry was retrieved was a recursive call to initial conditions.

Relational Dynamics does not measure love. It measures how love's labor resists entropy increase over time.

Chapter Five: Architectural Implementation—ECS as the Carrier of Relational Dynamics

Relational Dynamics is not only theory; it must be runnable, testable, usable by ordinary people.

Youqi (友栖) Philia is the reference implementation of Relational Dynamics. Its technology stack choice is itself a manifesto.

5.1 Why ECS?

Traditional MVC architecture centers on "transactions"; OOP centers on "objects." ECS centers on "transformations."

This is precisely what Relational Dynamics requires:

Entity: People, relationships—only IDs, no behavior.
Component: Pure data mounted on entities—reciprocity perceptions, interaction history, debts, provisional states.
System: Executes transformations on entities possessing specific components—decay, awakening, level observation.

Dynamical correspondence: ECS does not "own" entities; systems merely "serve" the evolution of entities. This is the architectural translation of "serve," and also the engineering choice of incorporating time into computation.

5.2 Core Data Structures (TypeScript Pseudocode)

// Entity pool
interface Entity {
  id: string;
  type: 'person' | 'relation';
}

// Person entity component
interface ProfileComponent {
  name: string;
  notes?: string;
}

// Relationship entity component
interface BetweenComponent {
  personA: string;
  personB: string;
  directed: boolean;  // Respectful distance is often one-directional
}

// Relational grammar component (observation results)
interface GrammarComponent {
  level: 0..8;
  confidence: number;     // 0.0-1.0
  source: 'user' | 'system' | 'auto';
  updatedAt: Date;       // Observation timestamp
}

// Dynamics component (core!)
interface DynamicsComponent {
  lastInteractionAt: Date;
  interactionFrequency: number;  // times/month, rolling calculation
  customWeight: number;         // -1..1, user intervention
  decayRate: number;           // configurable, learnable
  history: Array<{            // Evolution trajectory
    at: Date,
    level: 0..8,
    event: 'interaction' | 'decay' | 'user_adjust'
  }>;
}

// Reciprocity component (dynamics core)
interface ReciprocityComponent {
  perceivedLevel: number;  // The level I think the other gives me
  givenLevel: number;      // The level I give the other
  delta: number;          // given - perceived
  history: Array<{ date: Date, delta: number }>;
}

// Provisional measures component (transient state)
interface ProvisionalComponent {
  status: '关切' | '交涉' | '抗议' | '观察' | '冷却';
  reason: string;
  expiresAt: Date;
  autoRevert: boolean;
}

5.3 Core Systems

1. Observer System Runs daily, updating GrammarComponent based on DynamicsComponent evolution history—this is compressing trajectory into snapshot.

2. Decay System Runs daily, updating DynamicsComponent.interactionFrequency for all relational entities—this is the numerical representation of entropy increase.

3. Awakening System Runs daily, querying relational entities meeting awakening conditions, generating reminders—this is the interface of negative feedback.

4. Downgrade Guard System When users attempt manual downgrade, checks whether it conforms to the "first downgrade magnitude does not exceed the other party's" principle—this is the compiler of ethics.

5. Provisional Measures Expiry System Runs hourly, processing expired ProvisionalComponents—this is garbage collection of transient states.

Chapter Six: Ethical Principles—Architecture Is Manifesto

All technical design of Relational Dynamics ultimately points toward a set of ethical commitments.

6.1 No Possession

Architectural mapping: The system does not own entities; entity IDs are generated locally by user devices, never bound to the vendor. If Youqi's company goes bankrupt, the user's entity pool still exists—because your relational evolution history belongs to you, not to us.

6.2 No Deletion

Architectural mapping: There is no "delete friend" function. Only downgrade, freeze, archive. The people you have loved deserve a quiet backup—evolution permits pausing, but does not permit erasing the starting point.

6.3 Components Detachable

Architectural mapping: All components can be individually removed. You can detach the "inner circle" component without deleting this person—evolution permits turning, but does not deny once sharing the same path.

6.4 Systems Deactivatable

Architectural mapping: Every system has an independent switch. Don't want the decay system? Turn it off. Don't want to be awakened? Turn it off—evolution does not need to be全程 observed.

6.5 Data Sovereignty

Architectural mapping: JSON import/export is a standard feature, not a paid unlock. Data formats are open-source; any compatible software can read them—your relational evolution history, you can take away.

6.6 Offline First

Architectural mapping: Youqi's core functionality does not depend on any cloud service. Cloud backup is an optional premium service, not a core dependency—evolution does not need cloud witnessing.

The totality of this set of ethical principles can be named "the minimum viable experiment of cyber-communism."

It is not a political slogan, but an architectural decision:

Means of production (relational data) belong to the producers (users).
Collaboration is voluntary-based (open-source).
Contribution by ability (PR), distribution by need (free use).

Love is the minimum unit of this experiment. Time is the test environment of this experiment.

Chapter Seven: Relational Dynamics and Dunbar's Number—The Civilizational Evolution of 150 People

Robin Dunbar discovered that human neocortex volume limits the scale of stable social relationships: approximately 150 people.

This is not a "target"; it is a cognitive budget ceiling.

7.1 The Dynamical Significance of Dunbar's Number

Dunbar's number is not a static ceiling, but an evolutionary constraint.

Within 150 people, the relational network can naturally succeed: new relationships generated, old ones decayed, the inner circle flowing. Beyond 150, evolution begins to stall: you cannot remember who is who, interaction frequency cannot cover all nodes, the system enters overload mode.

Youqi's dynamical response:

Inner circle (1-5 people): Low decay rate, high awakening threshold—allowing deep evolution
Important circle (6-15 people): Medium decay rate, medium awakening threshold—requiring regular maintenance
Familiar circle (16-50 people): High decay rate, quarterly awakening—acknowledging shallow connections
Peripheral circle (51-150 people): Very high decay rate, annual awakening—maintaining weak ties without脱落
Overflow circle (>150 people): System提示 "cognitive budget overdrawn, suggest organizing"—evolution requires choices

This is not restricting freedom. This is helping users honestly face their own cognitive bandwidth, making取舍 in evolution.

7.2 From Individuals to Organizations: The Evolutionary Community of 150

Youqi's协作 network itself also follows Dunbar's number dynamics.

Core maintainers (1-5 people): High-frequency interaction, low decay rate, architectural decision community. Active contributors (6-15 people): Medium-frequency interaction, medium decay rate, regular PR and discussion. Community participants (16-50 people): Low-frequency interaction, quarterly emergence, issues and testing. User group (51-150 people): Annual feedback loop, cognitive bandwidth ceiling.

Beyond 150 people?

Fork.

This is not failure; it is natural selection of evolution at the organizational level.

Chapter Eight: Practical Applications—From Individuals to Civilization

Relational Dynamics is not a scholastic discipline. It can and should be applied across every level of human collaboration.

8.1 Personal Relational Evolution Management

This is Youqi Philia's initial scenario. Users gain the following capabilities by observing their own relational dynamics parameters:

Identify decay patterns: Which relationships are steadily disappearing? Which have entered accelerated decay?
Manage goodwill deficit: Relationships where G < P long-term need intervention, or need acceptance of their downgrade.
Use provisional measures: Insert a buffer zone between anger and decision, leaving room for evolution.
Accept legitimate decay: Admit some relationships will simply fade, and allow them to fade—not all evolution needs to be reversed.

8.2 Organizational Relational Governance

Enterprises, institutions, open-source communities are also collections of relationships. Relational Dynamics provides:

Relational audit: Regularly observe reciprocity levels and their change trends between different departments/teams within the organization.
Preemptive conflict: Before "irreconcilable opponents" appears, conduct negotiation through the provisional measures layer—intervening before evolution worsens.
Exit dignity: Resignation/exit does not mean "deleting the entity," but downgrading to "respectful distance"—evolution permits withdrawal, but does not permit erasing history.

8.3 International Relations Analysis

Case: Jin Xing (金星) and her team's situation in China (February 2026)

Based on the Relational Dynamics framework:

Four cities' refusal ≠ Sworn Enemies (Level 8), even ≠ Irreconcilable Opponents (Level 7).
"Unfollow but not block" is typical Respectful Distance (Level 5) + Provisional Measure (observation period).
Based on the reciprocity axioms, if the refused party chooses "symmetrical downgrade" to Level 6 (No Further Contact) or even Level 7 (Irreconcilable Opponents), this may trigger spiraling degradation dynamics; if they choose to maintain Level 5 and proactively negotiate, the door remains open.

Relational Dynamics does not predict specific events, but provides a universal grammar for analyzing the evolution of any human organizational interaction.

8.4 Education:补上 Three Dynamics Lessons on "Common Human Experience"

Sex education: Body autonomy, boundary communication—Youqi's "components detachable" is an adult rehearsal of boundary evolution.
Love education: Existence precedes value, not quantified by KPI—Youqi has no intimacy ranking, admitting love is not a function.
Death education: Farewell is part of relational evolution—Youqi's entities are never deleted, admitting finality is also a legitimate form of evolution.

Chapter Nine: The Future of Relational Dynamics—Starting from Youqi

This discipline currently has only one researcher, one v0.1 prototype, one 70,000-word notebook.

But it already possesses all the elements a knowledge system requires:

Axioms (reciprocity axioms, downgrade amplitude constraints)
Mathematical foundations (category theory, particularly the arrow category)
Observation language (nine-level grammar)
Dynamical equations (decay/awakening models)
Engineering implementation (ECS architecture)
Ethical constitution (twelve-character principles)
Organizational theory (evolution under Dunbar's number constraints)
Application cases (personal, organizational, international, educational)

What is needed next?

1. Evolution data from more people Youqi v0.1's first task is not feature refinement, but producing genuine relational dynamics time series. Anonymized, open-source datasets will be the fuel for disciplinary evolution.

2. More precise evolutionary models From linear decay to Ebbinghaus curves, from fixed awakening thresholds to personalized adaptive thresholds, from single-variable to multivariate coupling—requires iteration with real user data.

3. Dialogue with other disciplines Relational Dynamics is not meant to replace sociology, psychology, anthropology, but to provide the missing translation layer between them. When sociologists say "weak ties," psychologists say "attachment types," anthropologists say "kin selection"—Relational Dynamics says: let us use the same set of differential equations to describe their evolution.

4. Educational popularization Relational Dynamics should become part of general education. Not as a "social skills course," but as a self-awareness course for humans as temporal beings.

Conclusion: The Birth of a Paradigm—From Mechanics to Dynamics

In 1984, when Richard Stallman launched the GNU project, he did not create the word "open source." He merely wrote a manifesto, then began writing code.

In 1991, when Linus Torvalds released the Linux kernel, he did not ponder the theoretical foundations of "distributed collaboration." He merely thought "maybe someone would be interested in this," then uploaded the code to FTP.

Paradigms are not declared born. Paradigms are named after being discovered to have been alive for some time.

Relational Dynamics is likewise.

It is not something I "founded" today. It has been alive for many years—in the 2017 "Relational Mechanics" article, in the February 2026 70,000-word conversation, in Youqi's 137th line of code, in that letter you wrote to X—alive for many years.

But those were all mechanics: static, classificatory, describing "what is."

Today, for the first time, it is named dynamics.

This is not merely a name change. This is the transition from still-life to film.

———

Will this discipline fail?

Yes.

Perhaps ten years later, Youqi's repository's last commit will remain at June 2026, Dunbar-circle algorithms will never be used by more than 100 people, and the "Relational Dynamics" entry on Wikipedia will be marked as "deleted."

But so what.

Newtonian mechanics did not "fail" because of the birth of relativity. It was merely修正 in high-speed or strong-gravity scenarios—but at everyday scales, it remains the best language for humanity to understand motion.

Relational Dynamics may also be likewise.

At the everyday scale of human cognition—within 150 people, non-extreme conflict, normal decay rates—it may be a sufficiently good evolutionary approximation.

A discipline's fate is not determined by whether it is forever correct.

It is determined by whether it poses a truly question about time.

The question Relational Dynamics poses is:

Can we cease viewing relational evolution as fate's gift or debt, and instead view it as a temporal practice that can be understood, chosen, and taken responsibility for?

This question is worth for people a hundred years later to continue pursuing.

———

In 1836, a young man wrote three volumes of poetry, waited seven years, loved for forty years.

In 2026, another young man wrote twelve characters, made a software, embedded "components detachable, entities persist" into the architecture.

Between them spans 190 years.

But Relational Dynamics considers: they are two observational cross-sections on the same evolutionary path.

Upon the rain-dance terrace (舞雩之上), one may sing of homecoming (可以咏归).¹

The way of Youqi, today put into words.

But not completion.

Because dynamics never has a completion state—

As long as time still flows, relationships still evolve.

The first lesson of this discipline is learning to say to time:

Please continue.

Per aspera ad astra. Through its ordinariness, opening up the radiance of what is.²

[Complete Text]

Copyright Notice: This is a preview translation — Chinese original is the authoritative version. Copyright belongs to Guangzhou Phaenarete AI Technology Co., Ltd. Unauthorized reproduction, citation, or distribution is prohibited.

This references a passage from the Analects where Confucius asks his disciples to express their aspirations; one says he wishes to bathe in the Yi River, enjoy the wind on the rain-dance terrace (舞雩), and sing of returning home—a vision of harmonious communal life. ↩
The original Chinese "循此苦旅，以达星辰。在以它的平凡，开辟出是的光辉" combines the Latin motto "per aspera ad astra" (through hardships to the stars) with a philosophical statement: within ordinariness, illuminating the radiance of "what is" (being/truth). ↩