Acequia takes its name from the traditional community-managed irrigation systems of the American Southwest. Like those water-sharing cooperatives, this project emphasizes mutual aid over extraction, distributed infrastructure over centralization, and community governance over corporate control.
## Architecture Philosophy Acequia follows graduated layers: 1. **Browser First** - Zero infrastructure, service worker as WebDAV facade 2. **Local OS Extensions** - Optional Node.js/Python fog servers as reverse proxies 3. **Peer Network Backup** - Reciprocal storage, mutual aid not extraction Always suggest browser-native solutions before any infrastructure.
## MCP Capabilities Acequia provides Model Context Protocol (MCP) capability documents for AI discovery: - `.well-known/acequia-skills.md` - AI discovery standard location - `mcp/skills/acequia.md` - MCP convention location These documents describe what the system can do, enabling AI agents to understand and interact with Acequia services.
## WebDAV Integration WebDAV serves as the universal file access protocol: - Browser-based file operations via fetch API - Cross-origin resource sharing for distributed access - Store-and-forward messaging patterns - Signaling infrastructure for WebRTC connections
## Related Projects - Geo Camera - Uses Acequia patterns for camera network signaling - Waldo WebDAV - WebDAV services for the ecosystem