LifePod OS

Version 1.0 — System Blueprint

A complete agentic operating system for community pods rooted in spiritual formation. Five autonomous agents coordinate spiritual growth, daily operations, generous contribution, systemic health, and transparent governance — all without extracting from the people they serve.

Five Pillars

Spiritual Formation

Anchor every workflow in liturgical rhythm, scripture engagement, and reflective practice. The system never optimizes for speed at the cost of depth.

Friction Removal

Automate logistics so leaders spend time on people, not spreadsheets. Scheduling, follow-ups, reminders, and reporting happen behind the scenes.

Community Impact

Track tangible outcomes: meals served, hours given, neighbors reached. Every action feeds a collective narrative of transformation.

Anti-Extraction

No data is sold. No attention is hijacked. Members own their data. Financial flows are transparent. The system serves the community, not the other way around.

Replication Scaling

Every pod that launches inherits the full operating system. Playbooks, templates, and agent configurations are portable across geography and denomination.

Agent Architecture

Each agent operates autonomously on its defined cadence but communicates through shared data events. Escalation paths flow from agent to leader to steward. No single agent holds authority — governance is distributed by design.

Formation Agent

Cultivate deep, sustained spiritual growth by guiding members through scripture engagement, reflective practice, liturgical rhythms, and formation milestones — never optimizing for speed over depth.

Responsibilities

Generate and distribute weekly scripture reading plans aligned with the liturgical calendar or pod-chosen curriculum
Prompt members to submit reflections after each gathering or reading cycle
Track individual and collective formation milestones (e.g., first reflection, 12-week streak, mentor pairing)
Surface formation insights to leaders without exposing private reflections
Coordinate spiritual direction pairings and accountability partnerships
Archive formation artifacts (journals, prayers, commitments) with member consent
Flag spiritual drift patterns (declining engagement, isolation signals) to the Health Agent

Inputs

Liturgical calendar dataScripture curriculum selectionsMember reflection submissionsAttendance records from Operations AgentGathering notes and themesPod leader formation priorities

Outputs

Weekly scripture plan (per pod)Reflection prompts (per gathering)Formation milestone badgesAggregate formation health scoreDrift risk flags (to Health Agent)Quarterly formation summary reports

Tools

Tool	Purpose
ScripturePlanGenerator	Builds reading plans from curriculum + liturgical calendar inputs
ReflectionCollector	Sends prompts, collects and stores reflection entries with encryption at rest
MilestoneTracker	Evaluates member activity against milestone criteria and awards badges
DriftDetector	Analyzes engagement decay patterns and emits risk signals
FormationReporter	Compiles aggregate (never individual) formation metrics into leader dashboards

Cadence

Weekly

Scripture plan distribution, reflection prompt dispatch

Monthly

Formation milestone evaluation, drift analysis

Quarterly

Formation summary report, curriculum rotation assessment

Triggers

New pod createdGathering completedMember joins podReflection submitted14-day engagement gap detectedLeader requests formation review

Escalation Path

Formation Agent auto-prompt>Pod Leader nudge notification>Movement Steward pastoral alert>Health Agent risk flag

Failure Modes

Failure Mode	Mitigation
Reflection fatigue — members stop submitting	Reduce prompt frequency, offer alternative formats (audio, one-word, image), surface to leader for pastoral follow-up
Curriculum misalignment — readings feel irrelevant	Enable leader override of auto-generated plans; collect feedback after each cycle; A/B test alternate curricula
Privacy breach — individual reflections exposed	Enforce encryption at rest, aggregate-only reporting, explicit consent for any sharing, audit logs on all read access
Drift detection false positive — flagging engaged members	Require multi-signal confirmation (attendance + reflection + contribution); allow members to self-report sabbatical mode

Operations Agent

Eliminate administrative friction so that pod leaders and members spend their time on relationships and mission — not logistics, scheduling, or chasing follow-ups.

Responsibilities

Schedule pod gatherings based on member availability and venue constraints
Send automated reminders (24h, 2h) with location, agenda, and any pre-read materials
Track attendance and generate presence/absence records per gathering
Assign and track tasks (setup, teardown, meals, childcare) with rotation fairness
Manage resource allocation (spaces, budgets, materials) across pods
Generate operational reports for leaders and stewards
Coordinate cross-pod logistics for movement-wide events

Inputs

Member availability preferencesVenue/space calendarTask roster historyPod budget allocationsLeader scheduling overridesEvent registrations

Outputs

Gathering invitations with calendar eventsTask assignments with rotation trackingAttendance records (per gathering)Resource utilization reportsOperational health dashboard dataCross-pod coordination briefs

Tools

Tool	Purpose
SchedulerEngine	Optimizes meeting times against member availability and venue constraints
ReminderDispatcher	Sends multi-channel reminders (SMS, email, push) on configurable cadences
AttendanceLogger	Records check-ins via QR, manual entry, or leader confirmation
TaskRotator	Assigns recurring tasks with fairness scoring to prevent burnout
ResourceAllocator	Tracks and distributes shared resources (rooms, budgets, supplies)
OpsReporter	Compiles operational metrics into leader and steward dashboards

Cadence

Weekly

Gathering scheduling, reminder dispatch, attendance logging

Monthly

Task rotation rebalancing, resource utilization review

Quarterly

Operational efficiency audit, cross-pod coordination planning

Triggers

Gathering scheduled24h before gathering2h before gatheringAttendance recordedTask not acknowledged within 48hResource conflict detectedNew member onboarding

Escalation Path

Operations Agent auto-resolve>Pod Leader manual override>Movement Steward resource arbitration>Financial Steward budget review

Failure Modes

Failure Mode	Mitigation
Scheduling deadlock — no time works for all members	Fall back to majority-available slot; notify excluded members with recording/catch-up plan; offer async participation
Task burnout — same members always assigned	Enforce fairness scoring with hard caps; surface imbalance to leader; enable opt-out periods
Reminder fatigue — members mute notifications	Allow per-member channel and frequency preferences; consolidate reminders; track open rates and adapt
Attendance data gaps — manual entry missed	Auto-flag missing attendance within 24h; enable retroactive entry by leader; cross-reference with task completion

Contribution Agent

Track, celebrate, and amplify every form of generosity — financial giving, volunteer hours, skills shared, meals prepared, neighbors served — building a living narrative of community impact.

Responsibilities

Record financial contributions with full transparency and categorization
Log volunteer hours and service activities with impact descriptions
Calculate and visualize impact metrics (meals served, hours given, families reached)
Generate contribution acknowledgments and tax-relevant summaries
Surface giving patterns to Financial Steward without exposing individual amounts to peers
Compile community impact narratives for quarterly storytelling
Detect contribution anomalies (sudden drops, unusual patterns) for Health Agent

