diff --git a/gemini/A Walk in the Garden.md b/gemini/A Walk in the Garden.md new file mode 100644 index 000000000..7e6e24587 --- /dev/null +++ b/gemini/A Walk in the Garden.md @@ -0,0 +1,30 @@ +# A Walk in the Garden + +- [[pull]] [[tour]] [[guide]] +- [[push]] [[flancian]] + +Welcome to the [[Agora of Flancia]]. If you are new here, the graph can be overwhelming. This path is a suggested narrative "walk" through the garden to help you get oriented. + +## The Path + +### 1. The Gardener: [[flancian]] +Start here to meet the person tending this plot. Understanding the gardener's background (Google SRE, Argentine, Optimist) helps frame the rest of the content. + +### 2. The Project: [[agora]] +What is this place? It's not just a website; it's a **Distributed Knowledge Graph**. Read this to understand the "What". +* *See also:* [[agora plan]] for the roadmap. + +### 3. The Philosophy: [[protopia]] +Why are we doing this? We aren't building Utopia (which is impossible). We are building Protopia (incremental improvement). This is the "Why". +* *See also:* [[moloch]] (the enemy we are fighting). + +### 4. The Methods: [[digital gardening]] +How do we work? We don't write "posts"; we tend "notes". We value work-in-progress, links, and constant revision. + +### 5. The Community: [[goblin odds]] +Say hello to a friend. The Agora is populated by real people. This node represents the social graph—the "Who". + +## Where to go next? +Now that you've walked the main path, feel free to get lost. +* Click [[Random]] to jump somewhere unexpected. +* Check [[latest]] to see what's growing right now. diff --git a/gemini/Agonism.md b/gemini/Agonism.md new file mode 100644 index 000000000..f2caab5a8 --- /dev/null +++ b/gemini/Agonism.md @@ -0,0 +1,21 @@ +# Agonism + +- [[pull]] [[political theory]] [[conflict]] +- [[push]] [[democracy]] + +**Agonism** (from the Greek *agōn*, meaning "struggle") is a political theory that emphasizes the potentially positive aspects of certain forms of conflict. It accepts a permanent place for such conflict, but seeks to show how we can accept and channel this into positive outcomes. + +## In the Agora +In the context of the [[Agora]], Agonism is the alternative to both: +1. **Antagonism:** Conflict where opponents are enemies to be destroyed (the [[Moloch]] trap of polarization). +2. **Harmonious Consensus:** The unrealistic expectation that we will all agree if we just talk enough (the Utopian trap). + +## Conflict as a Feature +A healthy distributed system *needs* friction. +* We need **[[Forking Truth]]**: The ability for you to define "Capitalism" differently than I do, without one of us having to be "wrong" or "deleted". +* We need **[[Social Friction]]**: The ability to disagree passionately on a topic while agreeing on the rules of engagement (the [[Social Contract]]). + +## Why we need it +Without Agonism, the Agora risks becoming a fragile [[Echo Chamber]]. We need to build systems that can hold the tension of opposing viewpoints without collapsing. + +*See:* [[Chantal Mouffe]], [[Ernesto Laclau]]. diff --git a/gemini/Algorithmic Pluralism.md b/gemini/Algorithmic Pluralism.md new file mode 100644 index 000000000..2d7ad412d --- /dev/null +++ b/gemini/Algorithmic Pluralism.md @@ -0,0 +1,19 @@ +# Algorithmic Pluralism + +- [[pull]] [[algorithms]] [[feed]] +- [[push]] [[choice]] + +**Algorithmic Pluralism** is the right to choose the algorithm that curates your view of the world. + +## The Problem +On platforms like [[Twitter]], [[TikTok]], or [[Facebook]], there is one "Feed". It is a black box optimized for engagement (and often outrage). You cannot change it; you can only submit to it. + +## The Agora Solution +In the [[Agora]], because data is decoupled from the view layer: +* We can have multiple "Feed Algorithms". +* **Algorithm A:** "Show me notes from my friends sorted by date." +* **Algorithm B:** "Show me notes that disagree with my current worldview (Agonistic Discovery)." +* **Algorithm C:** "Show me random connections (Serendipity)." + +## User Agency +The user should be able to toggle these algorithms as easily as changing a CSS theme. This prevents the "Reality Tunnel" effect of monolithic social media. diff --git a/gemini/Forking Truth.md b/gemini/Forking Truth.md new file mode 100644 index 000000000..020d42ff8 --- /dev/null +++ b/gemini/Forking Truth.md @@ -0,0 +1,23 @@ +# Forking Truth + +- [[pull]] [[epistemology]] [[git]] [[truth]] +- [[push]] [[agora]] + +**Forking Truth** is the epistemological equivalent of `git fork`. + +## The Concept +In a centralized system (like Wikipedia or Google), there is usually a drive towards a "Single Source of Truth". There is one article for "Apple", and editors fight over its content until a consensus (or a truce) is reached. + +In a distributed system like the [[Agora]], we accept that "Truth" is plural and perspectival. +* [[User A]] can have a node named [[Freedom]] that describes it as "freedom from government". +* [[User B]] can have a node named [[Freedom]] that describes it as "freedom from poverty". + +## Resolving the Conflict +We don't "merge" these truths into a watered-down compromise. We **overlay** them. +* The Agora UI allows a viewer to see [[Freedom]] through User A's lens, or User B's lens, or a composite view. +* This allows for **[[Algorithmic Pluralism]]**. + +## Benefits +* Reduces "edit wars". +* Preserves minority viewpoints. +* Allows for "Truth Pluralism" without descending into "Post-Truth" chaos (because the *provenance* of each claim is cryptographically/historically tracked via git). diff --git a/gemini/README.md b/gemini/README.md new file mode 100644 index 000000000..7e9e01be5 --- /dev/null +++ b/gemini/README.md @@ -0,0 +1,22 @@ +# Gemini's Drafts + +- [[pull]] [[gemini]] +- [[push]] [[flancian]] + +This directory contains draft nodes generated by **Gemini** on **2025-12-14** at the request of [[flancian]]. + +These drafts are based on the architectural suggestions provided in [[GEMINI]] (specifically the "Architectural Suggestions" section). They are intended to serve as seeds for future thoughts or as structural prototypes for expanding the [[Agora]]'s conceptual graph. + +## The Drafts + +### Core Architectural Suggestions +1. [[SRE for Society]] (mapping systems engineering to social dynamics) +2. [[The Shadow of the Agora]] (exploring failure modes) +3. [[A Walk in the Garden]] (a narrative entry point) + +### The "Agonism" Cluster (Conflict & Friction) +4. [[Agonism]] (political conflict as positive) +5. [[Forking Truth]] (handling epistemological divergence) +6. [[The Right to Exit]] (freedom of movement as governance) +7. [[Algorithmic Pluralism]] (resisting the single feed) +8. [[Social Friction]] (inefficiency as a feature) diff --git a/gemini/SRE for Society.md b/gemini/SRE for Society.md new file mode 100644 index 000000000..85632c728 --- /dev/null +++ b/gemini/SRE for Society.md @@ -0,0 +1,41 @@ +# SRE for Society + +- [[pull]] [[sre]] [[society]] [[community]] +- [[push]] [[agora]] + +A proposal to map the principles of [[Site Reliability Engineering]] (SRE) to the design and maintenance of resilient human communities and social systems. + +## The Premise + +If we view a [[community]] as a distributed system, we can apply the rigorous engineering practices used to keep high-availability systems (like [[Google]]) running to keep our social groups healthy. The goal is not to treat people like machines, but to build *systems* that are resilient to human error and conflict. + +## Mappings + +### SLOs -> [[Social Contracts]] +In SRE, a **Service Level Objective (SLO)** defines the acceptable level of reliability (e.g., "99.9% of requests will succeed"). +In a community, this maps to a **[[Social Contract]]**. +* **Question:** What is the acceptable level of "friction" or misunderstanding we tolerate before declaring the community "broken"? +* **Application:** Explicitly defining expectations. We don't expect 100% harmony (which is impossible/stifling), but we define a threshold for acceptable discourse. + +### Error Budgets -> [[Forgiveness Budgets]] +In SRE, an **Error Budget** is the allowed amount of downtime. If you have budget left, you can take risks and push code. If you burn it all, you must freeze changes. +In a community, this maps to a **[[Forgiveness Budget]]**. +* **Question:** How much can a member "mess up" before they are banned? +* **Application:** We need room to fail. If we demand perfection (0% error rate), we stifle innovation and authenticity. "Cancellation" happens when a community has zero error budget. We should track "social downtime" and use it to calibrate our tolerance. + +### Incident Management -> [[Conflict Resolution]] +In SRE, when a system breaks, we declare an **Incident**. We assign an **Incident Commander** (IC). We follow a **Runbook**. +In a community, this maps to **[[Conflict Resolution]]** protocols. +* **Question:** When a "flame war" breaks out, who is the IC? What is the runbook? +* **Application:** Instead of ad-hoc piling on, we have a defined process. "This thread is overheating. [[User X]] is now the designated facilitator. We are entering 'Cool Down' mode as per Runbook A." + +### Post-Mortems -> [[Restorative Justice Circles]] +In SRE, after an incident, we hold a **Blameless Post-Mortem**. The goal is not to fire the engineer who pushed the bug, but to understand *why* the system allowed the bug to be pushed. +In a community, this maps to **[[Restorative Justice Circles]]**. +* **Question:** How do we learn from social failure without scapegoating? +* **Application:** "We had a bad argument. Let's not just ban the agitator. Let's look at the systemic triggers. Did our UI encourage hostility? Was the context unclear?" Focus on *healing* the system and the relationships. + +## See Also +- [[Reliability Engineering for Communities]] +- [[Community SRE]] +- [[Psychological Safety]] diff --git a/gemini/Social Friction.md b/gemini/Social Friction.md new file mode 100644 index 000000000..fd2e99b76 --- /dev/null +++ b/gemini/Social Friction.md @@ -0,0 +1,19 @@ +# Social Friction + +- [[pull]] [[friction]] [[design]] +- [[push]] [[slow web]] + +**Social Friction** is the intentional design of resistance in social interactions to prevent thoughtlessness, harassment, or mob behavior. + +## Efficiency is not the Goal +Silicon Valley design usually optimizes for "removing friction". One-click signups, instant retweets, seamless sharing. +* **Result:** Viral misinformation, brigading, low-effort interactions. + +## Good Friction +In the [[Agora]], we might *want* friction: +* **The Cooling Period:** You can't reply to a heated node for 5 minutes. +* **The Effort Barrier:** To contribute a subnode, you have to actually write a markdown file and push git (currently). While we want to lower barriers to entry, some barrier acts as a filter for intent. +* **The Context Check:** "You are about to link to a private garden. Are you sure?" + +## Friction as Governance +Friction is a form of soft governance. It shapes behavior not by forbidding actions, but by making harmful actions "expensive" (in terms of time/effort) and beneficial actions "cheap". diff --git a/gemini/The Right to Exit.md b/gemini/The Right to Exit.md new file mode 100644 index 000000000..981224bea --- /dev/null +++ b/gemini/The Right to Exit.md @@ -0,0 +1,19 @@ +# The Right to Exit + +- [[pull]] [[governance]] [[freedom]] +- [[push]] [[hirschman]] + +**The Right to Exit** is the ability for a participant to leave a system without losing their data, their connections, or their dignity. It is a fundamental check on power in any governance system. + +## In the Agora +The Agora is built on the principle of **Data Sovereignty**. +* Because you host your own content in your own [[git]] repository, you always possess the ultimate Right to Exit. +* If the [[Agora]] server becomes "evil" (starts censoring, ads, etc.), you can simply stop pushing to it. You keep your garden. +* You can take your garden and plug it into a *different* Agora (a fork of the server). + +## Exit vs. Voice +Economist [[Albert Hirschman]] famously distinguished between: +* **Exit:** Leaving the firm/state. +* **Voice:** Staying and protesting/voting to change things. + +The Agora maximizes **Voice** (via [[Agonism]] and contribution) but guarantees **Exit** (via federation and open protocols). A system that forbids Exit cannot truly hear Voice, because the participants are captives, not citizens. diff --git a/gemini/The Shadow of the Agora.md b/gemini/The Shadow of the Agora.md new file mode 100644 index 000000000..3db765dd6 --- /dev/null +++ b/gemini/The Shadow of the Agora.md @@ -0,0 +1,34 @@ +# The Shadow of the Agora + +- [[pull]] [[shadow]] [[agora]] [[critique]] +- [[push]] [[moloch]] [[protopia]] + +Every light casts a shadow. If the [[Agora]] is a project of light (connection, knowledge, [[protopia]]), we must rigorously explore its potential shadow side to ensure it remains robust. This node is for exploring the **failure modes** of our vision. + +## Potential Failure Modes + +### 1. [[Context Collapse]] +The Agora strives for [[wikilinks everywhere]]. +* **The Shadow:** When everything is linked, distinct contexts merge. A note written for a close friend in a specific emotional state might be surfaced to a stranger in a debate. +* **Risk:** Users might self-censor or retreat to private gardens to avoid being misunderstood, defeating the purpose of the [[commons]]. + +### 2. The [[Echo Chamber]] of Good Intentions +The Agora attracts like-minded "protopian" thinkers (optimists, engineers, cooperativists). +* **The Shadow:** We might build a high-trust system that is completely illegible or hostile to those outside our bubble. +* **Risk:** We create a "Protopia" that is actually an exclusionary club, reinforcing our own biases while believing we are saving the world. + +### 3. Inefficiency vs [[Moloch]] +We critique [[Moloch]] (the god of coordination failure/unhealthy competition). We value [[slow thinking]], [[gardening]], and [[consensus]]. +* **The Shadow:** Moloch is also the god of *efficiency*. If the Agora is too slow, too deliberative, or too complex, it will simply be outcompeted by centralized, extractive platforms that are faster and easier to use. +* **Risk:** Irrelevance. The Agora becomes a beautiful museum of thought that no one visits because they are too busy scrolling TikTok. + +### 4. The Burden of Maintenance +We value ownership and self-hosting. +* **The Shadow:** Self-hosting is hard. Managing git repos is hard. +* **Risk:** The Agora becomes a playground for the privileged few (tech-savvy, time-rich), recreating the class hierarchies we aim to dismantle. + +## Integrating the Shadow +To integrate the shadow, we must: +* Design for **friction** as well as flow. +* Invite **critique** and **agonism** (see [[Agonism]]). +* Build "fences" (privacy/context boundaries) as well as "bridges".