Cookbook Overview
Start Here
This is the fastest way to choose the right Locus cookbook for your use case.
Pick by outcome, not by internal architecture.
Choose by Outcome
I need better answers in customer-facing workflows
Start with:
I need safer incident or operations decisions
Start with:
I need rollout-safe automation with dry-run controls
Start with:
I need research and synthesis across sessions
Start with:
Choose by Build Style
I want code-first SDK examples
Start with Examples.
I want orchestration recipes plus prompt templates
Start with Mini Orchestration Cookbooks.
I want domain presets and starter config values
Start with Agent Blueprints by Domain.
Quick Path Matrix
| Goal | First Page | Time to First Value |
|---|---|---|
| Support copilot with memory grounding | Cookbook 1 | 30-60 minutes |
| Incident triage with explain guardrails | Cookbook 2 | 45-90 minutes |
| Release decision workflow with dry-run transforms | Cookbook 3 | 60-120 minutes |
| Research synthesis with deterministic context shaping | Cookbook 4 | 45-90 minutes |
| Domain-specific rollout preset | Agent Blueprints | 30-60 minutes |
Implementation Flow We Recommend
- Start with one cookbook and keep scope narrow.
- Run recall plus explain before writing any policy automation.
- Add transform dry-run as a safety default.
- Promote to production only after integration acceptance checks.
Competitive Positioning
Locus is optimized for teams that need:
- memory behavior that is observable and explainable,
- deterministic workflow composition options,
- transport-neutral integration paths across SDK, MCP, and gateway.
Use this hub as your entrypoint, then deepen into the linked pages.