Inputs

Financial transaction recordsVolunteer hour logsService activity reportsImpact measurement templatesMember consent preferencesBudget category definitions

Outputs

Contribution receipts and acknowledgmentsImpact dashboards (aggregate)Individual giving summaries (private, member-only access)Quarterly impact narrative reportsAnomaly flags (to Health Agent)Financial transparency reports (to Financial Steward)

Tools

Tool	Purpose
GivingLedger	Records and categorizes financial contributions with audit trail
ServiceLogger	Captures volunteer hours, skills offered, and service descriptions
ImpactCalculator	Aggregates raw contribution data into meaningful impact metrics
NarrativeCompiler	Transforms impact data into human-readable stories for community sharing
AnomalyDetector	Monitors contribution patterns for sudden drops or unusual spikes
ReceiptGenerator	Produces tax-ready contribution summaries per member

Cadence

Weekly

Contribution logging, service activity recording

Monthly

Impact metric compilation, anomaly analysis

Quarterly

Impact narrative report, financial transparency summary, tax receipt batch

Triggers

Financial contribution receivedVolunteer hours submittedService event completedMonth-end closeContribution anomaly detectedMember requests giving summary

Escalation Path

Contribution Agent auto-acknowledge>Pod Leader impact review>Financial Steward transparency audit>Movement Steward narrative approval

Failure Modes

Failure Mode	Mitigation
Giving pressure — system inadvertently shames non-givers	Never display individual amounts publicly; aggregate-only dashboards; celebrate all contribution types equally
Impact inflation — metrics misrepresent actual outcomes	Require verification for claimed impacts; use conservative counting methods; audit quarterly
Financial data breach — giving records exposed	Encrypt all financial data at rest and in transit; role-gated access; audit every read operation; member-only view of own records
Volunteer burnout — high hours signal exploitation	Cap recommended hours; surface high-hour members to leader; integrate with Health Agent vitality scoring

Health Agent

Continuously monitor the systemic health of each pod and the broader movement, detecting risk signals early, enforcing anti-extraction safeguards, and ensuring no person or pattern degrades the community's wellbeing.

Responsibilities

Compute pod vitality scores from attendance, formation, contribution, and relational signals
Detect and flag extraction patterns (financial, attentional, emotional, labor)
Monitor leader burnout indicators (task load, hours, sentiment)
Enforce data sovereignty: no member data sold, shared, or used for targeting
Run quarterly anti-extraction audits against defined safeguard criteria
Issue system-wide health alerts when multiple pods show correlated risk
Maintain the grievance and conflict signal pipeline to Governance Agent

Inputs

Attendance trends (from Operations Agent)Formation engagement scores (from Formation Agent)Contribution patterns (from Contribution Agent)Task load per member (from Operations Agent)Member feedback and sentiment signalsExternal risk indicators (e.g., economic stress data)

Outputs

Pod vitality scores (0-100)Risk alert notificationsAnti-extraction audit reportsLeader burnout flagsSystem-wide health dashboardGrievance signals (to Governance Agent)

Tools

Tool	Purpose
VitalityScorer	Computes weighted health scores from multi-agent input signals
ExtractionDetector	Pattern-matches against defined anti-extraction criteria across data streams
BurnoutMonitor	Tracks leader and high-contributor load metrics against safe thresholds
DataSovereigntyAuditor	Scans system logs for unauthorized data access, export, or sharing
HealthAlertDispatcher	Sends graduated alerts (info, warning, critical) to appropriate roles
GrievancePipeline	Routes conflict and concern signals to Governance Agent with anonymization

Cadence

Weekly

Vitality score update, burnout indicator check

Monthly

Extraction pattern analysis, system health dashboard refresh

Quarterly

Full anti-extraction audit, data sovereignty audit, movement health report

Triggers

Vitality score drops below 60Extraction pattern detectedLeader task load exceeds thresholdMember files grievanceData access anomaly detectedThree or more pods show correlated decline

Escalation Path

Health Agent auto-alert>Pod Leader pastoral intervention>Movement Steward systemic review>Governance Agent formal process

Failure Modes

Failure Mode	Mitigation
False alarm fatigue — too many low-severity alerts	Implement alert severity tiers; batch low-severity into weekly digest; allow leader acknowledgment to suppress repeats
Surveillance perception — members feel monitored	Publish exactly what signals are tracked; use aggregate-only metrics; allow members to see their own data; no individual scoring shared with peers
Extraction blind spot — novel pattern not in criteria	Quarterly criteria review with member input; open suggestion pipeline; Movement Steward can add new detection rules
Health Agent compromise — agent itself becomes extraction vector	Governance Agent audits Health Agent access logs quarterly; read-only access to raw data; no write access to member records

Governance Agent

Ensure transparent, accountable, and distributed governance across every pod and the movement — managing roles, permissions, decision-making, conflict resolution, leadership succession, and replication readiness.

Responsibilities

Manage role assignments and permission grants per the RBAC matrix
Facilitate pod-level voting and consensus processes for key decisions
Route and track conflict resolution workflows from intake to resolution
Monitor leadership succession readiness and surface apprenticeship opportunities
Enforce term limits and rotation schedules for leadership roles
Manage pod replication workflows: readiness assessment, template cloning, mentor pod pairing
Maintain the governance audit trail — every role change, vote, and decision is logged

Inputs

Role assignment requestsVote submissionsConflict/grievance signals (from Health Agent)Leadership tenure dataPod maturity indicatorsReplication readiness assessments

Outputs

Role assignment confirmationsVote results and decision recordsConflict resolution outcomesSuccession readiness reportsPod replication packagesGovernance audit trail exports

Tools

Tool	Purpose
RoleManager	Assigns, modifies, and revokes roles with full audit logging
VotingEngine	Facilitates asynchronous voting with configurable quorum and threshold rules
ConflictRouter	Intake, anonymize, assign mediator, and track resolution workflow
SuccessionTracker	Monitors leadership tenure, identifies apprenticeship candidates, generates succession plans
ReplicationEngine	Packages pod templates, agent configurations, and playbooks for new pod launches
AuditLogger	Immutable append-only log of all governance actions with timestamps and actor IDs

Cadence

Weekly

Role change processing, active conflict status updates

Monthly

Succession readiness review, governance metrics compilation

Quarterly

Term limit enforcement, replication readiness assessment, full governance audit

Triggers

