Four entry points
This site is the engineering reference, not marketing copy. Everything load-bearing for contributors — human or AI — lives here.
Architecture
System layers, module-level docs, and the architecture-index that every backend file is mapped against by a pre-commit gate.
ADRs
Numbered architectural decision records — context, alternatives, consequences. Read directly from the canonical docs/adr/ tree, no copies.
Research
Pre-decision research artifacts: landscape scans, deep dives, focused spikes. Each doc is opinionated and feeds upcoming ADRs.
Methodology
Ratiba-specific overrides and supplements to the global S4U methodology — agentic-development patterns, auto-debug logging, the harness.
Why this is different
The agent is the UI.
Every competitor in this market — Fresha, Setmore, Q-SYS, Gebeya Jitume — ships a web dashboard for the business owner and a booking link for the customer. Both assume screen literacy. Ratiba inverts that: business owners run their operation from inside WhatsApp; customers book by speaking, in Swahili or English. The dashboard exists only for bulk operations and onboarding.
That commitment is structural, not cosmetic. It shapes the architecture (channel-boundary tenant resolution, conversation-as-canonical-state, shared orchestration with channel-specific shapers), the testing strategy (golden-conversation snapshots over SQL fixtures), the methodology (eval-driven dev, auto-debuggable logging), and the harness (Docusaurus + architecture-index + pre-commit gates) you are reading now.