MCP-only
Use this when you need the connection first or your team will operate the workflow directly.
- Connectivity validation
- Scoped host setup
- Read-only or constrained rollout
How I Work
Start with the workflow creating the most drag.
Fix the first workflow. Add approvals and oversight when the risk rises. Reserve Enterprise Extension for auditability, recovery, and cross-system coordination.
Governed Execution
Where Policy OS fits
Workflow Infrastructure gets the first handoff working. Policy OS decides what runs automatically, what needs review, and what stops.
Client LLM
Ops Inbox
Background Agent
Routes
Hub MCP Tenant, host, session
Decides
Policy OS Reason-coded governance
Auto-allowApprovalBlock
CRM
ERP
Workflow System
Safe actions run fast. Risky actions route to approval. Disallowed actions stop with a reason.
The Reliability Stack
Connectivity
Model Context Protocol
Compute
Cloudflare Workers
Persistence
Cloudflare D1
Intelligence
Anthropic Claude
State Coordination
Durable Objects
Client Runtime
SvelteKit
Safety
TypeScript
Operating Interface
Notion API
Offer Ladder
From wedge to governed execution
Start with the wedge that proves value. Add governed execution when the workflow starts touching revenue, compliance, or customer trust.
Policy OS
The approval and oversight layer that makes Skills + MCP safe to run faster in production.
- Approval and block boundaries
- Reason-coded access and blocked states
- Evals, release gates, and incident loops
Enterprise Extension
Apply when several systems, teams, or compliance requirements have to stay aligned.
- Custom trust boundaries
- Cross-system orchestration
- Deterministic retries and auditability
MCP-only gets you connected. Policy OS keeps the workflow safe as speed and volume increase.
Operating Artifacts
What ships with every governed engagement
Every governed engagement ships as artifacts your team can inspect, inherit, and operate.
mcp_contract.yaml
Tools, resources, auth scope, and transport boundaries.
agent_contract.yaml
Allowed actions, approvals, escalation triggers, and operating limits.
outcome_contract.md
Success metrics, fallback triggers, and ownership boundaries.
runbook.md
Recovery steps, operator lanes, and rollback expectations.
golden-task checks
Regression evidence that keeps releases tied to real workflow behavior.
What a Month Looks Like
Phase 1
Workflow Infrastructure
Get the first high-value workflow working with clear rules, owners, and handoffs.
Phase 2
Policy OS
Add evals, approvals, release checks, and incident loops as the workflow touches real risk.
Phase 3
Extension
Extend into custom orchestration when several systems or teams need one operating model.
Questions
What is your primary service?
Workflow Infrastructure fixes the first painful workflow. Policy OS becomes the core engagement once speed needs approvals, release controls, and ongoing oversight. Enterprise Extension covers the highest-stakes environments.
Do you build full business systems and run onboarding?
When full system development and team onboarding are the primary need, I provide a direct referral path to Half Dozen.
What does .agency own?
.agency owns the rules, approvals, handoffs, release controls, and operating artifacts around the workflow.
When should we add Policy OS?
Add it when the workflow touches revenue, customer trust, compliance, or several systems that must stay in sync.
When do we need Enterprise Extension?
Use Enterprise Extension when several systems, teams, or compliance requirements must stay aligned and recover cleanly from failure.
Do you still offer MCP-only?
Yes. MCP-only still works for discovery, compliance-constrained pilots, or teams that need the connection before the operating layer.
Do clients own the implementation?
Yes. Clients retain ownership of code, workflows, and operating documentation. We optimize for portability and long-term control.
Why the phrase Skills + MCP?
Client-facing delivery is Skills + MCP. MCP handles trust and connectivity. Skills carry behavior and workflow intent.
Map the workflow that's creating the most drag.
We’ll define the handoffs, approvals, failure modes, and escalation path before implementation.