Roster
Your firm's vendor panel as structured data: primary, backup, and excluded tiers, scoped by category, callable from your AI.
What it does
Your roster is the set of vendors your firm has decided to work with. Scope holds it as structured data with three tiers: primary (first priority), backup (overflow and after-hours), and excluded (never dispatch).
Entries are scoped by category, so your primary court reporter and your primary process server are independent. Lock windows let you commit a vendor to a tier for a period.
Your AI can read the roster, set a vendor's tier, and remove a vendor. Every roster change is recorded.
Why it matters
Dispatch is roster-first, so the roster is what makes routing land on the vendors you trust instead of a cold marketplace. Bringing your existing vendors onto your roster keeps the relationship yours.
The excluded tier is a hard stop. A vendor you have had problems with never receives a dispatch, with no chance of a stray email reaching them.
How to use it
Call scope_list_roster to read it, scope_set_vendor_tier to change a tier, and scope_remove_from_roster to remove a vendor.
scope_list_roster()
scope_set_vendor_tier({ vendor_id: "...", tier: "primary" })