Claude Cowork Integration

Introduction · governed external reasoning worker
Governed co-worker Remote MCP / API gateway No direct SOR access

Claude Cowork Integration Runtime

Claude is integrated as a governed external reasoning worker. bp Sphere owns context, evidence, policy, authority, replay, learning, and enterprise memory; Claude receives a redacted context pack and can only use read-only or draft-only Sphere tools.

Principle
Claude thinks. Sphere governs. Humans decide.
Access model
Context pack + MCP tools only
Action model
Read-only / draft-only by default
Replay model
Prompt + tools + output + human decision

Target architecture

The integration exposes a secure Sphere context gateway to Claude Cowork. Claude never receives raw SAP, Ariba, Databricks, ServiceNow, Outlook, or Teams access.

External reasoning worker
Claude Cowork
Research
Explain
Draft
Governed connector
Sphere Context Gateway
Identity
Role/Mission Auth
Redaction
Tool Gate
Replay Logger
System of intelligence
Sphere Runtime
Finance Ontology
Evidence Fabric
Policy Runtime
Decision Replay
Learning Runtime
SOR Adapters

1. Remote MCP

POST /mcp exposes governed Sphere tools to Claude Cowork over HTTPS. This is the production analyst/supervisor connector path.

2. Claude API

POST /api/claude-cowork/claude-api/draft-memo lets Sphere call Claude headlessly when ANTHROPIC_API_KEY is configured.

3. Claude Code CLI

For engineering automation on the NVIDIA server, use headless CLI tasks separately from business decision workflows. Repo access does not grant finance write authority.

Boundary model

LayerClaude getsSphere retains
ContextCase brief, mission, role, evidence summary, allowed toolsFull graph, raw SOR, policies, lineage, audit logs
RetrievalOnly through Sphere MCP/API toolsSAP, Ariba, Databricks, ServiceNow, Outlook, Teams adapters
ActionsDraft memo, explanation, escalation draft, test planExecute, approve, write-back, escalate, replay
MemorySession-scoped working memoryEnterprise finance memory and learning runtime
GovernanceTool permissions and redacted contextIdentity, policy, evidence, lineage, human authority

Context pack contract

What Claude receives

claude_cowork_context_pack_v1 with tenant, mission, role, selected case, business goal, facts, policy checks, evidence refs, lineage refs, allowed tools, forbidden actions, and required output schema.

What is withheld

Raw source records, unrestricted enterprise graph, direct system credentials, policy execution authority, write-back permissions, and enterprise memory mutation rights.

Data boundary: Claude receives redacted references and approved snippets. Only Sphere can retrieve raw evidence, execute authority checks, persist replay, or promote learning.

Usability pattern

Claude Cowork is useful only when it feels like a natural extension of case work. Sphere should open Claude with a selected case, a visible context card, prebuilt prompts, structured output expectations, and save/replay actions.

Context Card

Sharing with Claude: case, supplier profile, invoice/PO/receipt/prior-payment evidence refs, duplicate policy, similar prior cases, role, and authority boundary.

Authority Label

Claude Recommendation · Human Approval Required · No SAP write performed · No payment released

Deep Links

Every response points back to case, evidence pack, replay record, policy check, and similar cases in Sphere.

Consistent entry points

LocationAction labelRule
Case DrawerAsk Claude CoworkConsistent business action label
Evidence PackExplain with ClaudeConsistent business action label
Policy SectionInterpret policyConsistent business action label
Replay ViewReview decision pathConsistent business action label
Supervisor QueueDraft escalationConsistent business action label
Agent Audit PageReview agent logicConsistent business action label

Suggested prompts

#PromptPattern
1Analyze this casePrebuilt prompt, not blank chat
2Find missing evidencePrebuilt prompt, not blank chat
3Explain why this was flaggedPrebuilt prompt, not blank chat
4Compare with similar casesPrebuilt prompt, not blank chat
5Draft supplier clarificationPrebuilt prompt, not blank chat
6Draft supervisor escalationPrebuilt prompt, not blank chat
7Review agent recommendationPrebuilt prompt, not blank chat
8Review policy positionPrebuilt prompt, not blank chat

Structured output

#SectionRequirement
1FindingRequired in Claude response
2RiskRequired in Claude response
3Evidence usedRequired in Claude response
4Missing evidenceRequired in Claude response
5Policy positionRequired in Claude response
6Recommended next stepRequired in Claude response
7Human decision requiredRequired in Claude response
8ConfidenceRequired in Claude response
9Links back to SphereRequired in Claude response

After Claude responds

