Ecosystem-wide documentation for Ann Lite — the reference point for how all 13 repositories fit together, and the policies that govern them.
Where annlite-backend, annlite-database, etc. each document their own internals, this repository documents the ecosystem: cross-repository architecture, shared policies, and governance. It links to repository-specific docs rather than duplicating them, so there is exactly one source of truth for any given detail.
| Section | Covers |
|---|---|
| Architecture | Full ecosystem diagram, repository responsibilities, cross-cutting invariants |
| API | Pointer to annlite-backend's API reference |
| Database | Pointer to annlite-database's schema/ERD, entity summary |
| Payments | Both donation methods, unified provider abstraction, confirmation flow |
| CeloHT Integration | Scope and boundaries of the CeloHT integration |
| Security | Pointer to annlite-security, cross-cutting principles |
| Privacy | What is/isn't collected, beneficiary data minimization, donor anonymity |
| Charity Policy | Organization verification, project lifecycle, beneficiary protection |
| Donation Policy | Ethical principles, supported methods, refund policy |
| Transparency Policy | Public donation feed rules, fund progress tracking |
| Content Policy | Editorial workflow, languages, theological consistency |
| Accessibility | Current state and known gaps, WCAG 2.1 AA target |
| Development | Local setup order, cross-repo linking, coding standards |
| Deployment | Deployment principles (full detail pending annlite-infrastructure) |
| Testing | Per-repository testing strategy, cross-cutting invariants worth testing |
| Roadmap | Build-order status, honestly tracked known gaps |
| Governance | Founder, decision-making, roles, ethical oversight |
- New contributor? Start with Architecture and Development.
- Reviewing the donation flow? Read Payments, Donation Policy, and Transparency Policy together.
- Handling beneficiary or user data? Read Privacy and Charity Policy first.
This documentation reflects the ecosystem as actually built, including gaps — see Roadmap for a plain list of what is not yet implemented. Documentation changes should accompany the code change that makes them true, not precede it as aspiration.
Every repository in the Ann Lite organization. This is the connective layer, not a dependency of any single one.