Skip to content

Design Partner Pilot Pack

Why this page exists. SecurityRecipes already has the artifacts a serious buyer wants to inspect. The next step is proving that those artifacts can run inside a customer pilot, produce telemetry, validate a paid wedge, and support a credible hosted MCP business.

SecurityRecipes is positioned as The Secure Context Layer for Agentic AI. That claim becomes materially more valuable when a design partner can answer four questions quickly:

  • Which agent workflow are we piloting?
  • Which private context and MCP controls are in scope?
  • Which telemetry proves security and ROI?
  • Which paid product wedge is this pilot validating?

The Design Partner Pilot Pack turns those questions into a generated artifact. It does not claim recurring revenue exists yet. It defines the motion required to prove it.

What was added

  • data/assurance/design-partner-pilot-profile.json - source-backed pilot profile for buyer segments, phases, telemetry, success metrics, paid wedges, pricing guardrails, diligence questions, and risk gates.
  • scripts/generate_design_partner_pilot_pack.py - deterministic generator and --check validator for CI drift detection.
  • data/evidence/design-partner-pilot-pack.json - generated pack with source-pack hashes, readiness score, phase gates, wedge proof states, telemetry requirements, and diligence answers.
  • recipes_design_partner_pilot_pack - MCP tool for the full pack, a buyer segment, pilot phase, monetization wedge, metric, diligence question, or pilot risk.

Run it from the repo root:

python3 scripts/generate_design_partner_pilot_pack.py
python3 scripts/generate_design_partner_pilot_pack.py --check

What the pack contains

SectionPurpose
pilot_summaryReadiness score, decision, source-pack readiness, phase count, wedge count, metric count, and failure count.
buyer_segmentsFrontier model lab, AI platform vendor, security platform vendor, and regulated enterprise views.
pilot_phasesQualify, bind private context, run read-only MCP, govern controlled actions, and prove the renewal case.
success_metricsReceipt completeness, context hash coverage, MCP decision coverage, reviewer time saved, automation success, safe holds, replay, private context, and renewal intent.
monetization_wedgesHosted MCP policy, private context registry, connector drift, run-receipt vault, trust-center API, and continuous eval replay.
telemetry_requirementsMetadata-first telemetry events and prohibited data classes.
risk_registerPilot risks with hold, deny, or kill decisions.

Why this is acquisition-grade

The site already has open knowledge, generated evidence, and a production-oriented read-only MCP server. The missing enterprise proof is customer pull.

This pack makes that proof testable:

  • The open layer stays useful and forkable.
  • The pilot binds private context, telemetry, and customer evidence.
  • The paid wedge is explicit before implementation expands.
  • Synthetic ROI is labeled as assumption-based until customer telemetry replaces it.
  • The pilot can stop safely on token passthrough, approval bypass, unsafe model routing, raw secret capture, or connector drift.

That is the right path toward a credible $10-20M outcome: design partners first, hosted MCP controls second, renewal evidence third.

MCP examples

Inspect the full pilot pack:

recipes_design_partner_pilot_pack()

Inspect the regulated-enterprise buyer view:

recipes_design_partner_pilot_pack(segment_id="regulated-enterprise")

Inspect the hosted MCP policy wedge:

recipes_design_partner_pilot_pack(wedge_id="hosted-mcp-policy-plane")

Inspect the controlled-action phase:

recipes_design_partner_pilot_pack(phase_id="govern-controlled-actions")

Industry alignment

The profile is grounded in current primary sources:

See also