What Is a Community Trust Hub?
A Community Trust Hub is a local church, community group, or partner organisation that plays a specific role in the WSI/CES Community Cloud platform:
- Democratic governance anchor — helping govern how community programs work, what evidence is collected, and how decisions are made locally.
- Community intelligence contributor — participating in program design and contributing anonymised, consent-based signals to the community intelligence layer.
- CES readiness partner — preparing for future community exchange (time banking, mutual aid) when governance gates are formally met.
- SDG 11 evidence node — contributing to sustainable community evidence aligned with the UN Sustainable Development Goals framework (SDG 11/16/17).
WSI/CES is not asking churches to become technology operators. The platform is designed so that a local church can participate at whatever level fits their capacity — from simply informing their community about available programs, to eventually helping govern how exchange resources are allocated locally.
Biblical AI Governance Principle
WSI/CES operates under a biblical AI governance principle: AI and digital systems are servant instruments, not masters. They are created tools that may support stewardship, justice, mercy, truth, accountability, and protection of the vulnerable — but they must never replace:
- God's authority
- human conscience and pastoral discernment
- community accountability and consent
- protection of vulnerable people
- Founder review where required
Community Trust Hubs participate in a human-led governance model. AI and digital systems assist with organisation and evidence — they do not make decisions about people, programs, or communities.
What Is Available Now
The following are live and publicly accessible as of July 2026:
| What | Where | Status |
|---|---|---|
| MAF ICF Participation Program | maf.timebank.tw | Live — public read |
| Community Interest Registration | marketplace.timebank.tw | Live — interest form |
| Gifts — 彼此服事 Church Mutual Aid V0 | gifts.timebank.tw | Live — static pilot |
| WSI Public Identity Site | whitestoneintel.org | Live — public read |
| Marketplace / Program Catalog | marketplace.timebank.tw | Live — no live checkout |
| Learn Platform | learn.timebank.tw | Live — V0 pilot |
| Community Member Portal | portal.timebank.tw | Live — Keycloak gated |
What Is Not Yet Available
The following are explicitly not available and require additional governance authorization before they can operate:
| What | Status |
|---|---|
| Live participant matching | NOT authorized — Gate 3 runtime locked |
| CES exchange / time credit transactions | NOT authorized — Gate 3 runtime locked |
| Community exchange activation | NOT authorized — separate Founder gate required |
| OursWeb / CCNDA church directory matching | NOT authorized — waiting for API key |
| Automated offer / acceptance workflows | NOT authorized — Gate 3 locked |
| Participant data exchange or collection | NOT authorized — Gate 3 locked |
| Local church MCP deployment | NOT authorized — separate Founder approval required |
Expressing interest in joining this network does not activate any of the above functions. No automated matching, exchange, or data processing will occur from a briefing request.
The Governance Journey
WSI/CES uses a formal gate process before any community exchange or matching feature goes live:
The gate process ensures participant data is handled with full consent, privacy review, and human oversight before any live exchange occurs.
Readiness Maturity Levels
Community Trust Hubs grow through defined maturity levels. Organizations can self-assess their current level and prepare for Founder review before any pilot package is considered:
| Level | Name | Description | Allowed action |
|---|---|---|---|
| L0 | Interest | Wants to learn about Community Trust Hubs | Conversation only |
| L1 | Basic readiness | Steward, mission, and community context identified | Self-assessment |
| L2 | Governance readiness | Consent, privacy, safeguarding, evidence, and reviewer roles drafted | Founder readiness review |
| L3 | Pilot-ready candidate | No STOP conditions; review package complete | Future pilot approval may be requested |
| L4 | Pilot approved | Separate Founder-approved pilot package exists | Not yet available |
| L5 | Renewal-ready | Pilot evidence, audit, and renewal complete | Not yet available |
What We Are Asking of Local Partners Now
- Read — Review the program overview at maf.timebank.tw and gifts.timebank.tw.
- Discuss — Share the Community Trust Hub concept with your leadership team.
- Self-assess — Review the Partner Readiness Checklist below and identify your current maturity level.
- Connect — Send a briefing request to [email protected] to share your community context.
- Wait — No exchange or matching will occur until the governance gate is explicitly opened with your knowledge and consent.
Partner Readiness Self-Assessment Checklist
Use this checklist to assess your organization's readiness before requesting a briefing. Completing the checklist does not authorize any program, data collection, or system access. You can review it informally with your leadership team before contacting us.
1. Biblical AI Governance Boundary
| Question | Our answer |
|---|---|
| We understand AI/digital systems are servant instruments, not masters. | PASS / WARN / STOP |
| We understand AI may not replace God's authority, human conscience, pastoral discernment, consent, or protection of the vulnerable. | PASS / WARN / STOP |
| We will not represent AI output as pastoral, legal, clinical, financial, eligibility, or matching authority. | PASS / WARN / STOP |
2. Organisation and Role
| Question | Our answer |
|---|---|
| Our organisation has a clear local role and defined community it serves. | PASS / WARN / STOP |
| We can name an accountable steward and backup contact. | PASS / WARN / STOP |
| We understand readiness is preparation, not program enrollment or operational approval. | PASS / WARN / STOP |
| We will not claim WSI/CES matching, exchange, CES transactions, or MCP federation are live. | PASS / WARN / STOP |
3. STOP Conditions — Review Before Proceeding
If any item below is "yes", the readiness result is STOP. Contact us before proceeding.
| STOP condition | True? |
|---|---|
| We need AI/digital systems to decide about people or programs. | yes / no |
| We cannot name a responsible human steward. | yes / no |
| We intend to collect participant data before approval. | yes / no |
| We cannot define safeguarding or escalation contacts. | yes / no |
| We cannot accept privacy, audit, renewal, suspension, or rollback controls. | yes / no |
| We need live matching, exchange, CES transactions, or MCP deployment now. | yes / no |
4. Consent and Privacy Readiness
| Question | Our answer |
|---|---|
| We can explain what data would be collected in a future approved pilot and why. | PASS / WARN / STOP |
| We understand consent must be informed, specific, and withdrawable. | PASS / WARN / STOP |
| We can support data minimization, retention limits, and suppression or removal. | PASS / WARN / STOP |
| We understand participant data remains not authorized now. | PASS / WARN / STOP |
5. Vulnerable-Person Protection
| Question | Our answer |
|---|---|
| We can identify vulnerable-person contexts in our community (children, elders, people in crisis, financially vulnerable people). | PASS / WARN / STOP |
| We will not use AI for profiling, eligibility, clinical inference, pastoral inference, or automated decisions about people. | PASS / WARN / STOP |
| We have a human escalation path for harm, coercion, complaint, or consent uncertainty. | PASS / WARN / STOP |
6. Safeguarding and Escalation
| Role | Ready? |
|---|---|
| Named safeguarding lead | PASS / WARN / STOP |
| Backup safeguarding contact | PASS / WARN / STOP |
| Privacy concern escalation path | PASS / WARN / STOP |
| Pastoral or community concern escalation path | PASS / WARN / STOP |
| Contact path to WSI/CES steward | PASS / WARN / STOP |
7. Governance Maturity Self-Assessment
L4 pilot approval and L5 renewal are not available through this checklist. They require separate Founder authorization.
Request a Briefing
If your church, ministry, or community organisation would like to learn more, or to share your community context and begin a conversation, contact us by email. This is a conversation only — no data is collected, no account is created, and no program access is granted by sending an email.
WSI/CES Community Cloud · [email protected] · SDG 11 / 16 / 17