FAQ
Direct answers about CharterGate.
What problem does CharterGate address?
CharterGate helps a person or AI-controlled workflow start with a real-world goal, turn it into an exact request, and check that request against a verified trusted source before any separate execution occurs.
Does CharterGate execute the action?
No. CharterGate evaluates and reports. Real-world execution stays in a separate system under separate credentials and controls.
What is a trusted source?
A trusted source is a specific registered authority that CharterGate can identify and verify, such as an owner instruction, policy, agreement, rule set, or other source that actually applies to the request. It is not a generic website, an AI guess, or a template.
Does private-preview access expose every trusted source?
No. Private-preview identities can be scoped to specific trusted sources, can expire, and can be revoked independently. Having access to CharterGate does not automatically grant access to another organization's private sources.
What does an AUTHORIZED result mean?
It is governance evidence for the exact evaluated request under the controlling trusted source. It is not the action itself, does not grant unrelated permission, and does not infer the owner's separate approval.
Can an agent grant or expand its own authority?
No. A governed component must not be able to register, enlarge, bypass, or silently reinterpret its own authority.
Can memory or model reasoning establish permission?
No. Memory, retrieval, and reasoning can support context, but authority must come from an applicable verified authority basis.
What happens when a material requirement cannot be established?
The consequential lane should fail closed. Unresolved authority, provenance, identity, scope, condition, or binding problems remain visible instead of being converted into approval.
What details can matter to an evaluation?
Tenant, actor, action type, target, capability, risk, reversibility, scope, exclusions, conditions, validity dates, source revision, and relevant artifact identity can all be material.
How are revoked or superseded records handled?
CharterGate keeps revocation and supersession explicit. Historical authority can remain auditable without silently remaining effective.
What should an audit record explain?
It should identify the exact proposal, controlling authority and revision, material matches or mismatches, applied conditions, evaluator and policy version, returned result, and audit identity.
What makes CharterGate more than a simple allow/deny check?
CharterGate is designed to preserve the authority source and revision, resolve the controlling record, compare the exact proposal binding, keep unresolved material requirements visible, and return separate resolution, gate, disposition, and authorization states with audit evidence. A simplified allowed/blocked field can be derived for a client, but it does not replace the canonical governance state.
Where can CharterGate fit?
Start with a bounded workflow where the goal, trusted source, scope, conditions, reversibility, and final decision owner can be stated clearly. The use-cases page explains the fit boundaries.
How can I ask a question about CharterGate?
Use the contact form for questions about the product, a potential use case, or the governance model.