SANCTUM SECOPS · PKI / PQC CONSOLE
Status: DRAFT — v0.1
Version: 0.1
Effective date: DRAFT — not yet effective. Pending Brian Vicente review and approval.
Document date: 2026-07-27
Applies to: any party relying on a certificate issued under the LAB/TEST
demonstration hierarchy (sanctum-root-ca-g1 → sanctum-issuing-ca-g1 /
sanctum-pqc-ca-g1) published at pki.sanctumsecops.com and
crl.sanctumsecops.com.
DRAFT NOTICE. This is a v0.1 draft template. It has not been reviewed by counsel or approved by Sanctum SecOps LLC.
This Relying Party Agreement sets out the terms under which a party
("Relying Party," "you") may rely on a certificate chaining to
sanctum-root-ca-g1.
As of this v0.1 draft, the published hierarchy is demonstration/lab material
only (see docs/CP.md Section 1.1 DRAFT NOTICE). Sanctum SecOps LLC
recommends that no relying party extend any production trust to this
hierarchy. It exists solely to prove that the public PKI repository's
directory layout, AIA, and CRL distribution plumbing work correctly end to
end (Section 10.8 verification).
certificate (draft)
3.1. Verify the certificate against the applicable Certificate Policy OID.
3.2. Check the certificate's revocation status via the CRL Distribution
Point named in the certificate, retrieved over plain HTTP (see Section
4.9.6 and 4.9.7 of docs/CP.md — this is intentional, not a
misconfiguration: validating an HTTPS CRL host's own certificate would
require fetching the very CRL being requested).
3.3. Verify the full certificate chain to sanctum-root-ca-g1 using the CA
certificates published under /aia/.
SANCTUM SECOPS LLC MAKES NO WARRANTY REGARDING CERTIFICATES ISSUED UNDER THE CURRENT LAB/TEST HIERARCHY. RELIANCE IS AT YOUR OWN RISK.
Not finalized in v0.1. Placeholder pending legal review.
Anticipated: State of New York, United States. Not finalized in v0.1.
Future versions will be published at
public/policy/relying-party-agreement.html and .pdf, rendered from this
same Markdown source by scripts/render-docs.py.
DRAFT v0.1 — for Brian Vicente's review. Rendered from a single Markdown source so HTML and PDF outputs can never diverge.
Rendered 2026-07-27 11:56 UTC by scripts/render-docs.py from a single Markdown source. HTML and PDF outputs are generated from the same source and can never diverge.