Product and technical planning for Garrison Bible Study. Published on the docs site under Developer → Planning (Architecture). Code layout and stack live in Architecture; everything else is organized by topic below.
| Document | What it covers |
|---|
| Vision | Problem, goals, curriculum philosophy, AI at a high level |
| Branding | Product name, taglines, store copy (open choices) |
| Product Scope | v1 vs later, tenant model, business model, roadmap |
| Architecture | Repos (api, ui, www, docs, mobile), GraphQL, frameworks, tooling |
| Document | What it covers |
|---|
| Onboarding | Signup, church linking, personality and habits |
| Identity and Access | Auth, trust tiers, households, roles (ABAC), church membership |
| Identity verification | ID + liveness for non-church users, church exemptions |
| Domain Model | Studies, study sessions, log entries, notes, habits, phases |
| Sync and Offline | CRDT note sync, mobile offline — implementation: Note CRDT sync |
| Study Methods | Book, topical, and word study templates |
| Study Plans | Plan templates, study steps, resolution at create |
| Learning outcomes | Outcome definitions, quizzes, per-study evaluations |
| Phase promotion | Track completion + checkup study before phase advance |
| Tracks | Ordered plan groups, funnel vs specialization, tags |
| Mentorship | Mentor–mentee pairs, participation modes, step note lanes |
| Motivation | Intrinsic/extrinsic motivation, streaks, gamification |
| Groups and Community | Groups, future forum, moderation, doctrine acceptance |
| Messaging | Mentor/mentee in-app chat (no SMS) |
| Bible and Scripture | Translations, Logos, self-hosted text, future in-app Bible |
| Document | What it covers |
|---|
| Integrations | ChMS, Logos, Canvas, exports, personality data |
| Files and Uploads | Presigned uploads, file IDs (post–v1) |
| AI Guidelines | Product AI, MCP, moderation, guardrails |
| Security and Privacy | Encryption, audit logs, deletion, church analytics |
| Deployment | SaaS vs self-host, Docker Compose, infrastructure |
| Foundational Doctrine | Non-negotiable doctrine (immutable) |
Scoped follow-up features (not open design questions): Planning backlog.
