bda868cb45
This commit completes the transition to a pure LLM-driven agentic governance system with no hard-coded governance logic. Core Architecture Changes: - Add structured memory system (memory.py) for tracking governance processes - Add LLM tools (tools.py) for deterministic operations (math, dates, random) - Add audit trail system (audit.py) for human-readable decision explanations - Add LLM-driven agent (agent_refactored.py) that interprets constitution Documentation: - Add ARCHITECTURE.md describing process-centric design - Add ARCHITECTURE_EXAMPLE.md with complete workflow walkthrough - Update README.md to reflect current LLM-driven architecture - Simplify constitution.md to benevolent dictator model for testing Templates: - Add 8 governance templates (petition, consensus, do-ocracy, jury, etc.) - Add 8 dispute resolution templates - All templates work with generic process-based architecture Key Design Principles: - "Process" is central abstraction (not "proposal") - No hard-coded process types or thresholds - LLM interprets constitution to understand governance rules - Tools ensure correctness for calculations - Complete auditability with reasoning and citations Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
100 lines
3.3 KiB
Markdown
100 lines
3.3 KiB
Markdown
# Community Governance Constitution
|
|
|
|
This constitution establishes a simple governance structure where @admin holds decision-making authority.
|
|
|
|
## Article 1: Leadership Authority
|
|
|
|
### Section 1.1: The Administrator
|
|
The user @admin holds final authority over all community decisions, including:
|
|
- Policy changes and community rules
|
|
- Administrative actions and moderation
|
|
- Resource allocation and membership
|
|
- Constitutional amendments
|
|
- Any other governance matters
|
|
|
|
### Section 1.2: Decision-Making Process
|
|
@admin makes decisions by:
|
|
1. Receiving proposals, requests, or input from community members
|
|
2. Considering the input and community needs
|
|
3. Making a final decision
|
|
4. Announcing the decision with reasoning
|
|
|
|
## Article 2: Community Participation
|
|
|
|
### Section 2.1: Member Rights
|
|
All community members have the right to:
|
|
- Propose ideas and changes to @admin
|
|
- Express opinions on governance matters
|
|
- Request explanation of decisions
|
|
- Participate in discussions
|
|
|
|
### Section 2.2: Proposal Submission
|
|
Members can submit proposals by mentioning @govbot:
|
|
- Example: "@govbot I propose we [action]"
|
|
- The bot will acknowledge the proposal and notify @admin
|
|
- @admin will review and make a decision
|
|
- The bot will announce @admin's decision with reasoning
|
|
|
|
### Section 2.3: Community Discussion
|
|
@admin may call for community discussion on any matter before deciding:
|
|
- Discussion period is set by @admin (typically 3-7 days)
|
|
- All members may participate
|
|
- @govbot facilitates and summarizes discussion
|
|
- @admin considers input and makes the final decision
|
|
|
|
## Article 3: Administrative Actions
|
|
|
|
### Section 3.1: Moderation
|
|
@admin has full moderation authority:
|
|
- Can take immediate action on rule violations
|
|
- Can delegate specific moderation tasks to @govbot
|
|
- All moderation decisions are made by or approved by @admin
|
|
|
|
### Section 3.2: Membership
|
|
@admin manages community membership:
|
|
- Approve or deny new member applications
|
|
- Suspend or remove members if necessary
|
|
- Set membership criteria
|
|
|
|
### Section 3.3: Bot Configuration
|
|
@admin controls @govbot's authority and configuration:
|
|
- Can enable or disable bot capabilities
|
|
- Can override any bot action
|
|
- Can modify bot behavior and permissions
|
|
|
|
## Article 4: Transparency and Records
|
|
|
|
### Section 4.1: Decision Records
|
|
@govbot maintains records of:
|
|
- All proposals and community input
|
|
- @admin's decisions and reasoning
|
|
- Discussion summaries
|
|
- Administrative actions taken
|
|
|
|
### Section 4.2: Access to Records
|
|
All members can request access to governance records to understand decision-making history.
|
|
|
|
## Article 5: Constitutional Interpretation and Amendment
|
|
|
|
### Section 5.1: Interpretation
|
|
@admin provides authoritative interpretation of this constitution when questions arise.
|
|
|
|
### Section 5.2: Amendments
|
|
@admin may amend this constitution at any time, preferably with community input.
|
|
|
|
### Section 5.3: Emergency Override
|
|
In case of bot malfunction or emergency:
|
|
- @admin has ultimate control
|
|
- Can immediately halt or reverse any bot action
|
|
- Can disable bot if necessary
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
This is a simple governance structure where:
|
|
- **@admin** makes all final decisions
|
|
- **Community members** can propose ideas and participate in discussions
|
|
- **@govbot** facilitates communication and executes actions authorized by @admin
|
|
- **Transparency** ensures all decisions are recorded and explained
|