https://ratiba.chat/adr/weekly0.5https://ratiba.chat/adr/ADR-0001-tech-stackweekly0.5https://ratiba.chat/adr/ADR-0002-multi-tenant-isolationweekly0.5https://ratiba.chat/adr/ADR-0003-fsm-persistenceweekly0.5https://ratiba.chat/adr/ADR-0004-testing-strategyweekly0.5https://ratiba.chat/adr/ADR-0005-orchestration-modelweekly0.5https://ratiba.chat/adr/ADR-0006-handoff-modelweekly0.5https://ratiba.chat/adr/ADR-0007-payments-orchestrationweekly0.5https://ratiba.chat/adr/ADR-0008-whatsapp-cloud-api-directweekly0.5https://ratiba.chat/adr/ADR-0009-channel-agnostic-conversation-substrateweekly0.5https://ratiba.chat/adr/ADR-0010-tenant-self-service-customisationweekly0.5https://ratiba.chat/adr/ADR-0011-docs-ia-and-toolingweekly0.5https://ratiba.chat/adr/ADR-0012-m13-containers-and-real-pilotweekly0.5https://ratiba.chat/adr/ADR-0013-phase0-knowledge-answersweekly0.5https://ratiba.chat/adr/ADR-0014-conversational-knowledge-authoringweekly0.5https://ratiba.chat/adr/ADR-0015-pooled-deferred-allocationweekly0.5https://ratiba.chat/docs/weekly0.5https://ratiba.chat/docs/architectureweekly0.5https://ratiba.chat/docs/architecture/component-mapweekly0.5https://ratiba.chat/docs/architecture/data-flowweekly0.5https://ratiba.chat/docs/architecture/overviewweekly0.5https://ratiba.chat/docs/architecture/schema-evolutionweekly0.5https://ratiba.chat/docs/architecture/system-overviewweekly0.5https://ratiba.chat/docs/how-it-worksweekly0.5https://ratiba.chat/docs/how-it-works/admin-orchestratorweekly0.5https://ratiba.chat/docs/how-it-works/catalog-onboardingweekly0.5https://ratiba.chat/docs/how-it-works/channel-substrateweekly0.5https://ratiba.chat/docs/how-it-works/conversation-fsmweekly0.5https://ratiba.chat/docs/how-it-works/cross-sellweekly0.5https://ratiba.chat/docs/how-it-works/identity-and-tenancyweekly0.5https://ratiba.chat/docs/how-it-works/knowledge-answersweekly0.5https://ratiba.chat/docs/how-it-works/paymentsweekly0.5https://ratiba.chat/docs/how-it-works/personality-dialsweekly0.5https://ratiba.chat/docs/how-it-works/voice-conversationweekly0.5https://ratiba.chat/docs/methodology-appliedweekly0.5https://ratiba.chat/docs/methodology/weekly0.5https://ratiba.chat/docs/quickstartweekly0.5https://ratiba.chat/docs/quickstart/dev-setupweekly0.5https://ratiba.chat/docs/quickstart/first-bookingweekly0.5https://ratiba.chat/docs/quickstart/onboard-tenantweekly0.5https://ratiba.chat/docs/quickstart/seed-dataweekly0.5https://ratiba.chat/docs/referenceweekly0.5https://ratiba.chat/docs/reference/adrsweekly0.5https://ratiba.chat/docs/reference/apiweekly0.5https://ratiba.chat/docs/reference/configurationweekly0.5https://ratiba.chat/docs/reference/glossaryweekly0.5https://ratiba.chat/docs/reference/schemaweekly0.5https://ratiba.chat/docs/runbookweekly0.5https://ratiba.chat/docs/runbook/capacityweekly0.5https://ratiba.chat/docs/runbook/incident-responseweekly0.5https://ratiba.chat/docs/runbook/incidentsweekly0.5https://ratiba.chat/docs/runbook/local-devweekly0.5https://ratiba.chat/docs/runbook/observabilityweekly0.5https://ratiba.chat/docs/runbook/pilot-deploymentweekly0.5https://ratiba.chat/docs/runbook/testingweekly0.5https://ratiba.chat/methodology/weekly0.5https://ratiba.chat/methodology/agentic-developmentweekly0.5https://ratiba.chat/research/weekly0.5https://ratiba.chat/research/2026-04-25-agentic-landscape-2026weekly0.5https://ratiba.chat/research/2026-04-25-eval-frameworksweekly0.5https://ratiba.chat/research/2026-04-25-human-in-the-loop-handoffweekly0.5https://ratiba.chat/research/2026-04-25-langgraph-postgressaver-spikeweekly0.5https://ratiba.chat/research/2026-04-25-orchestration-patternsweekly0.5https://ratiba.chat/research/2026-04-25-payments-orchestrationweekly0.5https://ratiba.chat/s4u-methodology/appendix-a-testingweekly0.5https://ratiba.chat/s4u-methodology/appendix-b-uiuxweekly0.5https://ratiba.chat/s4u-methodology/appendix-c-agentsweekly0.5https://ratiba.chat/s4u-methodology/appendix-d-memoryweekly0.5https://ratiba.chat/s4u-methodology/appendix-e-hooksweekly0.5https://ratiba.chat/s4u-methodology/appendix-f-evidenceweekly0.5https://ratiba.chat/s4u-methodology/appendix-g-adrweekly0.5https://ratiba.chat/s4u-methodology/appendix-h-architecture-as-codeweekly0.5https://ratiba.chat/s4u-methodology/appendix-i-tool-selectionweekly0.5https://ratiba.chat/s4u-methodology/appendix-j-state-mdweekly0.5https://ratiba.chat/s4u-methodology/appendix-k-loop-dispatchweekly0.5https://ratiba.chat/s4u-methodology/appendix-l-product-scale-planningweekly0.5https://ratiba.chat/s4u-methodology/appendix-m-canonical-stackweekly0.5https://ratiba.chat/s4u-methodology/appendix-n-documentation-excellence-passesweekly0.5https://ratiba.chat/s4u-methodology/CHANGELOGweekly0.5https://ratiba.chat/s4u-methodology/evidence/automated-review-gatesweekly0.5https://ratiba.chat/s4u-methodology/evidence/automated-review-workflowsweekly0.5https://ratiba.chat/s4u-methodology/evidence/hook-architectureweekly0.5https://ratiba.chat/s4u-methodology/evidence/quality-gatesweekly0.5https://ratiba.chat/s4u-methodology/evidence/three-core-gates-optional-security-layerweekly0.5https://ratiba.chat/s4u-methodology/infrastructure/global-instructionsweekly0.5https://ratiba.chat/s4u-methodology/infrastructure/project-instructionsweekly0.5https://ratiba.chat/s4u-methodology/infrastructure/the-canonical-technology-stackweekly0.5https://ratiba.chat/s4u-methodology/infrastructure/the-instruction-hierarchyweekly0.5https://ratiba.chat/s4u-methodology/infrastructure/the-superpowers-skills-systemweekly0.5https://ratiba.chat/s4u-methodology/infrastructure/three-tier-architectureweekly0.5https://ratiba.chat/s4u-methodology/lifecycle/development-lifecycleweekly0.5https://ratiba.chat/s4u-methodology/lifecycle/lifecycle-integrationweekly0.5https://ratiba.chat/s4u-methodology/lifecycle/the-bug-fix-cycleweekly0.5https://ratiba.chat/s4u-methodology/lifecycle/the-code-review-cycleweekly0.5https://ratiba.chat/s4u-methodology/lifecycle/the-full-cycleweekly0.5https://ratiba.chat/s4u-methodology/lifecycle/the-incident-response-cycleweekly0.5https://ratiba.chat/s4u-methodology/operating-cardweekly0.5https://ratiba.chat/s4u-methodology/overviewweekly0.5https://ratiba.chat/s4u-methodology/philosophy/weekly0.5https://ratiba.chat/s4u-methodology/philosophy/consolidation-review-periodic-mechanism-backedweekly0.5https://ratiba.chat/s4u-methodology/philosophy/decision-cost-rubric-multi-dimensional-change-evaluationweekly0.5https://ratiba.chat/s4u-methodology/philosophy/design-before-codeweekly0.5https://ratiba.chat/s4u-methodology/philosophy/evidence-over-claimsweekly0.5https://ratiba.chat/s4u-methodology/philosophy/human-ai-collaboration-modelweekly0.5https://ratiba.chat/s4u-methodology/philosophy/investigative-disciplineweekly0.5https://ratiba.chat/s4u-methodology/philosophy/living-documentationweekly0.5https://ratiba.chat/s4u-methodology/philosophy/quality-as-architectureweekly0.5https://ratiba.chat/s4u-methodology/practices/architectureweekly0.5https://ratiba.chat/s4u-methodology/practices/model-selectionweekly0.5https://ratiba.chat/s4u-methodology/practices/notification-driven-self-paced-dispatch-the-loop-patternweekly0.5https://ratiba.chat/s4u-methodology/practices/product-scale-planning-cross-consistency-reviewweekly0.5https://ratiba.chat/s4u-methodology/practices/subagent-driven-developmentweekly0.5https://ratiba.chat/s4u-methodology/practices/the-agent-systemweekly0.5https://ratiba.chat/s4u-methodology/practices/the-four-project-reviewersweekly0.5https://ratiba.chat/s4u-methodology/purpose-and-scopeweekly0.5https://ratiba.chat/s4u-methodology/rule-inventoryweekly0.5https://ratiba.chat/s4u-methodology/section-10/architecture-decision-records-summaryweekly0.5https://ratiba.chat/s4u-methodology/section-11/documentation-principlesweekly0.5https://ratiba.chat/s4u-methodology/section-11/infrastructureweekly0.5https://ratiba.chat/s4u-methodology/section-11/living-documentation-practiceweekly0.5https://ratiba.chat/s4u-methodology/section-11/project-state-files-statemdweekly0.5https://ratiba.chat/s4u-methodology/section-11/the-ai-context-loopweekly0.5https://ratiba.chat/s4u-methodology/section-11/the-documentation-commit-patternweekly0.5https://ratiba.chat/s4u-methodology/section-11/what-gets-documentedweekly0.5https://ratiba.chat/s4u-methodology/section-12/regulatory-compliance-architecture-movedweekly0.5https://ratiba.chat/s4u-methodology/section-13/tool-ecosystemweekly0.5https://ratiba.chat/s4u-methodology/section-14/getting-startedweekly0.5https://ratiba.chat/s4u-methodology/section-14/operating-at-n1-developersweekly0.5https://ratiba.chat/s4u-methodology/section-15/permission-mode-tied-to-blast-radiusweekly0.5https://ratiba.chat/s4u-methodology/section-15/secret-hygieneweekly0.5https://ratiba.chat/s4u-methodology/section-15/securing-the-ai-collaboratorweekly0.5https://ratiba.chat/s4u-methodology/section-15/tool-mcp-least-privilege-provenanceweekly0.5https://ratiba.chat/s4u-methodology/section-15/untrusted-input-is-data-not-instructionsweekly0.5https://ratiba.chat/s4u-methodology/section-8/testing-standard-summaryweekly0.5https://ratiba.chat/s4u-methodology/section-9/uiux-standard-summaryweekly0.5https://ratiba.chat/s4u-methodology/showcaseweekly0.5https://ratiba.chat/s4u-methodology/standards/four-memory-typesweekly0.5https://ratiba.chat/s4u-methodology/standards/purposeweekly0.5https://ratiba.chat/s4u-methodology/standards/staleness-managementweekly0.5https://ratiba.chat/s4u-methodology/standards/the-memory-systemweekly0.5https://ratiba.chat/s4u-methodology/standards/what-not-to-saveweekly0.5https://ratiba.chat/weekly0.5