Eight institutional suites are now available. Pick the suite that matches the workflow — from credential intake and partner due diligence to cross-border sealing, AI accountability, rights and risk, institutional continuity, human service encounters, or public-service journeys around official documents.
What remains valuable when AI can generate almost anything: real-world proof, lawful human consent, institutional accountability, durable records, chain of custody, human review, cross-border trust, verification receipts, evidence continuity, and sealed institutional memory.
Every institutional workflow follows the same five-step shape. The suite determines the specifics; the shape stays constant.
The institution receives a submission — credential, claim, document, packet, complaint, supplier file, encounter, citizen application, or AI-assisted decision.
A named reviewer examines the submission against a defined scope and checklist. Reviewer name or role, scope, date, and evidence reviewed are captured.
PlenaProof produces a receipt describing what was submitted, who reviewed it, what was accepted or refused, and what was preserved.
Where appeal, refusal, missing-item correction, or human-review handover is needed, the path is documented and reviewable.
The packet, receipt, and decision trail survive staff turnover, leadership change, audit, dispute, and time.
A pilot should produce more than a conversation. It should map the institution to a suite, dashboard view, registry posture, badge status, pricing path, and next milestone.
Slim core platforms anchor each suite. Diagnostic modules surface when the workflow reveals deeper risk. Each suite produces one named buyer-ready output.
Slim core: VERITA ORIGINA CONSERVA
Diagnostic modules: PROVA SIGILLA TEMPORA
Workflow: one credential or claim moves from submission to review to verification-readiness receipt.
Buyer-ready output: Institutional Proof Packet.
Slim core: COMMERCIA VERITA
Diagnostic modules: PROVA CONSERVA SIGILLA TEMPORA DETECTA LEGIBLA
Workflow: one supplier, partner, donor, vendor, or counterparty becomes a due-diligence record.
Buyer-ready output: Counterparty Due Diligence Record.
Slim core: SIGILLA VERITA
Diagnostic modules: ASCENDA TEMPORA CONSERVA PROVA LEGIBLA
Workflow: one document is sealed, routed, and prepared for cross-border use.
Buyer-ready output: Sealed Cross-Border Document Packet.
Slim core: AEQUITA
Diagnostic modules: PROVA CONSERVA LEGIBLA DETECTA
Workflow: one AI-assisted decision receives human review, refusal/appeal path, and audit trail.
Buyer-ready output: Human Review & AI Decision Audit Pack.
Truth boundary: PlenaProof does not certify AI systems or provide compliance guarantees; it helps institutions document review, accountability, and decision trails.
Slim core: PROVA AEQUITA LEGIBLA
Diagnostic modules: TEMPORA CONSERVA SIGILLA FORTIA
Workflow: one complaint, appeal, or evidence packet becomes defensible.
Buyer-ready output: Appeal & Evidence Readiness Pack.
Slim core: CONSERVA FORTIA
Diagnostic modules: TEMPORA VERITA PROVA SIGILLA
Workflow: one institution's record set survives staff turnover or leadership change with full reviewability.
Buyer-ready output: Institutional Continuity Report.
Slim core: VERITA CONSERVA
Diagnostic modules: PROVA TEMPORA LEGIBLA SIGILLA
Workflow: one human service encounter becomes a documented service receipt.
Buyer-ready output: Human Service Encounter Receipt.
Slim core: NAVIGA VERITA
Diagnostic modules: TEMPORA CONSERVA PROVA SIGILLA
Workflow: one citizen journey becomes a public-service continuity receipt.
Buyer-ready output: Public Service Journey Receipt.
Truth boundary: PlenaProof does not issue national IDs, passports, visas, or government records; it documents the service journey around them.
Four platforms don't core any single suite. They enter as first-class diagnostic modules recommended across multiple suites when the workflow reveals deeper risk — recognition and mobility (ASCENDA), digital evidence (DIGITA), scam, anomaly, or synthetic-content signals (DETECTA), and deadlines and expiry (TEMPORA).
PlenaProof helps institutions become challenge-ready. When a decision is questioned by a student, client, regulator, board, funder, court, employee, journalist, parent, donor, partner, or public agency, the institution can show what was submitted, who reviewed it, what was missing, what was accepted or refused, what was escalated, and what was preserved.
One unified pilot form. Choose the suite, describe the workflow, and PlenaProof prepares a local readiness preview. If the Netlify function and Supabase table are installed, the same submission can attempt a saved intake case.
Begin with a founding pilot, learn from the buyer, then move to institution-scale plans.
One use case, one cohort
Defined suite, limited review volume, readiness report, and adoption recommendation.
Monthly
Light intake workflow, basic readiness reports, partner packets, or small cohort dashboards.
Expanded
Multiple departments, recurring reports, export-ready packets across several suites.
Custom
Role permissions, integrations, higher volume, dashboarding, and audit exports.
Locked across every PLENA institutional surface. These are not negotiable.
Verification-readiness, proof organization, receipt generation, human-review documentation, evidence continuity, diagnostic routing, sealed packet preparation, refusal receipts, and public-safe verification surfaces. PlenaProof is the proof, receipt, review, escalation, and continuity layer around the institution's existing systems — institutional memory you can prove.
PlenaProof does not issue passports, national IDs, visas, official credentials, court records, or government documents. PlenaProof does not replace universities, registrars, legal offices, compliance teams, banks, courts, governments, or regulators. PlenaProof does not provide legal advice. PlenaProof does not guarantee regulatory compliance. PlenaProof does not certify AI systems. PlenaProof does not claim formal partnerships unless they exist. PlenaProof does not replace apostilles, notarization, embassies, government seals, or official certification.
Buyers evaluating a PLENA institutional pilot can inspect the working reference receipts that the suites produce. All six VRX-1 gating receipt types have a client-side reference implementation that builds, verifies, and saves receipts entirely in the buyer's browser. Each has a published JSON schema and a worked sample receipt that round-trip verifies against the schema.
All six gating schemas in one canonical reference page.
Records that a submission was handed to a recipient (d19.69).
Returns the list of incomplete items with correction path (d19.82).
Documents who reviewed what, decision, AI-assistance (d19.81).
Institutional and Personal Refusal Receipt with reason codes (d19.81).
What must be done by when, with consequence and extension path (d19.82).
Amends a prior receipt without erasing it (d19.82).
SHA-256 fingerprints of every reference page and published schema.