PTPGE Ready

The mark a piece of software may carry when it handles the specification correctly for the roles it claims — nothing more. Self-checked against public vectors, free, bound to a version. Held by PTPGE, not by any implementation.

What it says

«This software computes, validates, resolves, carries or writes ptpge-cfs/1 identities and the five documents correctly for the roles named.» It does not say the print is good, that any marketplace endorses the tool, or that the vendor is a partner. That neutrality is what lets a competitor of any implementation carry the same mark — and what makes the specification a specification.

Five roles

Compute — produce the canonical string and sha256 for the profiles spec, request and offer (offer = request + variables/order/vendor), byte-identical to the vectors. Validate — recompute and refuse on mismatch; never case-fold or accept a non-64-hex value. Resolve — look up /f/<sha256>, handle hit, miss and superseded explicitly; never invent a product for a miss. Carry — pass a fingerprint through unchanged, request → quote → order → job. Write — emit a vendor declaration, request or quote that passes the document validator (schema, vocabulary, identity).

Rules for every role

Declare the cfs version you conform to — the mark is version-bound. Treat a fingerprint as opaque 64-character lowercase hex; never change case, whitespace or encoding. Fail closed — refuse or flag rather than guess. Never claim validity for an unresolved fingerprint. Fingerprints are permanent: a historical one is superseded, never invalid.

Check yourself

Vectors: vectors-cfs1.json — inputs with the expected canonical strings and hashes for spec, request and offer, plus a request/1 and a quote/1 that validate. Documents: POST mcp.ptpge.org/validate-document with the document as body (or the MCP tool ptpge_validate_document) returns valid, errors and warnings. Configurations: POST mcp.ptpge.org/validate and /fingerprint. A live domain: ptpge.org/check. Nothing you send is stored.

How to carry the mark

Run your software against the vectors for the roles you claim. Send a short report to post@ptpge.org: tool, version, roles, vector-pack version, result. PTPGE lists it in a public register on this page. Free. Shown as «PTPGE Ready — cfs/1 (Compute, Write)». Revocable on drift or false claim; re-confirmation only at a major specification version. Audits only on dispute.

Register

No software has been listed yet. The reference implementations — the open MCP server (org.ptpge/mcp-server) and tools/fingerprint.py in the specification repository — pass all vectors and are the source the vectors are minted from, so they are not listed as conformant; they define conformance.