#ActionBoundary
1Save analysis to caseHuman-controlled post-response action
2Save as supervisor noteHuman-controlled post-response action
3Create escalation draftHuman-controlled post-response action
4Create supplier query draftHuman-controlled post-response action
5Add to replayHuman-controlled post-response action
6DiscardHuman-controlled post-response action
Operational rule: Claude output is not an action. Users save, escalate, discard, or add to replay through Sphere so governance and learning stay inside the platform.

Skill Manifest is separate from context

SKILL.md helps humans and models understand a reusable capability, but it does not share enterprise context. Sphere now exposes a governed Skill Manifest plus a selected-case Context Pack and MCP tools.

Skill Manifest

Defines what the skill is, owner, mission, authority, risk, evidence requirements, policies, tools, output schema, replay, learning, and model support.

Context Pack

Defines the selected case: facts, evidence refs, policy checks, lineage refs, similar cases, allowed tools, forbidden actions, and output schema.

MCP tools

Allow Claude to retrieve approved context and draft outputs through Sphere. Claude never receives direct SAP, Ariba, Databricks, Teams, Outlook, or ServiceNow access.

Example skillclaude_cowork.duplicate_invoice_investigator
Execution modellm_first
Authorityreason_and_draft_only
Prompt separationSkill manifest references prompt templates; it does not embed provider-specific prompt text.
Replay requiredTrue
Architecture rule: Skill Manifest + Context Pack + MCP Tools + Enterprise Memory are required for external model reasoning. A skill file alone is never sufficient context and never grants execution authority.

Remote MCP / API tools

ToolModePurpose
get_case_contextread_onlyGives Claude selected case context
get_case_summaryread_onlyReturns governed case summary
get_my_p2p_work_queueread_onlyReturns the role-scoped P2P invoice queue through the Experience API
open_invoice_detailread_onlyReturns the same P2P invoice detail contract used by the web drawer
show_invoice_evidenceread_onlyReturns the source-bound evidence stage for a P2P invoice
show_allowed_actionsread_onlyReturns action eligibility from the shared authority runtime
show_decision_replayread_onlyReturns the replay stage for a P2P invoice
search_evidence_packread_onlyRetrieves approved evidence snippets
get_policy_positionread_onlyReturns controls and authority gates
get_lineageread_onlyShows source systems, freshness, and SOR/cache status
compare_similar_casesread_onlyFinds prior outcomes and learning patterns
draft_decision_memodraft_onlyProduces structured recommendation draft
create_human_task_draftdraft_onlyDrafts Teams/Outlook escalation without sending
create_servicenow_ticketdraft_onlySubmits a governed ticket-creation intent; never writes directly to ServiceNow
open_pr_contextread_onlyShares implementation issue/code context
run_readonly_auditread_onlyRuns non-mutating audit checks

Four gates

GateRuleEnforcement
context_gateminimum required case context onlySphere-enforced before Claude receives context or tool result
tool_gateread-only tools unless draft-onlySphere-enforced before Claude receives context or tool result
authority_gateno write-back without Sphere approvalSphere-enforced before Claude receives context or tool result
replay_gatecontext, tools, output, and human decision are loggedSphere-enforced before Claude receives context or tool result

Forbidden actions

release_payment, update_sap, override_policy, approve_invoice, change_master_data, post_journal, send_supplier_message, create_source_system_write

Memory rule

Claude has session memory only. Enterprise learning and decision memory stay in Sphere.

Control rule

No payment release, SAP update, policy override, invoice approval, journal posting, or master-data change can be performed by Claude.

Implemented API shape

MethodEndpointPurpose
GET/api/claude-cowork/manifestCapability stance and governance model.
GET/api/claude-cowork/experienceRole-specific entry points, suggested prompts, output guide, save actions, and links.
POST/api/claude-cowork/context-packBuild redacted context pack for a selected case.
POST/api/claude-cowork/model-skill-contextBuild provider-neutral Skill Manifest + Context Pack + MCP tool package.
GET/api/claude-cowork/mcp/manifestRemote MCP/API connector manifest and tool list.
POST/api/claude-cowork/tool-callExecute read-only or draft-only Sphere tool contract.
POST/api/claude-cowork/draft-memoCreate decision-support memo output shape.
POST/api/claude-cowork/claude-api/draft-memoOptional headless Claude API call when ANTHROPIC_API_KEY is configured.
POST/api/claude-cowork/replayLog prompt, context pack, tool calls, output, and human decision.
GET/api/enterprise-skill-contracts/manifest/{skill_id}Inspect governed enterprise skill manifest.
POST/mcpRemote MCP JSON-RPC endpoint for Claude Cowork custom connector.
Architect message. Claude is a replaceable reasoning channel behind a governed context and tool gateway. The durable enterprise asset remains Sphere's context, evidence, policy, replay, learning, and memory layers.