Safety and Trust
The boundaries that make autonomous operations inspectable, revocable, and recoverable.
Organization Isolation
Applicable reads and writes are scoped by organization. Integration capabilities also bind the organization, profile, integration, and active execution.
Credential Isolation
Provider secrets stay encrypted behind the backend. They are never intentionally placed in an agent prompt, context manifest, workspace, log, or durable provider receipt.
Authorization Can Change
Credential rotation, disabling an integration, changing selected tools, or narrowing access advances authorization state and invalidates resumable chat sessions. A stale run cannot continue under an old grant.
Effects Are Explicit
Consequential external changes use typed actions with idempotency, risk, policy, execution state, and receipts. Unknown outcomes are visible and require reconciliation.
Output Must Be Durable
Validated workspace output is synchronized before success. A temporary worker exiting does not erase the business record of attempts, questions, approvals, evidence, or artifacts.
Hidden Reasoning Is Not Company Memory
Oblive retains useful summaries, evidence, decisions, blockers, checkpoints, and next actions. It does not promote hidden model reasoning into organizational context.
Local-first Does Not Mean No Boundaries
The supported stack is local, but provider access, service authentication, path validation, tenant scoping, and action policy still apply. Local deployment is not a reason to pass secrets through prompts or bypass durable state.