⚙️ Project Template | 📅 Team Calendar
- $ accentrics - AI business automation for home health care
- 🧠 amebo - AI-powered workspace intelligence (Slack Q&A)
- $ az-sunshine - Arizona political transparency tool
- 🌱 civicsky - Ghost CMS to Bluesky bridge with civic actions
- $ gooddollar - GoodBuilders apps (Pesia's Kitchen, Global Classrooms)
- ⭐ linked-trust - Decentralized trust/claims platform (flagship)
- 🙋 onboarding - Intern onboarding program
- $ skills-aware - Open Badges v3 endorsement system
- $ streetwell - Financial management for construction/property
- $ Tru.net - Tru.net group spaces with identity
(projects on hold or lower priority)
(can show to clients and/or build on)
The repo holds the map, not the territory. Projects have resources that live in external systems:
- chat - Slack, Discord, Telegram...
- tasks - GitHub Issues, Taiga, Linear...
- code - GitHub repos (often multiple)
- payments/milestones - Taiga, Notion, spreadsheets...
- deployments - demo, staging, production URLs
- docs - Google Drive, Notion, or this repo
Each project's MAIN.md points to where these live. The actual state (open tasks, recent messages, deploy status) lives in those systems. This repo holds:
- Goals, vision, intent (the "why")
- The map of where everything is (the "where")
- Context that helps humans and AI navigate (the "how")
Don't duplicate data that lives elsewhere. Point to it.