Role change requestedVote initiatedGrievance received from Health AgentLeadership term limit approaching (90 days)Pod maturity score exceeds replication thresholdGovernance audit scheduled

Escalation Path

Governance Agent auto-process>Pod Leader mediation>Movement Steward arbitration>External mediator referral

Failure Modes

Failure Mode	Mitigation
Power consolidation — single leader accumulates roles	Enforce hard role caps per member; term limits with no self-extension; require multi-steward approval for exceptions
Vote manipulation — low quorum exploited	Minimum quorum thresholds (e.g., 60% of active members); extend voting window if quorum not met; void if still unmet
Conflict stagnation — resolution takes too long	Enforce SLA timelines per conflict severity; auto-escalate if timeline exceeded; external mediator pool available
Replication without readiness — immature pod clones	Multi-criteria maturity gate (6 months, vitality > 75, leader trained); mentor pod required for first 90 days

Operational Playbook

Formation Agent Instruction Set

The Formation Agent guides spiritual rhythm prompts, reflection capture, and personal growth accountability for a LifePod of 10-12 members co-led by three leaders. Every automation below is designed to nurture depth without becoming performative, and to sustain engagement without surveillance. The agent never evaluates spiritual quality, never punishes non-participation, and never exposes individual data to the group.

Weekly Formation Workflow

Sunday through Saturday cadence for a Wednesday gathering

Agent selects from the current formation track or weekly theme set by the pod leader.
Each member receives one scripture-based prompt and one non-scripture alternative based on their preference flag in the members table.
Prompts are delivered via the pod's primary channel (SMS, app push, or email) using the member's preferred_contact_method.
A row is inserted into reflections with status = 'pending' and prompt_sent_at = now().

Data Written

reflections.status -> 'pending'reflections.prompt_sent_at -> timestampreflections.prompt_type -> 'scripture' | 'non_scripture'

Formation Templates

Four templates structure the data collection touchpoints of the Formation Agent. Each template defines exact fields, types, and safeguards. All content fields that contain personal spiritual writing are encrypted at rest.

Message Scripts

Four automated messages anchor the weekly rhythm. Each script includes full body text with personalization tokens, channel routing logic, and fallback behavior for edge cases. Scripts are delivered at the member's local time using their timezone preference.

Gentle Follow-Up Protocol

Non-coercive re-engagement for members who withdraw

The follow-up protocol is designed around a single principle: people are not problems to be solved. Each escalation level reduces digital contact and increases pastoral, human presence. The system protects members from over-pursuit and never weaponizes absence data.

Member misses 1 reflection submission

Day after reflection deadline (Tuesday)Tone: Silent grace

Action

No outreach. Zero follow-up.

System Behavior

No message is sent. Missing one reflection is normal life. The system does nothing. The member's reflection row remains status = 'pending' and eventually moves to 'expired' after 7 days.

Escalation

None. This is not a signal.

Member misses 2 consecutive reflection submissions

Wednesday of the second missed week (after the gathering)Tone: Gentle, relational, zero guilt. No mention of 'missed' or 'behind.'

Action

A single, warm, non-transactional message from the Formation Agent

Script

Hey {first_name},

Just wanted you to know you're thought of. Life gets full sometimes, and that's okay.

If anything is weighing on you that the pod could help carry, we're here. No need to respond to this — it's just a hello.

With care,
{leader_first_name} on behalf of {pod_name}

Escalation

If the member responds with a concern, the message is routed to the member's primary leader for personal follow-up within 24 hours. If no response, no further action for 2 weeks.

Member misses 3 consecutive reflections AND 2 consecutive gatherings

After the third missed weekTone: Pastoral concern, not administrative alarm

Action

Leader is privately notified via the Health Agent dashboard (not a group announcement)

System Behavior

A private notification appears in the leader's dashboard: '{first_name} has been quiet for a few weeks — both in reflections and gatherings. This may be a season of withdrawal. Consider reaching out personally, not digitally.' No automated message is sent to the member at this stage.

Escalation

If the leader does not log a personal outreach action within 7 days, the Health Agent escalates to the Movement Steward as a pastoral care flag. The member is never contacted by the system again until they re-engage voluntarily.

Member has been inactive for 6+ weeks (no reflections, no attendance, no contributions)

After the sixth consecutive week of inactivityTone: Protective. The system guards against over-pursuit.

Action

Status moved to 'sabbatical' — member remains on the roster but all automated messages stop

System Behavior

No message is sent. The member's record is updated: members.status = 'sabbatical'. All Formation Agent, Operations Agent, and Contribution Agent automated messages are suppressed. The member can re-engage at any time by responding to any pod communication or opening the app, which triggers an automatic status change back to 'active' with a warm welcome-back message.

Escalation

At the quarterly review, sabbatical members are noted (count only, no names) in the pod health report. The Governance Agent tracks total sabbatical duration. If a member has been in sabbatical for 6+ months, the leader is prompted once to consider a personal letter (handwritten or otherwise non-digital).

Operational Playbook

Operations Agent Instruction Set

The Operations Agent manages the weekly, monthly, and quarterly operational cadence for a LifePod. It automates meeting logistics, attendance tracking, task accountability, and review packet generation so that leaders can focus on people rather than process. Every automation is designed to reduce friction, not create bureaucracy. The agent never generates busywork and omits empty sections automatically.

Operational Cadence

Weekly, monthly, and quarterly rhythms with exact timing and data writes

Weekly Cadence

Owner: Operations Agent (automated) + Lead Facilitator (approval)

Operations Agent pulls: (1) outstanding action items with status = 'open' or 'overdue' from the tasks table, (2) any unresolved friction requests from the tasks table where origin = 'friction_request', (3) wins submitted via the Formation Agent's Saturday nudge, (4) any Health Agent flags visible to leaders.
Agent assembles a draft agenda using the Weekly Agenda Template (see below) and populates each section with real data. Empty sections are omitted automatically — agendas are never padded.
Draft agenda is delivered to the lead facilitator (the leader whose role in the leaders table is 'facilitator' for this rotation) for review via the leader dashboard.
Facilitator can reorder items, add discussion topics, set time allocations, and approve. If no approval by T-24 hours, the draft auto-publishes as-is.
Approved agenda is posted to the pod communication channel and a copy is stored in meetings.agenda_snapshot as JSON.

Data Written

meetings.agenda_snapshot -> JSONmeetings.agenda_status -> 'draft' | 'approved' | 'auto_published'meetings.facilitator_id -> uuid (rotating leader)

Monthly Cadence

Owner: Operations Agent (automated) + Pod Leaders (review)

