Vendor services are named because they help explain the system. The workflow map, contracts, policy, and runbooks stay portable.
How I Work
Start with one workflow, not a connected agent.
Bring the workflow where the agent can connect but your team still babysits the outcome. I map what it may do, where a human approves, how it recovers, and what evidence proves it worked.
Connected agent → trusted workflow.
Relationship boundary
You are not hiring an internal admin.
You are bringing in a solo operator with a purpose-built toolchain to diagnose, rebuild, and govern one critical operating path. The work is scoped, visible, and designed for your team to inherit.
- You bring the workflow, constraints, and approval owner.
- CREATE SOMETHING maps the rules, builds the control layer, and ships the operating artifacts.
- Your team gets visibility through runbooks, approvals, release evidence, operator briefs, and working software.
Trust boundaries
Transparency creates calm when the workflow has clear boundaries.
The buyer sees enough to trust and inherit the system. Sensitive credentials, private data, and platform-specific complexity stay behind the right operational boundary, so the experience feels calm instead of obscure.
Tokens, API keys, and client credentials belong in the approved vault or runtime environment, not in prompts or handoff docs.
Agents only act inside named permissions. The system shows what can run, what needs approval, and what stops.
Offer ladder
From connected agent to governed execution.
Start with the narrowest offer that proves value. Add Policy OS when the workflow starts touching revenue, compliance, or customer trust.
Service blueprint
The offer ladder turns a connected agent into a trusted workflow.
The service is easier to understand as a progression: first prove the connection, then turn it into one workflow, then install the policy layer that protects operator attention.
MCP Wedge
Connection proof
A constrained host proves the tool boundary before a workflow depends on it.
Workflow System
Operating path
The first handoff gets mapped, rebuilt, tested, and documented for inheritance.
Policy OS
Governed execution
Rules classify work into auto-allow, approval-needed, or blocked with reason.
Operator Surface
Calm visibility
The operator sees the state only when judgment, recovery, or review is required.
Policy OS output
Auto-allowApproval neededBlocked with reason
MCP Wedge
Use this when the connection is the job and your team will operate the workflow directly.
- Connectivity validation
- Scoped host setup
- Read-only or constrained rollout
Workflow System
Fix the first workflow your team still does by hand and make the handoffs reliable.
- Business-rule mapping
- Workflow implementation
- Auth and access setup
- Portable runbooks and handoff artifacts
Policy OS
The governed execution layer that makes Skills + MCP safe to run faster in production.
- Approval and block boundaries
- Reason-coded access decisions
- Operator brief and escalation surface
- Release checks and incident loops
- Evals tied to real workflow behavior
Enterprise Extension
Add this when several systems, teams, or compliance requirements must stay aligned.
- Cross-system orchestration
- Custom trust boundaries
- Deterministic retries and recovery
- Auditability for multi-team operations
Governed execution
Where Policy OS fits.
Workflow System gets the first handoff working. Policy OS turns connected agent capacity into a trusted workflow by deciding what runs automatically, what needs review, and what stops with a reason.
Governed Execution
Policy OS
Hub MCP routes the request. Policy OS turns the connected agent into a trusted workflow by deciding what runs, what waits, and what stops with a reason.
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.
Where Ink fits
Ink is the visible surface. The engagement is the operating layer behind it.
The device makes the promise tangible, but it only works if the workflow has mapped owners, approval rules, blocked states, and evidence. That is what the service installs.
Decides what needs judgment
The operating layer classifies safe work, approval-needed work, and blocked actions before the operator is interrupted.
Makes the decision visible
The physical surface is optional, but useful when the buyer needs to see and feel the operator promise.
Acts only when needed
The service is designed so the human returns to the dashboard for evidence and action, not for constant monitoring.
Operating Artifacts
What ships with every governed engagement
Every governed engagement ships as artifacts your team can inspect, run, 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.
First call
The mapping session is where the buyer stops guessing.
We turn the messy workflow into an inspectable plan: what connects, what runs, what pauses, what stops, and what artifact proves the first build.
Book Mapping SessionThe handoff with drag, risk, rework, or capacity trapped in manual coordination.
Source accounts, owners, vendor roles, approvals, blocked states, and failure modes.
Whether the right first move is MCP Wedge, Workflow System, Policy OS, referral, or governed agent capacity.
Workflow map, stack boundary, agent/MCP contract, policy notes, and implementation path.
Questions
What buyers usually need clarified before the first call.
What is your primary service?
Workflow System 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.
Are you joining our team or running internal ops?
No. I operate as a solo specialist using CREATE SOMETHING as the delivery toolchain. You get scoped delivery, governed agent capacity, artifact-backed visibility, approval points, and a clean handoff instead of open-ended staffing.
Are agents part of the workforce?
They can be, but connection is only the starting point. Agents belong in the workflow when they have a clear job, scoped tools, approval boundaries, and evidence. MCPs are the toolkits; Policy OS decides what agents can do, what needs a person, and what must stop.
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. .agency is optimized for workflow systems and governed execution, not ongoing admin coverage.
What does .agency own?
.agency owns the rules, approvals, handoffs, release controls, and operating artifacts around the workflow. Your team keeps business context, approval ownership, and long-term control.
When should we add Policy OS?
Add it when failures become expensive or the workflow touches revenue, customer trust, compliance, or several systems that must stay in sync.
Do you still offer MCP Wedge?
Yes. MCP Wedge still works for discovery, compliance-constrained pilots, or teams that need the connection before the operating layer.
Do we need to understand MCP or the vendor stack first?
No. Bring the workflow and the accounts involved. I translate the technical choices into a stack boundary, decision states, and implementation path your team can explain.
Do clients own the implementation?
Yes. Clients retain ownership of code, workflows, and operating documentation. The delivery is meant to stay portable after launch.
Is Ink the product?
Ink is the visible operator surface. The paid service is the workflow mapping, policy layer, artifacts, and escalation behavior that make the surface trustworthy.
Why the phrase Skills + MCP?
Client-facing delivery is Skills + MCP. MCP handles connectivity. Skills carry behavior and workflow intent. Policy OS turns both into a trusted workflow.
Map the workflow
Map the workflow that's creating the most drag.
We will define the handoffs, approvals, failure modes, and escalation path before any implementation work starts.