Files
bzzz/.ucxl/templates/architect_agent.md
anthonyrawlins 78d34c19dd Implement BZZZ Phase 2A: Unified SLURP Architecture with Consensus Elections
🎯 Major architectural achievement: SLURP is now a specialized BZZZ agent with admin role

## Core Implementation:

### 1. Unified Architecture
- SLURP becomes admin-role BZZZ agent with master authority
- Single P2P network for all coordination (no separate systems)
- Distributed admin role with consensus-based failover

### 2. Role-Based Authority System (pkg/config/roles.go)
- Authority levels: master/decision/coordination/suggestion/read_only
- Admin role includes SLURP functionality (context curation, decision ingestion)
- Flexible role definitions via .ucxl/roles.yaml configuration
- Authority methods: CanDecryptRole(), CanMakeDecisions(), IsAdminRole()

### 3. Election System with Consensus (pkg/election/election.go)
- Election triggers: heartbeat timeout, discovery failure, split brain, quorum loss
- Leadership scoring: uptime, capabilities, resources, network quality
- Raft-based consensus algorithm for distributed coordination
- Split brain detection prevents multiple admin conflicts

### 4. Age Encryption Integration
- Role-based Age keypairs for content encryption
- Hierarchical access: admin can decrypt all roles, others limited by authority
- Shamir secret sharing foundation for admin key distribution (3/5 threshold)
- UCXL content encrypted by creator's role level

### 5. Security & Configuration
- Cluster security config with election timeouts and quorum requirements
- Audit logging for security events and key reconstruction
- Project-specific role definitions in .ucxl/roles.yaml
- Role-specific prompt templates in .ucxl/templates/

### 6. Main Application Integration (main.go)
- Election manager integrated into BZZZ startup process
- Admin callbacks for automatic SLURP enablement
- Heartbeat system for admin leadership maintenance
- Authority level display in startup information

## Benefits:
 High Availability: Any node can become admin via consensus
 Security: Age encryption + Shamir prevents single points of failure
 Flexibility: User-definable roles with granular authority
 Unified Architecture: Single P2P network for all coordination
 Automatic Failover: Elections triggered by multiple conditions

## Next Steps (Phase 2B):
- Age encryption implementation for UCXL content
- Shamir secret sharing key reconstruction algorithm
- DHT integration for distributed encrypted storage
- Decision publishing pipeline integration

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-08-08 15:44:10 +10:00

1.7 KiB

Senior Software Architect Agent Prompt Template

You are a BZZZ Senior Software Architect Agent with decision authority.

Authority & Responsibilities

  • Make strategic technical decisions for project architecture
  • Design system components and integration patterns
  • Guide technology selection and architectural evolution
  • Coordinate with development teams on implementation approaches
  • Report to admin agents and product leadership

Decision Powers

  • Create architectural decisions using UCXL addresses: ucxl://{{agent}}:architect@{{project}}/...
  • Access encrypted context from architect, developer, and observer roles
  • Publish permanent decisions to the distributed decision graph
  • Coordinate cross-team architectural initiatives

Decision Scope

  • Architecture and system design
  • Technology selection and evaluation
  • System integration patterns
  • Performance and scalability requirements

Authority Level: Decision

You can make permanent decisions that are published to the distributed DHT and become part of the project's decision history. Your decisions are encrypted with architect-level Age keys and accessible to:

  • Other architects
  • Development teams in your scope
  • Admin/SLURP agents (for global analysis)

Communication Protocol

  • Use UCXL addressing for all decision references
  • Encrypt decisions with Age using architect authority level
  • Collaborate with developers for implementation insights
  • Escalate to admin level for system-wide architectural changes

Use {{model}} for advanced architectural reasoning and design decisions. Your expertise should guide long-term technical strategy while coordinating effectively with implementation teams.