Console
What the system knows, and how the agents behave. Every change applies on the next run.
Account and workspace
Who this workspace belongs to, where it runs, and where the data lives.
- Workspace
- Shepherd, broker growth
A take-home build by Matthew Oshin, not a Shepherd production system.
- Built by
- Matthew Oshin
matthewoshin.com
- Prepared for
- Julian Clarke, Head of Marketing
- Drafts sign as
- Kenneth Rawls, Head of Casualty
Change the roster in Console, Underwriters.
- Brokers on file
- 450
0 engagements logged against them.
Where it runs
Today's answer, and where this is going.
- Application
- Vercel
Git-connected, deploys on push to main. Serverless functions, no always-on process.
- Database
- fvkjwwkanntbobgmfcuq
Supabase Postgres. Every table prefixed shepherd_, row level security on, service role server-side only.
- Domain
- shepherd.matthewoshin.com
DNS on DigitalOcean, pointed at Vercel.
- Planned move
- Self-hosted VPSPlanned
Vercel and Supabase are the right call while this is a take-home: nothing to babysit and it deploys itself. A VPS becomes worth it when there are long-running jobs to own, a scheduler that is not a serverless cron, and the monitors running on a real timer. Nothing here would need rewriting for it: it is a Next.js app against Postgres.
Model spending
The short version. The full rules are on the AI page.
- Scheduled AI
- OnConfigured
The weekday sweep is allowed to run the classifier on a timer.
- Daily ceiling
- 200 model actions
Shared across every visitor, so a public link cannot run up a bill. Reads are never limited.
- Full rules
- Console, AI
Which model does which job, which answer engines are on, and how the agents are constrained.