Open technical foundations. Focused commercial assurance.

VerShep is the company and master brand. CPF is the technical assurance substrate; DEP and VerShep Assurance turn that foundation into product experiences and focused solutions.

Technical framework

Contextual Pipeline Framework

The technical assurance substrate for source authority, bounded work, evidence, verification, and Human acceptance.

CPFCurrent foundation

VerShep product

Digital Entity Platform

A CPF-based product built by VerShep for Entity creation, bounded goals, supervision, evidence review, continuity, and accountable outcome history.

DEPPublic Early Access

Commercial platform

VerShep Assurance

The commercial product and service system that turns CPF and DEP capabilities into focused customer paths.

VerShepPublic product system

Framework boundary

CPF is not being renamed as a marketing product.

CPF remains the Contextual Pipeline Framework. VerShep Assurance is the commercial system built on CPF; DEP is VerShep's CPF-based Digital Entity Platform product.

CPF and DEP are stewarded by VerShep, LLC. Existing third-party contributions and dependencies remain governed by their applicable licenses; this relationship does not retroactively change contributor rights.

Public agent and developer surface

Inspect current products in human-readable and machine-readable form.

Current foundation

CPF contracts and guards

Existing framework doctrine includes source authority, bounded work, verification evidence, and Human review semantics.

Public now

Machine-readable catalog

Humans and agents can inspect current status, prices, boundaries, and conversion URLs through /api/catalog and /llms.txt.

Read-only beta

Public MCP endpoint

Connect an MCP client to https://vershep.com/api/mcp to discover the public catalog and choose a conversion path. The endpoint performs no purchase, submission, mutation, or customer-system access.

MCP endpoint

https://vershep.com/api/mcp

Protocol baseline

2026-07-28; legacy compatibility retained

The public read-only endpoint supports the stable 2026-07-28 stateless protocol baseline while retaining declared legacy handshake compatibility. It performs no purchase, submission, customer-system access, or mutation.