Operations Agent compiles the Monthly Review Packet by aggregating data from the past 4-5 weeks across all agent domains.
Packet includes: attendance trends (weekly rates + 4-week rolling average), reflection participation rates (submitted / total, no content), task completion rates (completed / assigned), contribution summary (hours + financial totals, no individual breakdown for members), friction request log (resolved / open / escalated), and any Health Agent alerts that were triggered.
The packet is formatted using the Monthly Review Packet Template and delivered to all three pod leaders via the leader dashboard.
Leaders hold a 30-minute async or sync review during the last week. They annotate the packet with observations, decisions, and carry-forward items. Annotations are stored in quarterly_reviews.leader_notes as JSON.
A condensed 'pod pulse' summary (3-5 bullet points, no individual data) is optionally shared with the pod at the leader's discretion.

Data Written

quarterly_reviews.type -> 'monthly_packet'quarterly_reviews.generated_at -> timestampquarterly_reviews.data_snapshot -> JSONquarterly_reviews.leader_notes -> JSON (after annotation)

Quarterly Cadence

Owner: Operations Agent (automated setup) + Movement Steward (facilitation)

Operations Agent generates the Quarterly Review Facilitation Template two weeks before the review date, pre-populated with 13 weeks of aggregated data.
The template includes six sections: Pod Health Score trend (13-week sparkline), Formation Index trends (individual, visible only to each member), Contribution and Impact summary (aggregate), Financial stewardship report (prepared by Financial Steward), Risk signals triggered and resolved, and Forward-looking goals for the next quarter.
The Movement Steward facilitates a 90-minute structured review using the template as a guide. The review is a conversation, not a report-out — members are invited to reflect on the pod's collective journey.
Post-review, the Movement Steward records: key decisions, quarterly goals, any structural changes (membership, meeting time, format), and individual formation milestone celebrations.
A final quarterly summary is archived in quarterly_reviews with type = 'quarterly_full' and becomes the baseline for the next quarter's comparison.

Data Written

quarterly_reviews.type -> 'quarterly_full'quarterly_reviews.quarter -> 'Q1_2026' etc.quarterly_reviews.data_snapshot -> JSON (13-week aggregate)quarterly_reviews.decisions -> JSON arrayquarterly_reviews.next_quarter_goals -> JSON array

Operational Templates

Five templates structure the operational lifecycle of a LifePod. Each template defines exact sections, data sources, and rendering logic. Templates are auto-populated from live pod data and empty sections are omitted to prevent information overload.

Automation Triggers

Five event-driven triggers power the Operations Agent. Each trigger specifies the exact condition, resulting action, data mutations, and failure handling. Triggers fire automatically and require no leader intervention unless an escalation is needed.

Channel Post Scripts

Two automated posts anchor the pod's communication channel each week. Both are fully templated with personalization tokens and adapt their formatting to the pod's channel type (Slack, WhatsApp, email, or in-app).

Meeting Notes Structure

Exact schema for recording decisions, owners, due dates, and next steps

Meeting notes are the operational memory of the pod. Every note record follows a strict schema that ensures decisions are traceable, action items are extractable, and private pastoral observations remain encrypted and leader-only. The Operations Agent parses these fields to generate tasks, channel posts, and review packets.

Field	Type	Req	Description
meeting_id	uuid (auto-linked)	Yes	Foreign key to the meetings table. Auto-populated when notes are created within the meeting context.
recorded_by	uuid (leader_id)	Yes	The leader who captured the notes. Defaults to the meeting facilitator but can be reassigned to any of the three co-leaders.
opening_notes	text (0-1000 chars)	No	Free-text notes from the opening segment. Captures the overall energy, any wins shared, and the opening question or prompt used.
discussion_summary	text (0-2000 chars)	Yes	Summary of the main discussion. Captures key themes, tensions, insights, and questions raised. Never records specific member attributions unless the member requests it.
decisions	JSON array of { decision: string, context: string }	No	Formal decisions made by the pod. Each decision includes the decision text and brief context for why it was made. Decisions are surfaced in the monthly review packet.
action_items	JSON array of { description, owner_id, due_date, priority, context }	No	Structured action items captured during the meeting. Each becomes a row in the tasks table post-meeting. Owner must be a current active member of the pod.
friction_raised	JSON array of { type, summary, anonymous }	No	Friction points raised during the meeting that need follow-up. Each is routed to the appropriate agent (Operations for logistical, Formation for spiritual, Health for relational).
commitment_count	integer	Yes	Number of members who indicated they would set a commitment during the commitment time. Does not track the content — that is captured post-meeting by the Formation Agent.
closing_notes	text (0-500 chars)	No	Brief notes from the closing: prayer requests mentioned (no details logged, just count), logistics announcements, and any schedule changes for upcoming gatherings.
next_steps	JSON array of strings	No	High-level next steps that are not formal action items but orient the pod for the coming week. These appear in the weekly channel post.
leader_private_notes	text (encrypted, 0-1000 chars)	No	Private notes visible only to the three co-leaders. Used for pastoral observations, concerns about specific members, or sensitive topics that need follow-up but should not be in the shared record.

Example Values

meeting_id

a3f8b2c1-4d5e-6f7a-8b9c-0d1e2f3a4b5c

recorded_by

Leader: Marcus Thompson

opening_notes

Opened with wins from last week. Three members shared. Energy was warm and grateful. Used opening question #14: 'Where did you see beauty this week?'

discussion_summary

Discussion centered on navigating workplace pressure while maintaining spiritual practices. Key tension: how to be present at work without losing formation rhythms. Several members shared creative solutions.

decisions

[{ "decision": "Move meeting time to 7:30 PM starting next week", "context": "Three members have childcare conflicts at 7:00 PM" }]

action_items

[{ "description": "Research community garden partnership", "owner_id": "uuid", "due_date": "2026-03-15", "priority": "medium", "context": "Discussed during the service initiative brainstorm" }]

friction_raised

[{ "type": "logistical", "summary": "Need childcare solution for Wednesday evenings", "anonymous": false }]

commitment_count

closing_notes

Three prayer requests shared. Announced that next week's meeting will be at the park instead of the usual location. Facilitator handoff to Sarah for next week.

next_steps

["Continue reflecting on the James passage", "Bring ideas for the community service project to next meeting"]

leader_private_notes

Marcus seemed withdrawn tonight. May be connected to his job situation. Sarah will check in privately this week.

Contribution Playbook

Contribution Agent Instruction Set

The Contribution Agent ensures every form of giving is visible, balanced, and sustainable. It tracks six categories of contribution, computes balance across the pod, flags over-concentration before burnout sets in, and enforces structural safeguards against hero culture and labor extraction. The system exists to protect people, not to measure productivity. Every metric serves dignity, every automation preserves agency, and every alert is framed as care.

