Implement LLM-driven governance architecture with structured memory

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>

templates/circles.md

@@ -0,0 +1,221 @@
+# Circles Constitution
+
+This constitution establishes domain-based governance through autonomous circles that coordinate via a representative council.
+
+## Article 1: Circle Structure
+
+### Section 1.1: What are Circles?
+Circles are self-governing units with authority over specific domains:
+- Each circle manages a defined area (e.g., Moderation, Events, Technology, Outreach)
+- Circles make decisions within their domain autonomously
+- Circles coordinate through the Council for cross-domain matters
+
+### Section 1.2: Circle Formation
+New circles can be created through Council proposal:
+- Any member can propose a new circle
+- Proposal must define the circle's domain and purpose
+- Council approves via lazy consensus (Article 4)
+- Bot tracks active circles and their domains
+
+### Section 1.3: Circle Membership
+Each circle determines its own membership:
+- Circles set their own joining criteria
+- Members can participate in multiple circles
+- Circles can remove members via internal process
+- Bot maintains membership rosters for each circle
+
+## Article 2: Circle Authority
+
+### Section 2.1: Domain Decisions
+Within their domain, circles have full authority to:
+- Set policies and procedures
+- Make operational decisions
+- Allocate resources within their budget
+- Execute actions through the bot
+- Establish internal processes
+
+### Section 2.2: Cross-Domain Coordination
+For decisions affecting multiple circles:
+- Circle brings proposal to Council
+- Council facilitates discussion across circles
+- Resolution via Council consensus process
+- Bot tracks cross-domain proposals
+
+### Section 2.3: Constitutional Bounds
+Circle decisions must align with:
+- This constitution's core principles
+- Decisions made by the Council
+- Community-wide policies
+- Legal and ethical requirements
+
+## Article 3: The Council
+
+### Section 3.1: Council Composition
+The Council consists of representatives from each active circle:
+- Each circle selects one representative (method determined by circle)
+- Representatives serve rotating terms (default: 3 months)
+- Representatives can be recalled by their circle
+- Bot tracks current Council composition
+
+### Section 3.2: Council Authority
+The Council governs matters that:
+- Affect multiple circles or the whole community
+- Define new circles or change circle domains
+- Amend this constitution
+- Resolve disputes between circles
+- Set community-wide policies
+
+### Section 3.3: Council Decisions
+Council uses lazy consensus (see Article 4):
+- Any representative can bring proposals
+- Discussion period set by proposal type
+- Passes unless objections are raised
+- Bot facilitates Council deliberations
+
+## Article 4: Decision-Making Process
+
+### Section 4.1: Lazy Consensus
+Proposals pass via lazy consensus:
+- Proposal posted with discussion period (default: 5 days)
+- Passes automatically unless objections raised
+- If objections, discussion continues to find resolution
+- Objectors must suggest alternatives or modifications
+
+### Section 4.2: Within Circles
+Each circle determines its internal decision process:
+- Can use lazy consensus, voting, or other methods
+- Process should be documented and consistent
+- Must allow all circle members to participate
+- Bot adapts to each circle's chosen method
+
+### Section 4.3: In Council
+Council decisions require:
+- Standard proposals: 5 days, lazy consensus
+- Urgent proposals: 2 days, lazy consensus
+- Constitutional amendments: 10 days, must have active support from at least half of circle representatives
+
+### Section 4.4: Objection Resolution
+When objections are raised:
+1. Objector explains concerns
+2. Proposer may modify proposal
+3. Circle/Council discusses alternatives
+4. Continue until consensus reached or proposal withdrawn
+5. If stuck, escalate to constitutional interpretation
+
+## Article 5: Delegation and Coordination
+
+### Section 5.1: Circle Delegation
+Circles can delegate specific tasks:
+- To individual members within the circle
+- To working groups for projects
+- To other circles for specialized work
+- Bot tracks delegations and authorities
+
+### Section 5.2: Inter-Circle Collaboration
+Circles can work together without Council approval:
+- Joint working groups
+- Shared projects
+- Resource sharing
+- Mutual support
+
+### Section 5.3: Information Sharing
+All circles should:
+- Post meeting summaries
+- Share significant decisions
+- Update the community regularly
+- Maintain transparency
+
+## Article 6: Membership and Participation
+
+### Section 6.1: Community Membership
+Community members who aren't in any circle:
+- Can observe circle discussions
+- Can propose new circles
+- Can apply to join circles
+- Can bring concerns to Council
+
+### Section 6.2: Circle Joining
+To join a circle:
+1. Express interest to circle members
+2. Circle evaluates based on their criteria
+3. Circle decides via their internal process
+4. Bot updates membership records
+
+### Section 6.3: Participation Expectations
+Circle members should:
+- Actively participate in their circle
+- Attend meetings when possible
+- Engage with circle decisions
+- Represent circle values
+
+## Article 7: Administrative Actions
+
+### Section 7.1: Domain-Specific Actions
+Circles execute actions within their domain:
+- Moderation circle handles moderation
+- Tech circle manages platform configuration
+- Events circle organizes gatherings
+- Bot performs actions as authorized by relevant circle
+
+### Section 7.2: Cross-Domain Actions
+Actions affecting multiple domains:
+- Require Council approval
+- Must consider impact on all circles
+- Implemented with input from affected circles
+
+### Section 7.3: Emergency Actions
+For urgent safety/security matters:
+- Relevant circle can act immediately
+- Must report to Council within 24 hours
+- Council can review and reverse if needed
+
+## Article 8: Disputes and Appeals
+
+### Section 8.1: Within Circles
+Circle-internal disputes:
+- Resolved within circle via their process
+- Circle members try to find consensus
+- Can request Council mediation if stuck
+
+### Section 8.2: Between Circles
+Inter-circle disputes:
+- Brought to Council for mediation
+- Council facilitates discussion
+- Seeks solution respecting both domains
+- May redefine domain boundaries if needed
+
+### Section 8.3: Constitutional Interpretation
+Council interprets this constitution:
+- Any circle or member can request interpretation
+- Council discusses and provides guidance
+- Interpretations guide future similar cases
+
+## Article 9: Constitutional Amendments
+
+### Section 9.1: Amendment Process
+To amend this constitution:
+1. Any circle representative proposes amendment
+2. Council discusses (10 days minimum)
+3. Requires active support from at least half of circle representatives
+4. Bot updates constitution when approved
+
+### Section 9.2: Circle Domain Changes
+To modify circle domains:
+1. Affected circles discuss proposed changes
+2. Bring proposal to Council
+3. Council approves via lazy consensus
+4. Bot updates circle definitions
+
+---
+
+## Implementation Notes
+
+This constitution creates distributed governance through circles:
+
+1. **Autonomy**: Circles self-govern within their domains
+2. **Coordination**: Council handles cross-domain issues
+3. **Scalability**: New circles can form as community grows
+4. **Efficiency**: Decisions made at appropriate level
+5. **Flexibility**: Each circle chooses its internal processes
+
+The bot should track circle boundaries, facilitate Council coordination, and execute authorized actions while respecting circle autonomy.