AI ADMINISTRATOR 3.1 · SECURITY
Your data path. Your choice.
Fusion Toolkit is the local policy and execution boundary. Credentials, plans, approval enforcement, licence checks, and Oracle transport stay there. Model exposure depends on the agent and runtime you choose.
Two model paths
Local model path
You → compatible Ollama or local Qwen agent → local Toolkit → your Oracle origin
Prompts and selected results can stay on your machine when the complete agent and model runtime are local.
Provider-backed path
You → Codex, Claude, Gemini, or another provider-backed agent → local Toolkit → your Oracle origin
Your prompts and selected, bounded results may reach that provider under its account, regional processing, retention, and training controls.
Stays in your environment
- Oracle and licence credentials
- Encrypted profiles and canonical immutable plans
- Documentation checksums, effect classification, approval policy, and same-origin enforcement
- Oracle HTTPS transport, raw attachments, output files, and unselected response fields
Approval is a later act
Every state-changing or unknown-effect request stops after the complete current plan is displayed. Approval must arrive later and refer to that exact plan. Chat approval is the normal path; a human at the controlling terminal may use the terminal phrase fallback. Silence, an earlier blanket instruction, a tool permission, or a changed request is never approval.
- One execution: each approved write runs once; ambiguous results are never retried automatically.
- Exact counts: completed, failed, and unattempted operations are reported separately.
- Independent verification: a successful transport response is not presented as verified business success.
- Specific recovery: high-risk operations show the real impact and a separately reviewed recovery route before approval.
History is owner-approved
Execution history and reusable recipes are optional. After a successful read or completed write, the Toolkit asks whether to save them to the owner-only local library. Nothing is saved without a yes. Saved records are plain local JSON with credentials and transient approval material stripped. If a provider-backed model later reads that history, its contents may be transmitted to that provider.
No automatic Hufflelab data path
Nothing is transmitted to Hufflelab automatically. Fusion Toolkit supplies no hosted model, provider account, model API key, credits, or model subscription. Optional content-free metrics export remains opt-in.