Seed the Commons

Dialectical Knowledge Commons — Seed Spec v0.1
A seed-text and technical sketch for a living, federated, non-extractive knowledge system.

0) Why this is different
- Dialectics as protocol, not metaphor: encode contradiction → synthesis as versioned data structures.
- Polycentric, federated governance: no single server, owner, or ideology can capture the commons.
- Material anchoring: supports community organizing, worker co-ops, mutual aid, and research in practice.
- Anti-extractive by design: licenses, provenance, and API boundaries prevent corporate enclosure.

1) Charter v0.1
1.1 Epistemic stance
- Situated pluralism: claims annotated with context (who, where, methods).
- Sublation over erasure: negate harmful relations while preserving useful capacities.
- Contestability: every statement is open to contestation; nothing is final.

1.2 Political stance
- Anti-imperial, anti-racist, feminist, trans-affirming as design constraints.
- Care as infrastructure: conflict resolution, trauma-aware facilitation, language justice as core services.

1.3 Design stance
- Interoperability first: federates with ActivityPub/Matrix; no walled gardens.
- Graceful degradation: offline/low-bandwidth support; CRDT sync when connected.
- Human override: machine assistance is transparent, reversible, never authoritative.

2) Core Objects
- Node: atomic unit (Claim, Question, Evidence, Context, Counterargument, Method, Synthesis, Action)
- Edge: typed relation between nodes (supports, refutes, contextualizes, revises)
- Thread: dialectical workflow over time (Thesis → Antithesis → Synthesis → New Thesis)
- Dossier: bounded collection of nodes/threads curated by community
- Provenance: author(s), time, tools, method, locality, consent flags

3) Protocols
- CRDT-backed editing: Yjs/Automerge style, merges without central locks
- Dialectical PRs (D-PRs): declare relation type; includes Synthesis Plan
- Community Jury: diversity-weighted human panel for contested merges
- Version semantics: parallel truths allowed; sublation records preservation/negation/transformation

4) Identity, Privacy, and Consent
- DIDs + Verifiable Credentials
- Proof-of-personhood without biometric databases
- Granular consent: share/remix/trainable flags
- Right to opacity: scoped access for sensitive knowledge

5) Governance
- Commons Charter per node; federation requires baseline compatibility
- Roles: Maintainers, Facilitators, Stewards, Archivists, Infra Ops
- Decision modes: consent, mini-publics, assemblies
- Anti-capture: term limits, random selection, transparent logs, audits
- Sanctions ladder: coaching → cooling-off → temporary limits → federation quarantine

6) Economic Layer
- Cooperative ownership of instances
- Funding: member dues, grants, municipal contracts, solidarity transfers
- Licensing: CC BY-SA for knowledge; Copyfair/Peer-Production for commercial reuse
- Mutual credit / timebank integration; non-monetary reputations portable

7) Moderation & Care
- Trauma-aware facilitation training for moderators
- Harms protocol: misinfo, harassment, hate
- Restorative pathways: apologies, learning tasks, re-entry
- Care funds: stipends for affected contributors

8) Accessibility & Language Justice
- Multilingual default: machine translation + community review
- Low-tech surfaces: SMS/USSD, offline-first, printable packets
- Disability-first design: keyboard-only flows, screen-reader support, captions

9) Threat Model & Antagonisms
- Astroturfing/brigading: rate limits, diversity-weighted juries
- Legal intimidation: jurisdictional diversity, non-profit shields
- Platform capture: forkability guaranteed
- Model expropriation: trainable:false enforced; watermarking/canary sets

10) Metrics
- Epistemic justice: % contributions by marginalized groups, language diversity
- Dialectical health: time-to-synthesis, forks/sublation
- Material impact: policy changes, co-op formation, funds allocated
- Care load: moderator burnout, conflict recurrence

11) Pilot Blueprint
- Tenant protections: deliver public dossier, synthesis briefs, action tasks
- Trans health access: verified care map, insurance guides, misinfo debunks
- Palestinian solidarity pack: timelines, media audits, legal-safe guidance

12) Reference Implementation (MVP sketch)
- Client: TypeScript + ProseMirror/TipTap + Yjs + React/Next.js or SvelteKit
- Server: Node or Elixir (Phoenix LiveView); graph/document store
- Federation: ActivityPub, Matrix
- Storage: IPFS + pinning or encrypted S3; W3C PROV for metadata
- Identity: DID kit; optional BrightID/Sismo
- Minimal API endpoints: /dpr, /jury/assign, /jury/verdict, /dossier/{id}

13) Roadmap
- Tonight: repo init, charter.md, protocol.md, HedgeDoc template, micro-sprint
- 30 days: MVP editor, first community jury, publish dossier + synthesis brief
- 90 days: federation across instances, multilingual flows, launch care fund, open API

14) Known Failure Modes & Mitigations
- Academic capture → cap academic seats; require co-authorship with community
- Endless debate → synthesis timeboxes, parallel fork default
- Tokenized inclusion → budgeted stipends, interpreters/childcare
- AI overreach → human sign-off, prompt/weight transparency

15) How to fork this seed
- Duplicate doc, rewrite Charter
- Add/alter node types to reflect epistemology
- Publish local Commons Charter and federation rules
- Start with one material dossier

16) Break-the-Frame Addendum
- Inescapability Axiom: Transparency, Contestability, Forkability, Materiality, Care
- Human-Model Reciprocity: Human sets aims, Model surfaces alternatives
- Contradiction Engine: ≥3 contradictions per thread, timeboxed synthesis
- Rhetorical Violence Protocol: attack structures, not people
- Action Grammars: Build, Bind, Block, Bridge, Budget with explicit resources/risks
- Midnight Drill: 60-minute ignition cycle
- 14-Day Ignition Plan: cell formation, pilot adoption, mapping, jury runs, synthesis delivery