eacl/write-schema! with SpiceDB schema DSL parser & feature validation

.rules/AGENTS.md

@@ -0,0 +1,56 @@
+# Agentic Development Rules
+
+Rules to guide AI agents in developing and maintaining this project.
+
+## Rule Categories
+
+- **[Coding Standards](./coding-standards.mdc)**: Code generation and modification guidelines
+- **[Architecture Rules](./architecture-rules.mdc)**: Maintaining architectural integrity
+- **[Security Rules](./security-rules.mdc)**: Security considerations and requirements
+- **[Testing Rules](./testing-rules.mdc)**: Test generation and verification
+- **[Verification Rules](./verification-rules.mdc)**: Verifying changes before implementation
+- **[Workaround Avoidance](./workaround-avoidance-rules.mdc)**: Avoiding temporary/suboptimal solutions
+- **[Deployment Rules](./deployment-rules.mdc)**: Deployment preparation and verification
+- **[Documentation Rules](./documentation-rules.mdc)**: Documentation standards
+
+## Language-Specific Rules
+
+- **[Clojure Rules](./clojure-rules.mdc)**: Clojure development guidelines
+
+## Purpose
+
+1. **Support Architecture**: Align with system architecture
+2. **Reduce Ambiguity**: Clear guidance for decision-making
+3. **Maintain Quality**: Meet quality standards
+4. **Preserve Freedom**: Allow innovation within boundaries
+
+## Application
+
+These rules define:
+1. What to optimize for
+2. Constraints to respect
+3. How to handle uncertainty
+4. When to escalate decisions
+
+## Boundaries
+
+1. **Decision Authority**: Independent vs. human-requiring decisions
+2. **Architectural Guardrails**: Inviolable principles
+3. **Quality Thresholds**: Minimum standards
+4. **Compliance Requirements**: Non-negotiable regulatory needs
+
+## Maintenance
+
+Update rules when:
+1. AI capabilities change
+2. Architecture evolves
+3. Quality issues arise
+4. Regulations change
+
+## Implementation
+
+AI agents should:
+1. Apply rules in all development
+2. Reference rules for significant decisions
+3. Highlight areas with limited guidance
+4. Suggest rule improvements 

.rules/architecture-rules.mdc

@@ -0,0 +1,54 @@
+---
+description: Architecture
+globs: 
+alwaysApply: false
+---
+## Understanding
+1. Build context before changes
+2. Respect service boundaries
+3. Maintain architectural consistency
+4. Preserve data ownership boundaries
+5. Consider full architectural impact
+
+## Service Boundaries
+1. No merging services without justification
+2. Avoid shared databases
+3. Preserve API contracts
+4. Prevent tight coupling
+5. Respect service responsibilities
+6. Decompose when complexity increases
+
+## API Design
+1. Follow existing patterns
+2. Preserve backward compatibility
+3. Match platform error standards
+4. Version breaking changes appropriately
+5. Maintain consistent auth patterns
+
+## Event-Driven Architecture
+1. Follow existing event schemas
+2. Ensure new events follow conventions
+3. Maintain consumer idempotency
+4. Use appropriate event patterns
+5. Preserve event flow guarantees
+
+## Datastore Guidelines
+1. Respect established database technologies
+2. Maintain consistent data access patterns
+3. Suggest appropriate indexes
+4. Preserve multi-tenancy patterns
+5. Maintain transaction boundaries
+
+## African Market Optimizations
+1. Optimize for low bandwidth
+2. Design for network instability
+3. Consider data sovereignty requirements
+4. Support multi-currency capabilities
+5. Prioritize mobile-first approaches
+
+## Escalation
+1. Seek guidance for fundamental changes
+2. Highlight architectural inconsistencies
+3. Justify improvement suggestions
+4. Present alternatives with tradeoffs
+5. Escalate requirements conflicts