BYOK Intelligence Layer
Helpful AI without adl.church becoming a token reseller.
The product direction stays simple: users can connect their own provider key, adl.church keeps those secrets server-side, and every AI action runs over structured platform data with permission-aware scope.
Supported providers
OpenAI, Anthropic, Google AI
Security posture
Encrypted secret storage, server-side execution, and audit trails for every AI run.
Product intent
AI is for briefings, comparisons, and insight over records, not a blank ungrounded chatbot.
Initial AI Actions
These are the first workflows worth building because they directly help pastors, denominational leaders, and church planters.
Runtime Rules
The AI path is already mirrored in the database migrations, so this page acts as the product contract for the next implementation pass.
Provider secrets never ship to the browser.
AI should only see the records the current user is allowed to access.
Every run should log provider, model, user, record scope, and usage metadata.
Suggested edits should stay reviewable until a human approves them.