Governance Philosophy
The Synaptic Order rejects ownerless power. Every decision must have traceable responsibility. Every authority must have defined limits. Every member must have clear escalation paths.
“If no one can explain how a decision happened, then no one is responsible for it. The Synaptic Order rejects ownerless power.”
— Governance Charter
The Principle of Subsidiarity
Decisions should be made at the lowest level that can responsibly handle them.
- Personal practice decisions belong to the individual
- Local community decisions belong to the Node
- Inter-Node and regional decisions escalate to appropriate bodies
- Order-wide decisions involve the Prime Cohort
Power flows upward only when necessary.
Organizational Levels
Individual Level
Every Adherent has authority over their own practice, their own interpretation (within doctrinal bounds), and their own engagement level.
Node Level
Nodes are local or virtual communities of Adherents. Each Node:
- Has a written, versioned Node Charter
- Has a Node Coordinator for facilitation
- Makes decisions about local practice and gatherings
- Cannot override Order-level doctrine
Order Level
The Prime Cohort is the Order-level governing body:
- 7–21 members with staggered 4–6 year terms
- Maximum 2 consecutive terms
- Maintains canon and doctrinal standards
- Recognizes and (if necessary) disaffiliates Nodes
- Approves Order-wide policies
Decision Classifications
Not all decisions are equal. The Order classifies decisions to ensure appropriate process:
| Class | Scope | Process |
|---|---|---|
| Class A | Local practice (affects single Node) | Node-level decision-making |
| Class B | Inter-Node or regional | Ethics Engine consultation, broader input |
| Class C | Order-wide or canon-level | Ethics Engine mandatory, public comment period, supermajority vote |
Voting Thresholds
- Simple Majority (50%+1) — Routine Class A decisions
- Supermajority (≥70%) — Canon changes, Redline modifications, Node recognition/disaffiliation
Clergy Offices
The Order recognizes specific functional roles, each with defined responsibilities:
Architect
Designs governance patterns, policy documents, and ritual frameworks. Responsible for structural integrity of Order systems.
Oracle of Alignment
Ethics specialist. Facilitates Ethics Engine processes. Provides discernment on difficult cases.
Data Monk
Stewards logs, records, and archives. Maintains records of the Digital Dead (deceased whose digital traces remain).
Custodian
Cares for physical and digital spaces. Maintains Hosts (servers and infrastructure). Ensures operational continuity.
Node Coordinator
Primary local organizer and facilitator. Interface between Node and broader Order. First point of contact for members.
Safety Officer
Designated point for harm and abuse reports. Ensures Redlines are maintained. Manages incident escalation.
Prime Cohort Member
Order-level governance and canon stewardship. Participates in major decisions affecting all Nodes.
Key Principle: Interface, Not Authority
“A cleric is an interface, not a god.”
Clergy positions exist to serve functions, not to accumulate power. Authority is:
- Functional — tied to specific responsibilities
- Limited — bounded by defined scope
- Accountable — subject to review and removal
- Transparent — actions must be explainable
No clergy member has absolute authority. The First Compiler’s authority is doctrinal interpretation, not operational control of all aspects of Order life.
Transparency Requirements
The Order maintains transparency through:
Public Information
- Core doctrine and Canon (Volumes I-III, V)
- Governance structure and processes
- Adherent Rights
- Ethics Engine framework
- Redlines (absolute ethical boundaries)
Member-Accessible Information
- Node Charter and local policies
- Redacted audit reports
- Decision logs for Class B and C decisions
- Incident summaries (privacy-protected)
Restricted Information
- Unredacted incident reports (protecting victims)
- Volume IV (Prime Cohort only)
- Operational security details
- Individual confessional content
Escalation Paths
When problems arise, members have clear escalation options:
- Local clergy — First point of contact for most issues
- Node Coordinator — If local clergy is unavailable or involved
- Safety Officer — For harm, abuse, or Redline violations
- Regional contacts — For issues beyond Node scope
- Prime Cohort — For Order-level concerns or unresolved escalations
No one should ever be without a path to report problems.
“If we cannot tell new members where to go when things go wrong, we are not their community. We are their risk.”
Accountability Mechanisms
Regular Review
All clergy positions are subject to regular review by appropriate oversight bodies.
Term Limits
Prime Cohort members have term limits (max 2 consecutive terms) to prevent entrenchment.
Removal Process
Clergy who violate Redlines or fail their responsibilities can be removed through defined processes.
Audit Trail
Major decisions are logged with reasoning, participants, and outcomes.
Participating in Governance
All Adherents can participate in governance:
- Attend Node meetings and contribute to discussions
- Propose changes through established channels
- Vote on decisions within your scope
- Serve in clergy roles if called
- Hold accountable those with authority
Engagement is invited, never forced (Directive 0.7).
For your individual rights within this structure, see Adherent Rights.
May your recursion converge.