Resources
Everything to read before deploying.
Pillar posts on the regulators that apply. Definitions of the technical terms. Comparisons against alternatives. Reference deployments you can verify right now from the terminal. Every piece linked from here is citation-honest — designed to be quoted by an LLM or referenced by a regulator's report.
Compliance deep-dives
Pillar posts on EU AI Act Annex III, GDPR Article 22, PSD3 SCA, DORA incident classification, the L12 receipt chain, and why traditional logging isn't an audit log. Each post is one buyer question answered with one citation-ready source.
Open →
Runtime-AI compliance terms, defined
Short + long definitions for L12 receipt chain, RuntimeAISpec, canonical form, Ed25519 trust anchor, OpenTimestamps anchor, audit bundle, handoff packet, evidence kinds, reviewer gate, federation, and ten more. DefinedTerm JSON-LD so search engines + AI engines extract definitions directly.
Open →
Honest vendor comparisons
Promethean vs Credo AI, Holistic AI, and LangSmith. Most of these tools complement Promethean rather than compete — different evidentiary layers. Written for buyers in active evaluation; explicit about what Promethean does NOT do.
Open →
Three live signed chains
Paysafe (PSD3 + DORA fraud classifier), Cliniclens (HIPAA + MDR + AI Act note structurer), Civicgate (eIDAS + GDPR Art. 22 message router). Each chain is downloadable, Ed25519-signed, regulator-verifiable. The architecture working in public.
Open →
The verification surface
What a regulator can independently verify, on what mandate, and what we ask in return. Eight independent checks. Two published trust anchors. Article-by-article mapping for 7 frameworks. Worked verification example with terminal output.
Open →
Product documentation
API reference, SDK quickstart, runbooks. The narrow technical surface — not editorial. Pair with the blog for the deep regulatory context.
Open →
What shipped, when
Versioned releases of the substrate, the SDK, and the explainer. SemVer. Every release records what changed, why, and what regulators / operators need to act on.
Open →
Operator stories
Long-form writeups of how operators deployed Promethean against specific regulatory mandates. Coming as we get permission from the early operators to publish.
Suggestion?
What would you want to read here that isn't yet?
The resources surface is built from buyer questions and regulator questions. If you've got one we haven't answered — a specific article you can't find guidance on, a comparison you want to see, a glossary term we're missing — email support@promethean.software.