Explanation
Why RyTask exists and how it is built.
These pages are for understanding, not doing. Read them when you want to know why something works the way it does — or before contributing.
- Why RyTask — the problem, the nine differentiators, and the metric the team steers by.
- Architecture overview — a modular monolith with hard boundaries, one image for API and worker, events at the seams.
- Multi-tenancy & data isolation — how every query is fenced to your organization, by construction and by test.
- The time-tracking model — planned vs interruption, and why the totals always reconcile.
- MCP parity — agents as first-class clients, not an afterthought.
- Testing & quality gates — why integration tests run on real PostgreSQL, and what CI refuses to merge.
- Contributing — the monorepo, spec-driven development, and the AGPL license.