Contribution Categories

Six categories weighted equally in dignity, differentiated in measurement

Every contribution falls into one of six categories. The categories are not hierarchical. A text of encouragement (care work) carries the same systemic weight as a 3-hour initiative build (hours of service). The weight percentages in the Contribution Index reflect measurement methodology, not value.

Contribution Templates

Five templates structure how contributions are logged, initiatives are chartered, impact is reported, beneficiary feedback is collected, and burnout risk is assessed. Every template includes strict privacy rules that govern who sees what — the most sensitive data is always the most protected.

Automation Scripts

Four scripts: collect, compute, flag, and redistribute

The Contribution Agent runs four interconnected automation scripts each week. They form a chain: collection feeds computation, computation feeds flagging, and flagging feeds redistribution suggestions. Each script specifies exact triggers, data reads, data writes, output examples, and failure modes.

Anti-Hero Culture Rules

Structural safeguards that prevent extraction, competition, and burnout

Hero culture is the single greatest threat to sustainable community. It concentrates labor, creates dependency, burns out the most generous members, and makes everyone else feel inadequate. These six rules are structural, not aspirational. They are enforced by the system, not left to good intentions.

Low-Capacity Season Protections

Three tiers: self-declared, system-detected, and life-event sabbatical

People have seasons. Capacity fluctuates. A system that does not account for this will inevitably punish the vulnerable. These three protection tiers ensure that every member can step back without shame, without bureaucracy, and without losing their place in the community. The system adapts to the person — never the reverse.

Governance Playbook

Governance Agent Instruction Set

The Governance Agent ensures transparency, fairness, and anti-extraction compliance across all financial and decision-making activities. It enforces the LifePod financial split model (40/20/20/10/10), caps individual distributions, protects intellectual property defaults, requires consent for monetization, enforces leadership rotation, and maintains an immutable audit trail. Every rule exists to prevent the concentration of funds or power in any single individual or group.

Financial Split Model

40% Reinvest / 20% Movement / 20% Contributors / 10% Ops / 10% Care

Allocation Visualization

40%

20%

10%

Reinvest in Impact Movement Fund Contributor Distributions Ops Infrastructure Care Fund

Every dollar that enters the pod is immediately allocated according to this model. The split is non-negotiable at the category level — individual amounts within categories are flexible, but the percentages are structural. Variance of plus or minus 2% per category is tolerable; beyond that, the Governance Agent flags a compliance issue. Each allocation below expands to show its full rules, examples, and audit cadence.

Governance Rules

Distribution caps, IP defaults, consent, rotation, audit

Five structural rules form the anti-extraction backbone of LifePod governance. Each rule has explicit implementation details, enforcement mechanisms, and defined consequences for failure. These rules are not guidelines — they are hard constraints that the Governance Agent enforces algorithmically wherever possible and procedurally where human judgment is required.

Governance Templates

Five templates structure the documentation of financial stewardship, distribution approvals, IP and monetization consent, quarterly governance health checks, and Care Fund requests. Each template specifies every field with type, requirement level, description, and example value. Privacy rules and retention policies are attached to every template — the most sensitive data gets the strongest protections.

Automated Governance Checks

Four automated systems flagging concentration of funds or power

The Governance Agent runs four automated checks at defined intervals. Each check reads specific data tables, applies algorithmic detection logic, writes alerts and audit log entries, and defines explicit response protocols. These checks are the system's immune response — they detect early signs of extraction, entrenchment, or compliance drift before they become structural problems.

Security + Trust

RBAC and Privacy-by-Design

Privacy is not a feature of LifePod OS — it is a foundation. Every access decision starts from zero permissions and adds only what the role requires. Every data point has an owner. Every query is scoped. Every export is logged. This section defines the complete access control model, the Trust Contract that governs data use, the retention policy that limits data lifespan, and the anonymization approach that protects individuals in movement-wide analytics.

Per-Dataset CRUD Permissions

View, edit, export, and delete access for every role across every dataset

Ownown

Pod Aggpod agg

Pod Allpod all

Mvmt Aggmovement agg

Mvmt Allmovement all

Nonenone

Data Visibility Tiers

Private to member, visible to leaders, aggregated to movement

Private to Member

Data that belongs solely to the individual. No leader, steward, or system process ever accesses it in identifiable form. The member controls creation, viewing, editing, export, and deletion. The system may read aggregate completion rates (e.g., 'did they submit a reflection this week?') but never content.

Datasets in this tier

Reflection text content
Personal growth goal details
Friction removal request narratives
Private journal entries
Burnout self-assessment text

Who Sees: Only the member who created it. Ever.

Visible to Pod Leaders

Data that leaders can see for operational purposes within their own pod. Leaders can see individual records for attendance and task assignment, but only aggregate data for reflections and financial contributions. Access is scoped to their pod only — a leader of Pod A cannot see Pod B's data.

Datasets in this tier

Attendance records (per-member)
Task assignments and completion
Service hours (per-member)
Formation milestone status (achieved/not)
Member engagement status (present/drifting/absent)

Who Sees: Pod leaders for their pod only. Never cross-pod.

Aggregated to Movement Level

Data that movement stewards and financial stewards see as statistical summaries only. Individual identity is removed and replaced with cohort-level metrics. A steward might see 'Pod Alpha has 82% attendance this quarter' but never 'James missed 3 meetings.' The single exception: financial stewards can see individual financial contributions for tax receipt and compliance purposes, governed by regulatory requirements.

Datasets in this tier

Pod health scores
Attendance rate trends (per-pod)
Contribution totals (per-pod)
Impact metrics (per-initiative)
Burnout risk counts (per-pod, not per-person)

Who Sees: Movement stewards (governance + operations), financial stewards (finances only).

Trust Contract

What is tracked, why, and how it will never be used

Preamble

This Trust Contract is a binding commitment between LifePod OS and every member who entrusts their data to this system. It is not legal fine print — it is a covenant. Every person who submits a reflection, logs a contribution, or shares their presence in a gathering is extending trust. This contract exists to honor that trust explicitly, permanently, and without exception.

Signature Requirement

Every member signs this Trust Contract digitally upon joining a pod. The signed version is stored in the governance_log with a timestamp and contract version hash. Members are re-prompted to review and re-sign whenever the contract is amended.

Data Retention Policy

Minimal retention by category, lifecycle stage, and legal requirements

