01
Intent becomes a mission
A request should be clarified into an objective, risk assessment and proposed actions before operational execution begins.
Trust and governance
Capability should be inspectable before it is autonomous.
FrankAI is built around controlled action: understanding intent, identifying consequence, obtaining meaningful authority and preserving evidence.
02
Approval requires context
A reviewer should see the intended action, credible failure modes, withheld actions and the effect of rejection.
03
Action leaves a receipt
Material actions should produce evidence of authority, scope, outcome and recovery path without exposing unnecessary private content.
Capability register
What is live, staged and deliberately locked.
Honest status is part of the product. A capability is not represented as active until the access, safety and delivery path are actually verified.
Live
First-party frankai.online presence and controlled public information routes.
Live
Frank ServiceDesk operational workflow environment.
Live
Signed messaging integration bridge for controlled assistant events.
Staged
Frank Dispatch mission, approval and action receipt workflow using safe fixture intake.
Locked
Inbound email ingestion pending webhook credential activation and operational hardening.
Frank Dispatch
The next operating layer.
Dispatch is being developed to turn contact into governed missions, approvals and action receipts before real-world execution is enabled.