Identity and access
Service accounts, delegated access, credential storage, scopes, rotation, and operator roles.
Security & operations
Security posture is determined by the full architecture: environment, models, integrations, credentials, memory, logs, approvals, and operating ownership.
Threat model first
A client-controlled server does not by itself make the system private. The final data flow must state which external model, document, communication, and integration providers receive information.
Control planes
Service accounts, delegated access, credential storage, scopes, rotation, and operator roles.
Read and write separation, action allowlists, thresholds, approval gates, and blast-radius limits.
Source authority, client scope, retrieval filters, retention, deletion, and correction paths.
Decision traces, tool events, exceptions, costs, quality signals, alerts, and incident evidence.
Client-controlled, dedicated, cloud, hybrid, or local environments selected from actual requirements.
Versioned prompts, tools, policies, models, tests, rollback, and approval for production changes.
Autonomy matrix
Low-risk, reversible, tested actions with complete input and clear evidence.
Example: prepare a draft status brief.Client-facing, financial, regulated, uncertain, or difficult-to-reverse actions.
Example: send an engagement package.Actions outside role, permission, law, policy, or the agreed operating boundary.
Example: make a professional judgment reserved for licensed staff.AI Readiness Audit
In one working session, we map the workflow, systems, approval boundaries, risks, and the most useful first deployment.