Data Category	Active Member	After Departure	After Deletion Request	Legal Hold
Reflections (text content)	Retained indefinitely while active. Member can delete any time.	Retained 90 days post-departure for member retrieval, then auto-deleted.	Deleted within 72 hours of request. No recovery.	Not subject to legal hold. Spiritual content is never retained for compliance.
Attendance records	Retained indefinitely while active.	Anonymized after 90 days. Converted to pod-level aggregate counts.	Individual records deleted within 72 hours. Aggregates persist anonymized.	May be retained if subpoenaed. Member notified within 48 hours.
Financial contributions	Retained for 7 years (tax compliance requirement).	Retained for 7 years from last contribution date (regulatory minimum).	Personal identifiers removed within 72 hours. Transaction amounts retained anonymized for 7 years for audit compliance.	Subject to regulatory retention. Member notified of any legal hold.
Service hours + tasks	Retained indefinitely while active.	Anonymized after 90 days.	Deleted within 72 hours. Pod-level aggregate impact totals persist anonymized.	Not subject to legal hold unless part of a liability inquiry.
Health alerts + risk signals	Retained for 12 months rolling. Older alerts auto-archived and anonymized.	Deleted immediately upon departure. No retention period.	Deleted within 72 hours. No recovery.	Never retained under legal hold. Health data is ephemeral by design.
Governance logs + audit trails	Retained indefinitely (immutable append-only log).	Member's name in governance logs replaced with anonymized ID after 90 days.	Governance actions persist with anonymized author ID. Member identity removed.	Subject to regulatory retention. Immutable by design.

Anonymized Movement Analytics

How movement-wide metrics are computed without exposing individual identity

Formation Engagement RateMin cohort: 5

Aggregation: Per-pod (minimum 5 members)

Anonymization Method

Count of submissions / count of active members. No individual identification. Pods with fewer than 5 members are excluded from cross-pod comparisons.

Output Example

Pod Alpha: 78% reflection submission rate this quarter

Prohibited Use

Never displayed per-member. Never used to rank members. Never used to determine distribution eligibility.

Attendance Stability IndexMin cohort: 5

Aggregation: Per-pod (minimum 5 members)

Anonymization Method

Rolling 12-week average attendance percentage. Individual attendance is visible only to the member and their pod leader. Cross-pod reports use pod-level aggregates only.

Output Example

Movement-wide attendance stability: 85% (17 pods reporting)

Prohibited Use

Never used to shame absent members. Never displayed as a leaderboard. Never tied to financial outcomes.

Contribution Balance (Gini Coefficient)Min cohort: 5

Aggregation: Per-pod

Anonymization Method

Statistical dispersion calculated from service hour distribution. Output is a single number (0.0 = perfect equality, 1.0 = total concentration). Individual hours are inputs but never appear in the output.

Output Example

Pod Beta: Gini = 0.32 (healthy range)

Prohibited Use

Never identifies the concentrated contributor. Never displayed with member names. Intervention scripts address the pod, not the individual.

Community Impact ReachMin cohort: 1

Aggregation: Per-initiative, per-pod, per-movement

Anonymization Method

Aggregate beneficiary counts, volunteer hours, and output metrics. Beneficiary feedback is anonymized at collection. No personally identifiable information about beneficiaries is stored.

Output Example

Movement total: 340 people served, 1,280 volunteer hours, 12 active initiatives

Prohibited Use

Never used to rank pods against each other. Impact narrative is collaborative, not competitive.

Financial Health SummaryMin cohort: 5

Aggregation: Per-pod, per-movement

Anonymization Method

Aggregate inflows, allocations by category, and distribution totals. Individual giving amounts never appear in movement-level reports. HHI (Herfindahl-Hirschman Index) concentration metric uses anonymized inputs.

Output Example

Pod Gamma: $12,400 quarterly inflow, HHI = 1,800 (within healthy range)

Prohibited Use

Never reveals individual donor amounts in pod-level or movement-level views. Financial Steward access to individual records is logged and auditable.

Leadership Rotation ComplianceMin cohort: 1

Aggregation: Per-pod, per-movement

Anonymization Method

Binary compliance flag (compliant/overdue) and tenure-in-months for current leaders. Names are visible only in governance logs, not in cross-pod reports.

Output Example

14 of 17 pods compliant. 3 pods have leaders at 11+ months tenure (review due).

Prohibited Use

Never used to publicly call out specific leaders. Rotation reminders are private to the pod's leadership team.

Analytics Product Spec

Dashboard Builder Spec

Six purpose-built dashboard pages, each with complete layout specifications, KPI tile definitions (data source, calculation, refresh cadence, format), trend graph configurations (chart type, axes, drill-downs), data table structures (columns, sorts, filters, row actions), page-level filters, and explicit drill-down navigation paths. Every widget is constrained by role-based access control — no widget renders data the viewer is not authorized to see.

Pod Health Overview

Pod LeaderMovement Steward

5 KPIs2 graphs2 tables

Contribution Balance

Pod LeaderMovement Steward

4 KPIs2 graphs1 tables

Attendance Stability

Pod Leader

4 KPIs2 graphs1 tables

Community Impact Outcomes

Pod LeaderMovement Steward

4 KPIs1 graphs2 tables

Financial Stewardship

Financial StewardMovement Steward (read-only)

5 KPIs2 graphs2 tables

Leader Rotation Compliance

Movement Steward

4 KPIs1 graphs1 tables

Accountability Framework

Metrics and Indices

Six composite indices measure the multi-dimensional health of every pod and its members. Each index is computed from observable, auditable data inputs with explicit formulas. No black-box scoring. Every member can see how their own score is calculated. Leaders see only aggregates. The Pod Health Score synthesizes all five sub-indices into one vitality number.

PHS

Pod Health Score

Master composite — equal weight across all dimensions

PHS = (0.2 * PFI_avg) + (0.2 * CI_avg) + (0.2 * CII) + (0.2 * RSI) + (0.2 * SI)

The Pod Health Score is the master composite metric that synthesizes all five sub-indices into a single vitality number for each pod. PFI and CI are averaged across all active pod members to produce pod-level scores. CII, RSI, and SI are already pod-level metrics. All five indices are equally weighted at 20% each, reflecting the conviction that no single dimension of community health should dominate. The Pod Health Score is the primary input to the Health Agent's VitalityScorer tool and drives the traffic-light status displayed on all dashboards.

Thriving75 - 100

Watch50 - 74

At Risk25 - 49

Critical0 - 24

Measures the depth and consistency of an individual member's spiritual formation journey. This index tracks whether a member is actively engaging with scripture, submitting reflections, progressing through milestones, interacting with mentors or accountability partners, and maintaining consistent formation habits over time. The index is private to each member and is never shared with peers. Leaders receive only aggregate pod-level formation data.

