Where Summit sits, how the thirty days run, what a Decision Receipt actually contains, and how a proven pilot becomes a partnership. Pair these with the interactive demo.
1 · Where Summit sits
Summit runs beside your DevOps platform. It reads consequential agent events over an outbound, read-only connection, and seals them into a signed chain. Nothing is installed into your assistant, your runners, or your repos; nothing flows inbound; no source code leaves.
signed / verifiable pathtrust boundarydecision metadata only — no source code, nothing inbound
2 · How it goes in
Five phases. Each has one exit gate you can see. The first real receipt from your own flow lands in the first three days.
3 · The 30 days, by owner
Who does what, week by week. Access work is deliberately yours — the DevOps platform-certified engineers running the platform steps is the implementer-enablement half of a partnership.
4 · What a Decision Receipt proves
A log says what happened. A receipt proves it — the evidence, the alternatives ruled out, the authority — and each field answers an assessor's control question.
Three ways to emit receipts — pick per surface, mix freely. An agent skill the agent loads, the Summit MCP server registered as an agent/Claude Code tool client, or direct REST from CI. All land in the same signed chain. Modern code assistants speak MCP and run external agents, so the integration surface is there today.
REPRESENTATIVE — exact skill name, MCP tool signatures & API schema confirmed at kickoff
① Agent skill — in the agent / Claude Code flow
// after the agent completes a consequential step
use skill: summit-decision-receipt
action: "merge(!991 → release/2026.07)"
evidence: [pipeline #48214, approval:maria.v]
ruled_out: "merge on stale approval"
authority: "policy R7 — guarded merge"
→ returns receipt_id + chain head
② Summit MCP server — registered as an agent/Claude Code MCP client
# .mcp.json — add Summit alongside the agent's other tools
{ "mcpServers": { "summit": {
"url": "https://mcp.summitcognitive.ai",
"auth": "Bearer ${SUMMIT_PILOT_TOKEN}" } } }
# the agent then calls, mid-flow:
summit_register_decision(action, evidence, authority)
summit_attach_evidence(receipt_id, artifact_refs)
③ REST API — straight from a CI job
POST https://decrec.summitcognitive.ai/v1/receipts
Authorization: Bearer $SUMMIT_PILOT_TOKEN
{ "action":"deploy: promote(release → prod-east)",
"decision":"ESCALATED",
"evidence":["window 08:00-18:00 ET; now 18:35"],
"authority":"policy R9 — human auth required" }
# anyone verifies, no auth, no trust needed:
GET https://decrec.summitcognitive.ai/v1/chain/audit
6 · Pilot → partnership
The pilot is the on-ramp. Once one flow proves out, the platform team attaches receipts to assistant rollouts, compliance-bound customers get evidence they can't get anywhere else, and each delivered customer becomes the proof for the next.