Specific
A trusted source is a particular authority record, not a generic web search or an AI's best guess.
Goal-first workflow · same governance boundary
How it works
From “here is my goal” to “here is what the trusted source supports.”
CharterGate starts in ordinary language, then makes the source, limits, result, and evidence visible before any separate system can act.
01
Start with the goal.
Tell CharterGate what you are trying to accomplish in normal language. You do not need to begin with project slugs, action codes, run IDs, or JSON.
02
Choose the trusted source.
Select an already-configured source that actually applies: a specific policy, owner instruction, agreement, rule set, or other registered authority. Selecting a source does not create permission.
03
Clarify the context.
CharterGate asks where the goal applies, what should be checked first, and who is responsible for the final decision. It then prepares the guided evaluation without inventing authority.
04
Define limits and impact.
Review the request, included scope, exclusions, conditions, risk, and reversibility before evaluation so material mistakes are not silently carried forward.
05
Resolve and compare the exact authority.
CharterGate verifies the selected source and compares the request against the controlling binding. Revoked, superseded, expired, wrong-scope, or provenance-invalid records do not silently control.
06
Review Results, Sources & Evidence.
The product shows the governance result in plain language while preserving the controlling source, conditions, diagnostics, unresolved requirements, and audit evidence underneath it.
07
You decide what happens next.
CharterGate does not send, publish, deploy, pay, or modify external systems, and it does not infer owner approval. A separate authorized executor may act later only under its own authority and credentials.
Trusted sources in plain language
The check is only as real as the source behind it.
CharterGate keeps the source explicit so the user can tell what rules actually controlled the evaluation.
Scoped
The source applies only within its recorded project, action, target, conditions, exclusions, validity, and other material boundaries.
Fail-closed
If CharterGate cannot establish the required source or binding, it stops the evaluation path instead of turning uncertainty into permission.
Three presentation modes
The interface can get simpler or deeper without changing what controls.
Simple, Business, and Advanced change how the workflow is presented. They do not change source precedence, authority bindings, or the meaning of a governance disposition.
Goal-first guidance
Start with the goal, choose a trusted source, answer plain-language context questions, and review the result without needing machine terminology.
Structured workflows
Templates, repeatable context, and evidence suited to recurring team processes.
Full detail
Bindings, diagnostics, provenance, and audit detail for operators who need the complete record.
What the result means
Results for people. Sources & Evidence for verification.
CharterGate separates readability from proof rather than making people choose one or the other.
Result
Example
“The proposal is supported within the approved content-only scope. The recorded condition is that no DNS or access-control change is included.”
Sources & Evidence
Inspectable basis
Controlling authority identity, source provenance, matched proposal fields, conditions, unresolved requirements, diagnostics, evaluator version, and audit record.
Gate Keeper
Help and explanation only.
Gate Keeper can explain what a field means, help a user understand why CharterGate stopped, or point to the evidence behind a result. It cannot create authority, reinterpret the controlling source, alter a disposition, or execute anything.
Private preview
See the workflow with a bounded example.
Bring a low-risk scenario with a clear decision owner and explicit execution boundary.