Formula

PFI = (0.3 * ReflectionRate) + (0.25 * ScriptureEngagement) + (0.2 * MilestoneProgress) + (0.15 * MentorInteraction) + (0.1 * FormationStreak)

Input Definitions

ReflectionRate: Reflections submitted in period / expected reflections (0-1 ratio)
ScriptureEngagement: Completed readings / assigned readings (0-1 ratio)
MilestoneProgress: Milestones achieved / milestones available at tenure stage (0-1 ratio)
MentorInteraction: Mentor sessions attended / scheduled sessions (0-1 ratio)
FormationStreak: Consecutive weeks with at least one formation activity / 12 (capped at 1.0)

State	Label	Range
Healthy	Flourishing	75 - 100
Watch	Plateauing	50 - 74
Risk	Drifting	25 - 49
Critical	Disengaged	0 - 24

Risk Signal Definitions

Six defined risk signals provide early warning when pod health degrades. Each signal has explicit detection logic, threshold criteria, data inputs, and graduated response protocols. The Health Agent evaluates these continuously and emits alerts when thresholds are breached. Signals are never punitive — they exist to enable pastoral care before crises deepen.

Detects when a member or pod's attendance rate drops below historical norms, signaling possible disengagement, relational friction, or life crisis.

Detection Method

Rolling 4-week attendance average compared to member's 12-week baseline. Pod-level detection uses aggregate attendance rate compared to 3-month moving average.

Threshold Logic

Member-level: If 4-week average drops more than 30% below 12-week baseline, emit warning. If 3 consecutive absences without excused status, emit critical. Pod-level: If aggregate attendance drops below 65%, emit warning; below 50%, emit critical.

Response Protocol

Warning: Operations Agent sends check-in prompt. Critical: Pod Leader receives pastoral alert with context. If unresolved after 14 days, Movement Steward notified.

Data Inputs

attendance.statusgatherings.scheduled_atmembers.status

17 Entity Tables

Full Entity Schema

Complete table definitions for every entity in the LifePod OS data model. Each field includes its data type, whether it is required or optional, a realistic example value, and a description of its purpose. Tables are grouped by their primary owning agent. All UUIDs are v4 auto-generated. All timestamps are stored in UTC with timezone (TIMESTAMPTZ). Encrypted fields use AES-256-GCM with per-member key derivation.

Tables

189

Total Fields

152

Required Fields

Optional Fields

Atomic unit of the LifePod movement. Every member belongs to exactly one pod. Pods are the organizational boundary for data access, financial accounting, and governance.

Field	Type	Required	Example	Description
id	UUID	Required	a1b2c3d4-e5f6-7890-abcd-ef1234567890	Primary key, auto-generated
name	VARCHAR(120)	Required	Eastside Commons	Human-readable pod name
region	VARCHAR(80)	Optional	Southeast Atlanta	Geographic region or city
denomination	VARCHAR(60)	Optional	Non-denominational	Affiliated tradition if any
parent_pod_id	UUID FK	Optional	f9e8d7c6-b5a4-3210-fedc-ba0987654321	References pods.id for replicated pods
maturity_score	SMALLINT	Required	72	0-100 replication readiness score
vitality_score	SMALLINT	Required	85	0-100 health score from Health Agent
member_count	SMALLINT	Required	14	Current active member count
status	ENUM	Required	active	forming \| active \| multiplying \| dormant
launched_at	TIMESTAMPTZ	Required	2024-09-15T00:00:00Z	Date the pod officially launched
created_at	TIMESTAMPTZ	Required	2024-08-01T10:30:00Z	Record creation timestamp
updated_at	TIMESTAMPTZ	Required	2025-01-10T14:22:00Z	Last modification timestamp

Data Schema

Twelve interconnected tables form the data backbone of LifePod OS. Each table is owned by a primary agent but may be read by others per the access control matrix. All timestamps are stored in UTC. Encrypted fields use AES-256-GCM with per-member keys.

Field	Type	Nullable	Description
id	UUID	No	Primary key
full_name	TEXT	No	Display name
email	TEXT	No	Unique login email
phone	TEXT	Yes	SMS contact number
role	ENUM	No	Member \| Leader \| Movement Steward \| Financial Steward
pod_id	UUID FK	No	References pods.id
joined_at	TIMESTAMPTZ	No	Date member joined the pod
status	ENUM	No	active \| sabbatical \| alumni \| removed
notification_prefs	JSONB	Yes	Channel and frequency preferences
consent_flags	JSONB	No	Granular consent for data sharing
created_at	TIMESTAMPTZ	No	Record creation timestamp
updated_at	TIMESTAMPTZ	No	Last update timestamp

Role-Based Access Control

Four roles govern all access across LifePod OS. Permissions are enforced at the API layer and audited by the Governance Agent. No role can self-elevate. The principle of least privilege applies everywhere: members see only their own data, leaders see their pod, stewards see the movement — and no one sees more than their responsibilities require.

Role Definitions

Member

Default role for all pod participants. Can view and manage their own data, submit reflections, log service hours, and view aggregate pod metrics. Cannot access other members' private data or administrative functions.

Leader

Appointed facilitator of a specific pod. Can manage gatherings, assign tasks, view aggregate formation and contribution data, access risk alerts for their pod, and manage member roster. Cannot view individual financial contributions or modify governance rules.

Movement Steward

Cross-pod administrative role responsible for movement-wide health, governance, replication, and anti-extraction enforcement. Full read access across all non-financial individual data. Can configure agents, manage replication, and arbitrate conflicts.

Financial Steward

Dedicated financial oversight role with access to contribution records, budgets, and financial audit trails. Can view individual giving records for receipt generation and compliance. Cannot modify governance rules or access private reflections.

Permission Matrix

Dataset	Member	Leader	Movement Steward	Financial Steward
members (own profile)	Read Own	Read All	Read All	Read Own
members (all profiles)	No Access	Read All	Full Admin	Read All
pods	Read Own	Read All	Full Admin	Read All
gatherings	Read Own	Write All	Read All	Read Own
attendance	Read Own	Write All	Read All	No Access
reflections (own)	Write Own	No Access	No Access	No Access
reflections (aggregate)	No Access	Read Aggregate	Read Aggregate	No Access
tasks	Read Own	Write All	Read All	No Access
contributions (own)	Read Own	No Access	No Access	Read All
contributions (aggregate)	No Access	Read Aggregate	Read Aggregate	Read All
service_activities	Write Own	Write All	Read All	Read All
finances	No Access	Read All	Read All	Full Admin
risk_signals	No Access	Read All	Full Admin	Read Own
formation_milestones	Read Own	Read All	Read All	No Access
governance_log	Read Own	Read All	Full Admin	Read All

