Framework, applications, and cookbooks
Separate reusable SDK capability from consuming applications, agent runtimes, synthetic scenarios, and hosted control planes.
What the framework owns
- Vendor-neutral incident and recovery contracts.
- Deterministic diagnosis, explanation, and bounded evidence collection.
- Provider-neutral evidence, model, memory, reporting, context, policy, approval, verification, and audit ports.
- Strict configuration, redaction, local reports, local memory, webhook normalization, plugin discovery, CLI, and test doubles.
What consuming applications own
- Monitoring and incident detection.
- Provider credentials and concrete connectors.
- Project-specific rules, runbooks, prompts, playbooks, and policies.
- Agent runtime and model selection.
- Production orchestration, deployment, transport security, and access policy.
Why cookbooks remain separate
Cookbooks are executable learning and validation artifacts. They use synthetic data, own their optional dependencies (Agno and OpenRouter appear only there), and demonstrate how an application consumes core interfaces. They are examples—not the product boundary and not production control planes.