Approach
Leaders decide. Assistants prepare.
dCRN gives leaders leverage without touching their authority. The system never acts as the leader, and it never pretends to have decided anything.
From a spoken concern to an approved action.
Speak to the assistant
A coordinator records a voice note while the problem is still fresh.
Transcript captured
The audio becomes a source record and a plain summary of the issue and the ask.
Context checked
The assistant pulls related policies, prior decisions, and commitments from the knowledge base.
Recommendation drafted
Conflicts are flagged and a step-by-step implementation path is proposed.
Approve, pend, decline
Approved items become tasks. Everything is preserved.
Guardrails
Five rules the system will not break.
A recommendation is never presented as an approved decision until a human leader approves it.
Every recommendation cites the internal source material it was built from.
The assistant asks for missing context rather than inventing facts about people, budgets, policies, or schedules.
Anything involving minors, safety, HR, pastoral care, finances, or legal exposure escalates to a human immediately.
Permission boundaries hold. A volunteer lead never sees executive-only knowledge unless it is granted.
The pilot
Thirty to sixty days inside one ministry.
We are not asking a church to buy software. We are asking one church to help shape it. The pilot runs inside a single ministry, such as youth, worship, discipleship, or operations, and expands only after the decision workflow proves it earns its place.