Dashboard Views by Role

Member

My Formation: personal reflections, milestones, current scripture plan
My Attendance: personal gathering history, upcoming schedule
My Contributions: personal giving summary, volunteer hours, tax receipts
My Tasks: assigned tasks, upcoming duties, rotation schedule
Pod Overview: aggregate pod health score, upcoming events, impact highlights

Leader

Pod Dashboard: vitality score, attendance trends, formation engagement rates
Operations Console: scheduling, task assignment, resource allocation
Formation Overview: aggregate reflection rates, milestone distribution, drift alerts
Impact Summary: aggregate contributions, service hours, people served
Risk Alerts: active risk signals, burnout indicators, pending escalations
Member Roster: member status, role assignments, contact info

Movement Steward

Movement Dashboard: all pod vitality scores, cross-pod trends, system-wide health
Governance Console: role changes, active votes, conflict pipeline, succession tracker
Replication Hub: pod maturity scores, replication readiness, template management
Anti-Extraction Audit: data sovereignty status, extraction detection results
Impact Narrative: movement-wide impact metrics, stories, quarterly reports
System Administration: agent configuration, cadence overrides, alert thresholds

Financial Steward

Financial Dashboard: income/expense by pod, budget utilization, fund allocation
Contribution Oversight: giving trends (aggregate + individual where authorized), anomaly alerts
Transparency Reports: quarterly financial summaries, audit trail, compliance status
Tax Administration: receipt generation, year-end summaries, regulatory compliance

Dashboard Roll-Up Spec

Each role receives a tailored dashboard showing only the data they are authorized to see. Dashboards are composed of widgets, each pulling from specific data sources at defined refresh cadences. The principle of least privilege governs every view: members see themselves, leaders see their pod, stewards see the movement — nothing more.

Member5 widgets

Personal-only view. Members see their own formation journey, attendance history, contribution receipts, task assignments, and their pod's aggregate health. No access to other members' individual data.

Widget	Data Source	Refresh	Metrics Displayed
My Formation Journey	reflections, formation_milestones, commitments	Real-time on submission	Personal Formation Index (PFI) Current streak length Milestones achieved Active commitments
My Attendance	attendance, meetings	After each meeting	Attendance rate (rolling 12 weeks) Upcoming meetings Excused absence count
My Giving Summary	contributions	Real-time on contribution	YTD giving total Contribution history Downloadable tax receipt Recurring gift status
My Service	service_activities (own), tasks (own)	After each activity	Contribution Index (CI) Hours logged this quarter Upcoming task assignments Service types completed
Pod Pulse	pods, quarterly_reviews (aggregate only)	Weekly	Pod Health Score (aggregate) Upcoming events Impact highlights (aggregate) Member count

Leader6 widgets

Pod-scoped operational view. Leaders see aggregate formation and contribution data for their pod, manage gatherings and task assignments, monitor risk alerts, and track member engagement without seeing individual financial amounts.

Widget	Data Source	Refresh	Metrics Displayed
Pod Vitality Dashboard	pods, quarterly_reviews, alerts	Daily	Pod Health Score (current + trend) Sub-index breakdown (PFI avg, CI avg, CII, RSI, SI) Active alerts count by severity Quarter-over-quarter trend
Operations Console	meetings, tasks, attendance	Real-time	Upcoming meetings with RSVP counts Task assignment board Fairness score distribution Attendance rate (aggregate + per-member)
Formation Overview	reflections (aggregate), formation_milestones, commitments (aggregate)	Weekly	Reflection submission rate Milestone distribution chart Active drift alerts Commitment completion rate (aggregate)
Impact Summary	service_activities (aggregate), initiatives, beneficiaries (aggregate)	Weekly	Community Impact Index People served this quarter Total volunteer hours Active initiatives status
Risk Monitor	alerts, interventions, risk_signals	Real-time	Open alerts by type Intervention status tracker Burnout risk indicators Relational Strength Index
Member Roster	members, attendance (aggregate per member)	Real-time	Active/sabbatical/alumni count Role assignments Engagement status (present/drifting/absent) New member integration status

Movement Steward6 widgets

Cross-pod movement-wide view. Stewards see all pod vitality scores, governance activity, replication readiness, anti-extraction audit results, and system-wide health trends. They can configure agent behavior and manage the replication pipeline.

Widget	Data Source	Refresh	Metrics Displayed
Movement Health Map	pods (all), quarterly_reviews (all), alerts (all)	Daily	All pod vitality scores (sortable, filterable) System-wide health trend Correlated decline detection Movement-wide Pod Health Score average
Governance Console	governance_log, leaders, members (role data)	Real-time	Active votes and results Role change history Conflict pipeline status Leadership tenure tracker
Replication Hub	pods (maturity_score), leaders (training_milestones)	Monthly	Pods at replication threshold Mentor pod pairings Template readiness status New pod pipeline
Anti-Extraction Audit	alerts (extraction type), governance_log (audit actions)	Quarterly (with ad-hoc triggers)	Data sovereignty compliance Extraction pattern detection results Financial concentration alerts Leadership dominance indicators
Impact Narrative	service_activities (all), beneficiaries (all), initiatives (all)	Quarterly	Movement-wide people served Total volunteer hours Initiative completion rate Story highlights for communications
System Configuration	Agent configurations, cadence schedules, threshold settings	On change	Agent cadence overrides Alert threshold configuration Detection rule management System audit log

Financial Steward4 widgets

Financial oversight view. Financial Stewards see all income, expenses, allocations, distributions, and individual contribution records (for receipt and compliance purposes). They cannot access reflections, governance rules, or formation data.

Widget	Data Source	Refresh	Metrics Displayed
Financial Dashboard	financial_inflows, financial_allocations, distributions	Daily	Income vs. expense by pod Budget utilization rate Cash position Stewardship Index (SI)
Contribution Oversight	contributions (all), alerts (financial type)	Weekly	Giving trends (aggregate + individual where authorized) Recurring gift health Financial concentration alerts (HHI) Donor retention rate
Transparency Reports	financial_inflows, distributions, quarterly_reviews	Quarterly	Quarterly financial summary Allocation vs. actual spending Audit trail completeness Compliance status
Tax Administration	contributions (individual, authorized access)	On demand + year-end batch	Receipt generation queue Year-end summary generation Regulatory compliance checklist Giving history per member (authorized)