INTENT & CONTEXT
Define the work.
Begin with a bounded task and the context it needs. State the intended outcome and the authority available to the workflow.
THE MOTHERSHIP SYSTEM
One center of gravity.
Explicit boundaries.
Bring the intent, authority and record of AI work into the same operating picture.
SYSTEM MAP / 001ILLUSTRATION
01Your intentOne bounded task
MOTHERSHIPPlan · coordinate · resume
02Scoped toolsPermission before action
↳DeadBoltExternal enforcement
↗WitnessProvenance boundary
A record you can inspectDecisions, outcomes, integration evidence.
↓CONTROL PLANESELF-HOSTED / PRIVATE
THREE DIFFERENT RESPONSIBILITIES
Coordinate.
Gate.
Substantiate.
Mothership is the orchestration center. DeadBolt provides an external enforcement boundary where integrated. Witness addresses provenance. Their distinct responsibilities make the integration worth examining.
Inspect the recorded integrationONE EXECUTION PATH
Connect through
your own stack.
REST, MCP and the Python SDK share Mothership’s dispatcher. Tool discovery, scoped access, memory, approvals and receipts belong to the same workspace.
RESTMCPPython SDK
MOTHERSHIPShared dispatcherScopes · state · approvals · receipts
Conceptual architecture. No endpoint is contacted by this illustration.
FROM INTENT TO RECORD
A workflow with
somewhere to return to.
A conceptual workflow, not a guarantee that every deployment implements every path.
ORCHESTRATION
Coordinate the next step.
Use Mothership's orchestration, scoped tools and approval mechanisms to organize the work. Keep continuation tied to the task's state.
INTEGRATED ENFORCEMENT
Enforce the boundary.
Where DeadBolt is wired into a tool path, ask the external gate before allowing an action. The integration boundary matters; a gate cannot protect a path that bypasses it.
EVIDENCE & CONTINUATION
Inspect what happened.
Retain the available decision and execution evidence. Witness provenance is a separate layer with its own inputs and limitations.
USEFUL BOUNDARIES
Built to be inspected,
including the limits.
Self-hosted means an operating responsibility. Deployment, providers, access control and costs need concrete configuration.
Recorded means recorded. The public explorer does not execute an agent, issue permissions or connect you to a live pilot.
Integration is specific. A demonstrated path is evidence for that path, not a general security certification or proof of all workloads.
A thoughtful service layer,
when it’s ready.
Managed pilot operations, team administration and support or recovery assistance are proposed commercial directions. There is no paid checkout, team-tenancy platform, enterprise SSO or service-level commitment on offer here.
The private Mothership core and existing DeadBolt / Witness projects retain their separate licensing boundaries. A future offer does not change existing recipient rights.