Specialists, Guided Authoring & Revisions
Build reliable operational specialists with structured behavior forms, compiled system snapshots, immutable revision history, and canonical DM threads.
Operations Managers shouldn't have to debug brittle prose prompts when updating seasonal customer instructions. In SCA, each Specialist is defined by structured fields compiled cleanly into an immutable revision snapshot.
Structured fields instead of raw prompt sprawl
When configuring or editing a specialist under Specialists, owners organize behavior across four crisp sections:
- Identity & Scope: Clear display name, department label, plain-language summary, and zero-prompt starter templates for dispatchers.
- Structured Instructions: Operational boundaries (always cite section/page numbers, refuse undocumented exceptions rather than guessing, escalate restricted loads).
- Attached Knowledge Collections: Explicit binding to customer manuals or internal handbooks (
Coca-Cola SOPs,EU Customs Rules,Warehouse Safety). - Approved Tools: Toggled access to read lookups (
track_shipment,web_search) or confirmation-gated write connectors (log_carrier_exception,release_warehouse_hold).
Immutable revision history & rollback
Every save creates an immutable specialist_revisions snapshot storing the compiled instruction text, linked Knowledge Bases, tool assignments, and author timestamp. Supervisors can inspect past revisions and restore a prior snapshot cleanly if a rule update introduces unwanted phrasing.
Persistent canonical Direct Threads
Rather than scattering yesterday's pallet clarification across dozens of ad-hoc "New Chat" sessions:
- Each
(company, user, specialist)pair shares one canonical direct conversation. - Dispatchers can search past messages inside the thread without hunting through sidebar archives.
- Long-running threads automatically compact older turns into summary checkpoints, keeping model context lean and fast while keeping full audit history scrollable.