First Class Modules

GoClaw virtual assistant

Adds a dedicated virtual assistant to a user account that researches, summarizes, classifies, drafts, and proposes work without ever receiving more access or action authority than that user.

Use GoClaw as the virtual assistant attached to each enabled user account. It helps that person work their permitted Inbox items and business records, but it is not a privileged service account and cannot step outside the user's existing authorization boundary.

What it does

Adds a dedicated virtual assistant to a user account that researches, summarizes, classifies, drafts, and proposes work without ever receiving more access or action authority than that user.

Key capabilities

• Read only records, fields, locations, and Inbox context the represented user may read—and only when AI access is also allowed.
• Research, classify, summarize, draft replies, and prepare structured next actions.
• Create suggestion batches whose evidence, risk, confidence, required permission, and inputs can be reviewed.
• Route material or customer-facing actions through configured policy or human approval before deterministic execution.
• Respect action budgets, leases, retries, stale-context fences, and idempotent execution.
• Record attribution, approval/refusal, tool/action evidence, results, failures, ratings, and correlation history.

Common uses

• Triage and response preparation for permitted Universal Inbox work.
• Account, case, project, support, or operations research and follow-up suggestions.
• A personal daily assistant that reduces preparation work while the user retains decision authority.

How it connects

GoClaw claims authorized Inbox work, prepares AiActionSuggestionBatches and AiActionSuggestions, and—after current permission/policy/approval checks—creates AiActionExecutions for deterministic executors. It uses native records and the secured AI retrieval plane rather than maintaining a shadow copy of the user's data.

Where applicable, its records use the universal RecordId conventions so they can participate in secured relationships, activity history, favorites, dynamic fields, notifications, Inbox attention, and global search without copying the source record.

Security and data boundary

GoClaw operates on behalf of one user. Its effective access is the intersection of that user's tenant, DataRole, record, field, location, and action permissions with AI-specific CanAiReadRecords, secure-field exclusions, tool policy, quotas, approval policy, and the current source/Inbox activity version. The result can be narrower than the user's normal access, never wider.

• The authenticated service derives the SaaS app, tenant account, user, DataRole, and location scope; browser identifiers are never authorization proof.
• The page editor composes React components with validated data bindings. Those bindings call typed runtime APIs, whose application services execute reviewed stored procedures.
• List, search, detail, relation, activity, favorite, and write operations reapply their required server-side permissions.

Add it to an app

1. Enable the assistant for the intended user account and bind it to that user—do not create a wider shared service identity.
2. Select the Inbox queues/channels and record contexts it may prepare, while preserving all normal user and AI-read checks.
3. Configure reviewed action templates, required permissions, authority/approval policy, quotas, and exact behavior/harness versions.
4. Begin with research and drafts; add deterministic actions one at a time with safe error, retry, and idempotency behavior.
5. Test restricted records, secure fields, another location, stale Inbox activity, refused approval, quota exhaustion, and duplicate execution before widening use.