Specify Work

One integration. Every handoff explained.

Connect through SDK, MCP, or webhooks. Each successful run returns the sources and policy it used.

Configure a client

The right context. A reason for every choice.

Specify turns one agent request into a current, permitted, token-efficient bundle. Open any record to inspect why it moved or stayed out.

Claude Code request ·Draft the launch narrativerequest bound
Agent requestClaude Code asks Specify for governed context7 found
Claude CodeUser → Claude Code❯ Draft the launch narrative
MCP → Specifycontext.getLaunch workspace · current permitted context
Candidate recordsFound across the workspace
Specify stepsOne governed request
MCP → Specifycontext.getLaunch narrative · Claude Code
Grantwork · memory · sourcesBudget4,440 over 2,400
Prompt-ready contextwaiting
Request bound to launch workClaude Code · Launch workspace
Inspecting · WorkApproved launch briefCurrent scope and named owner

Claude Code asks for the material allowed to support this launch task.

One contract. Successful assemblies return the same receipt shape.

CHAPTER 01

Connect in one path

Use an SDK, MCP client, webhook, or provider adapter without changing the governance model.

Claude CodePython SDK client · configuredrevocable
  • SourceWorkspace setup
  • ActorClaude Code
  • ScopeLaunch narrative · read
  • ConsequenceOne identity uses the same contract on every client path

Choose a client path without changing the governance model.

SDK

Python · TypeScript

Read and write scoped work, proposals, and context receipts.

receipt = specify.context.for_work('SW-42')
Configure this client

Connect the agent. Get the evidence back.

SDK, MCP, and webhooks share one identity, scope, source, policy, and receipt model.

Review client access

Connect once. Read the result.

Connect one client, approve its scope, and verify the returned receipt.

  1. 01Choose client
  2. 02Scope access
  3. 03Verify receipt
Configure a client Inspect Agent Memory