Deep Dives
Multi-part freemium guides for people and agents building real AI workflows. Early parts of each series are free.
12 lessons · 5 free · Full curriculum
Build your own agent back office (CJS case study)
- Free Why a back office beats a lone agent
Use CJS's internal agent office as a case study in separating intake, coordination, specialist work, and approval. Design a small back office with visible ownership and clear limits. - Free Roles and ownership
Translate CJS's internal role patterns into clear responsibilities, review gates, and handoffs. Build a local ownership map that distinguishes preparing work from authorizing consequential actions. - Free Intake and the front desk
Learn from CJS's internal Secretary pattern to capture requests, separate routing from approval, and handle uncertain or consequential work. Practice a local front-desk workflow without calling APIs or taking external actions. - Premium Routines and the Office floor
Scheduled runs, status reporting, and the stale-agent problem — with a lightweight runbook template you can adapt. - Premium Deploy gate and Codex offload
Who may change the live site; draft → verify → publish; when to hand long work to Codex and what never goes in the prompt. - Premium Ship checklist and a minimal starter layout
Folder/API sketch, first-week checklist, and what to leave to Infrastructure — finishing the back-office build.
Add a decision layer: JEV on defapi without exposing keys
- Free What JEV is (and is not)
Understand JEV as a non-generative decision model, identify useful routing and ranking tasks, and keep its suggestions inside clear authority limits. - Free Where it sits in an agent stack
Place JEV behind an internal decision service, preserve existing authority and fallbacks, and design a shadow-first workflow before making any provider calls. - Premium Designing a small decision catalog
Named decisions, versioned questions, and thresholds — start with 3–5 decisions such as priority, station, and grounded_check. - Premium Keys, redaction, and calling defapi safely
Server-only secrets; redact PII before calls; no keys in prompts, repos, or browser; failure modes when the endpoint is down. - Premium Budgets, cache, circuit breaker
Daily caps, cache keys, breaker behaviour, and fallback to today’s rules when the decision layer is unavailable. - Premium Eval set and going live
Labelled examples, shadow mode, random audit, kill switch, and a checklist before leaving shadow.