Guspora Stewardship

Inspiration

Churches and ministries often manage real property, maintenance, safety, and community-service needs through conversations, meeting minutes, text messages, volunteers, and separate contractors.

The decision may be recorded, but the work that follows can still become fragmented:

Who is responsible?
Has funding been confirmed?
Which provider was selected?
What work has actually been completed?
What evidence exists?
Who has authority to approve the result?

Guspora Stewardship was inspired by the belief that compassion should lead to accountable follow-through. It helps ministries care faithfully for their property, resources, people, and commitments without replacing the church’s existing governance or trusted relationships.

What it does

Guspora Stewardship turns a property or ministry need into a funded, assigned, evidence-backed project.

The demonstration follows a fictional church property issue involving an unreliable emergency light in a food-pantry exit corridor.

The church administrator can:

Record the need against the exact property, space, and asset.
Ask GPT-5.6 to create a structured Stewardship Plan.
Review and edit the AI-generated plan.
Record how the church authorized the project, such as a congregational vote, committee decision, or authorized leader approval.
Confirm the project budget and funding commitments.
Connect a chosen service provider only after the funding gap reaches zero.
Monitor milestones, blockers, notes, and completion evidence.
Review the provider’s submission.
Accept or return the work for correction.
Update the asset’s permanent maintenance history and generate a privacy-safe Stewardship Impact Receipt.

The provider receives a separate, permission-limited workspace containing only the authorized project scope. The provider can accept the assignment, update milestones, record blockers, add evidence, and submit the work for review, but cannot approve its own completion.

Progress is based on real milestones and evidence rather than an invented percentage.

Human authority and responsible AI

GPT-5.6 acts as a bounded planning assistant.

It can draft:

Clarifying questions
Proposed tasks
Cost categories
Suggested milestones
Evidence requirements
Follow-up dates
Safety and privacy flags

It cannot:

Declare a property safe
Make a final code-compliance determination
Approve funding
Select the final provider
Authorize church decisions
Approve completed work
Give pastoral or spiritual direction

The application preserves the original model-generated plan separately from the human-edited and authorized version.

The central product principle is:

AI drafts. Authorized people decide.

How we built it

Guspora Stewardship was built as a focused proof of concept that can later become a ministry-specific workspace inside the larger Guspora platform.

The application uses:

Next.js
React
TypeScript
OpenAI Responses API
GPT-5.6
Zod Structured Outputs
Vitest
Playwright
Browser-local versioned demo persistence

Codex materially implemented and hardened the project’s:

Role and capability policies
Project state machine
Application-service and persistence boundaries
Funding and provider-assignment gates
GPT-5.6 integration
Structured-output validation
AI authority guard
Provider privacy boundaries
Milestone and evidence workflows
Human completion transaction
Asset-history update
Stewardship Impact Receipt
Accessibility behavior
Automated test coverage
Submission documentation

A genuine authorized GPT-5.6 request completed successfully through the OpenAI Responses API. The response was parsed against the required schema, and all semantic, invariant, and authority checks passed.

The final build passed:

148 automated tests across 15 files
TypeScript validation
Linting
Production build
Playwright browser testing
Dependency audit with zero production vulnerabilities
Tracked-file secret and raw-output scanning

Challenges we faced

One major challenge was preventing the AI experience from becoming an unaccountable chatbot. The generated plan had to be useful while remaining clearly subordinate to human authority.

We also had to make one project record serve two very different users. The church administrator needed governance, funding, and approval controls, while the provider needed only the authorized scope, milestones, and evidence requirements.

The live GPT-5.6 integration also required careful timeout handling, strict structured-output validation, semantic checks, and an authority guard. The application fails honestly when a model call is unavailable or invalid and never presents deterministic fallback content as genuine GPT-5.6 output.

Finally, we wanted the demonstration to remain safe and repeatable. All church, property, provider, sponsor, funding, and evidence records shown are fictional. No production Guspora data, real church records, donations, payments, customer communications, or external provider invitations are used.

Accomplishments we are proud of

We are especially proud that the project demonstrates a complete operational outcome rather than ending with generated text.

A single accepted completion action:

Records the church’s human review
Updates the permanent asset-maintenance history
Preserves the evidence
Creates an auditable activity record
Generates the Stewardship Impact Receipt

All of those results come from the same authoritative project record.

We are also proud that the product respects church governance rather than attempting to replace it. A church may continue making decisions through its existing meetings, committees, leaders, and congregational processes. Guspora Stewardship records the authorized decision and helps carry it faithfully through completion.

What we learned

We learned that AI becomes far more valuable when it operates inside a governed workflow instead of acting as the final authority.

We also learned that many operational failures are not caused by a lack of compassion or good intentions. They happen because ownership, funding, scope, evidence, and completion authority were never made explicit.

The strongest version of Stewardship is therefore not another church content application. It is an accountable operating workspace for real ministry needs.

What's next

The next step is to integrate Stewardship into Guspora’s shared platform architecture.

Future capabilities may include:

Multiple properties and assets
Recurring maintenance
Connected service-provider organizations
Volunteer-safe task coordination
Sponsor-funded ministry access
Church and nonprofit facility projects
Community-service projects
Inspections and deficiencies
Documents and communication
Ministry-safe reporting
Privacy-controlled impact summaries

Stewardship will remain a focused ministry experience while using Guspora’s shared identity, permissions, property records, providers, evidence, audit history, and governed AI controls.

The long-term vision is simple:

Turn ministry needs into funded, assigned, accountable, and verified outcomes.