Blog
Approvals, Budgets, and Logs: Safety by Default
Week 3
How policy modes and autonomy budgets prevent risky actions.
Local-first execution keeps model weights and sensitive data on-device unless you opt-in to the cloud.
High-risk actions pause for consent, and outbound communication is disabled until explicitly configured.
Audit logs capture tool inputs, outputs, and decision points so compliance teams can validate behavior.
More stories from the community
Week 1
A Private, Local AI Assistant with Guardrails
Announcing MCP and the philosophy behind local-first autonomous execution.
Read postWeek 2
Plan → Execute → Verify: Inside the Orchestrator
Diving into DAG planning, approvals, and audit trails.
Read postWeek 4
Authoring a New MCP Tool in 30 Minutes
Step-by-step walkthrough of schema-first tool development.
Read post