PlenaProof is the proof, receipt, review, escalation, and continuity layer around existing institutional systems. Each suite has a slim core of two to three platforms and recommends diagnostic modules as the workflow reveals deeper risk. Fourteen platforms sit underneath, surfaced when the workflow needs them.
Slim core. Strong diagnostic modules. Live proof workflows. Other platforms come in as diagnostic modules when the workflow reveals deeper risk.
AI can act. PlenaProof proves who authorized, reviewed, refused, corrected, and accepted responsibility. d19.104 adds a buyer-facing enterprise layer for AI agents, vendors, incidents, board/regulator packs, public trust portals, insurance evidence, and ProofOps.
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.
PlenaProof proves.
PlenaProof records what actually happened.
PlenaProof proves who reviewed, accepted, rejected, appealed, or sealed the decision.
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.
Institutional suites become stronger when they are backed by issuers, named reviewers, refusal receipts, legal opinion planning, case studies, academic defensibility, and a wallet build path.
PlenaProof provides the buyer-facing layer institutions need before procurement: Command Center, Verified Organization Registry, Badge/Widget, Trust Center, Pricing, and suite-specific pilot paths.
Cases, receipts, deadlines, readiness, audit packs, and buyer-specific dashboard language.
RegistryPublic institution profiles, trust levels, selected verification metadata, and badge readiness.
BadgeA visible PLENA trust signal institutions can place on their own websites.
TrustReceipts travel; databases stay home. Clear AI, privacy, review, and non-advice boundaries.
PricingFounding pilots, monthly institutional plans, enterprise/API pricing, and per-case add-ons.
PilotConvert interest into a defined pilot with buyer, use case, volume, workflow, and next action.
Eight suites. Each suite has an anchor, slim core of two to three platforms, recommended diagnostic modules, and a named deliverable.
Four platforms — DIGITA, TEMPORA, DETECTA, ASCENDA — do not headline any suite. They anchor specific diagnostic recommendations across suites and are first-class, not passive add-ons. PlenaProof diagnoses hidden institutional risks on the buyer's behalf and recommends the right module when the workflow reveals that risk.
Choose the institutional need. PlenaProof suggests the strongest core platforms, recommended diagnostic modules, and the buyer-ready output.
The new standalone suite pages are now direct buyer doors. Each page explains the buyer, 30-day pilot, platform route, sample output, and truth boundary.
Institutional Proof Packet
VERITA + ORIGINA + CONSERVACounterparty Due Diligence Record
COMMERCIA + VERITA + PROVASealed Cross-Border Document Packet
SIGILLA + VERITA + ASCENDAHuman Review & AI Decision Audit Pack
AEQUITA + PROVA + CONSERVAAppeal & Evidence Readiness Pack
PROVA + AEQUITA + LEGIBLAInstitutional Continuity Report
CONSERVA + FORTIA + TEMPORAHuman Service Encounter Receipt
VERITA + CONSERVA + PROVAPublic Service Journey Receipt
NAVIGA + VERITA + TEMPORACore platforms: VERITA ORIGINA CONSERVA
Diagnostic modules: PROVA challenge-readiness · SIGILLA sealing & cross-border · TEMPORA timing & expiry
Suggested workflow: one credential or claim moves from submission to review to verification-readiness receipt.
Buyer-ready output: Institutional Proof Packet.
VERITA assesses consistency, completeness, and plausibility of submitted documentation. It does not verify document authenticity and cannot access government databases, university registries, or official verification systems unless such integrations are later established. Reports are structured credibility assessments, not legal determinations, forensic audits, or government-grade identity verification.
A repeatable path from submission to verification-readiness receipt, with diagnostic modules surfaced as the workflow reveals risk.
Applicant credential intake, staff credential audit, NGO/donor evidence packet, church/ministry credential packet, student/researcher packet, or supplier trust packet.
VERITA captures the controlled intake and credibility assessment. ORIGINA supports authorship, origin, and attestation. CONSERVA supports preservation and record continuity.
If the case may be challenged: PROVA. If it crosses jurisdictions or needs sealing: SIGILLA. If timing or expiry matters: TEMPORA. PlenaProof recommends these as the workflow reveals deeper risk.
Institutional Proof Packet: gaps, flags, next official checks, recommended modules, and bundle-specific next steps, without claiming official document authentication.
This lightweight form helps sell the pilot conversation. For saved cases, use the full VERITA Institutional Intake endpoint when the backend is installed.
Helps institutions make complaints, appeals, evidence packets, refusal decisions, and escalation paths more reviewable and defensible.
Institution chooses the suite → selects the case type → the slim core handles the workflow → diagnostic modules surface where the workflow reveals risk → the institution receives an Appeal & Evidence Readiness Pack.
Not a law firm. Not legal representation. Not a substitute for licensed legal advice. Not an emergency service. Does not make final legal determinations.
Core platforms: PROVA evidence & dispute · AEQUITA fairness & appeal · LEGIBLA rights & readability
Diagnostic modules: TEMPORA deadlines & appeal windows · CONSERVA survival through investigation or audit · SIGILLA final-packet sealing or cross-border evidence · FORTIA institutional resilience & risk preparation
Suggested workflow: one complaint, appeal, or evidence packet becomes defensible.
Buyer-ready output: Appeal & Evidence Readiness Pack.
Rights complaint intake, appeal preparation, workplace grievance packet, fraud/scam concern, refusal decision, AI decision review, or evidence organization for an unfolding dispute.
PROVA carries evidence-and-dispute. AEQUITA carries fairness-and-appeal. LEGIBLA carries rights-and-readability. Three cores reflect the suite's breadth across rights, risk, and protection.
TEMPORA for deadlines and appeal windows. CONSERVA for audit-trail survival. SIGILLA for sealed packets or cross-border evidence. FORTIA for institutional risk preparation. PlenaProof recommends these as the workflow reveals deeper risk.
Appeal & Evidence Readiness Pack: gaps, flags, deadlines, appeal routes, and recommended next steps, without giving legal advice, representing a client, determining liability, or replacing licensed professionals.
A focused pilot form for institutions that need an appeal, evidence, refusal, or escalation-readiness workflow. Output: Appeal & Evidence Readiness Pack.
Four platforms don't core any single suite — they enter as recommended modules across multiple suites when the workflow reveals deeper risk. ASCENDA surfaces when credentials, mobility, recognition, advancement, student records, professional readiness, migration pathways, or cross-border opportunity are involved. DIGITA surfaces when digital access, platform access, account evidence, online presence, or digital identity context matters. DETECTA surfaces when scam, anomaly, synthetic-content, or fraud signals appear on submitted material. TEMPORA surfaces whenever deadlines, expiry dates, appointments, appeals, renewals, evidence windows, reporting windows, or escalation timing matter.
Core platforms: COMMERCIA VERITA
Diagnostic modules: PROVA dispute-readiness · CONSERVA audit-trail continuity · SIGILLA cross-border or formal sealing · TEMPORA deadlines & renewals · DETECTA fraud & synthetic-content signals · LEGIBLA plain-language review of terms
Suggested workflow: one supplier, partner, donor, vendor, or counterparty becomes a due-diligence record.
Buyer-ready output: Counterparty Due Diligence Record.
The suite is a Partner & Supplier Due Diligence Portal, not a marketing grouping.
Commercial workflow, supplier or partner profile intake, business-readiness framing, and counterparty context.
Credibility, completeness, and plausibility review of submitted claims and documentation summaries. Does not officially verify authenticity.
PROVA for dispute-readiness. CONSERVA for audit-trail continuity. SIGILLA for cross-border sealing. TEMPORA for renewals. DETECTA for fraud signals. LEGIBLA for plain-language terms review.
Counterparty Due Diligence Record: structured packet for AML/KYC review, donor due diligence, vendor onboarding, or partner review — without legal advice.
PlenaProof organizes submitted information, evidence packets, readiness gaps, and preservation structure. It is not a law firm, not tax or accounting advice, not official supplier certification, not sanctions screening, not procurement approval, and not a forensic audit.
Core platforms: SIGILLA VERITA
Diagnostic modules: ASCENDA credential recognition / mobility · TEMPORA deadlines & appointments · CONSERVA durability · PROVA evidence-chain · LEGIBLA readability of terms and instructions
Suggested workflow: one document is sealed, routed, and prepared for cross-border use.
Buyer-ready output: Sealed Cross-Border Document Packet.
SIGILLA does not replace apostilles, notarization, embassies, government seals, official certification, or legal authentication. It prepares a clean, sealed, reviewable packet around the institution's records and the person's records.
Most institutions begin with a founding pilot on one use case, then grow from there as the value compounds. There is no enterprise minimum — the founding pilot is the doorway.
One cohort, limited review volume. You leave with one named output (e.g. Institutional Proof Packet) on a real workflow.
Light intake workflow, basic readiness reports. Recurring access to one suite with a monthly receipts log.
Multiple departments, recurring reports, export-ready packets. Department-scale rollout across suites with exportable audit packs each cycle.
Role permissions, integrations, higher volume, dashboarding. Integrated, role-managed deployment with API access and a named contact.
PLENA's value compounds after the first deployment. Institutional memory accumulates across staff turnover. Audit packs become easier to assemble each cycle. Public verification builds external trust over time. Certified staff carry the practice forward. Renewal, accreditation, and board reviews get cheaper because the evidence is already in place.
Ungated sector check that produces a print-ready gap note and maps the buyer to the correct PLENA suite.
Security, data-flow, DPA/MSA shell, sub-processor list, implementation checklist, and procurement-safe claims.
Staff certification, reviewer training, records officer training, and AI oversight reviewer certification create internal capability and renewal habits.
Foundation training for teams that need shared PLENA proof language, receipt literacy, and safe review boundaries.
Command Center counters should show cases handled, receipts issued, deadlines met, reports exported, and reviewer training completed.
VRX-1-style identifiers become citable in reports, exhibits, filings, accreditation packets, and public verification workflows.
Read-only reviewer access lets external auditors, accreditors, counsel, and funders inspect selected audit packs without broad database access.
Each sector below maps to the standards, regulators, and review patterns buyers already work with. These are framework references and procurement starting points, not legal advice.
| Sector | References buyers recognize | Bundle copy to emphasize |
|---|---|---|
| University | FERPA, GDPR, QAA, ENQA, CHEA, registrar records, accreditation files, NIST AI RMF, ISO/IEC 42001 | AI-era admissions human review, credential integrity, transcript verification, research-origin record, VRX-1 receipts. |
| Bank / fintech / crypto | FATF, Travel Rule, FinCEN, OFAC, FCA, EBA, ESMA, AML/KYC, vendor due diligence, NIST AI RMF | Counterparty evidence, source-of-funds binder, VASP review, human review of AI-assisted risk decisions. |
| Publisher / journal | COPE, Crossref, ORCID, DOI metadata, CRediT, ICMJE, research integrity, AI-use disclosure | Origin records, reviewer integrity packets, publication provenance, AI-use receipts, preservation receipts. |
| NGO / foundation | CHS, Sphere Standards, PSEA/safeguarding, funder reporting, beneficiary intake, program monitoring | Funder-ready evidence binders, cohort intake, service navigation, AI triage receipts, deadline exports. |
| Church / diocese | Safeguarding records, clergy credentials, school networks, archive schedules, annual administrative review | Long-term record continuity, clergy/staff packets, public trust badge, human-review log, archive receipts. |
| Tourism / hospitality / travel | Booking records, guest identity, travel readiness, refund windows, service incidents, accessibility, safeguarding | Traveler proof packets, incident/complaint records, refund and chargeback evidence, human-review receipts, public verification links. |
| Aviation / airport / airline | Passenger-rights workflows, baggage custody, crew and vendor credentials, safety review, accessibility, disruption evidence | Boarding/event receipts, baggage-chain packets, delay/cancellation evidence, safety and complaint packets, AI rebooking/triage receipts. |
| Self-driving / autonomous mobility | Event logs, geofence records, human takeover, remote operator action, maintenance, software version, incident review | Collision/near-miss evidence packets, human-review receipts, regulator/insurer exports, chain-of-custody preservation. |
| Ride-hailing / Uber-style platforms | Trip records, driver identity, licensing, fare disputes, complaints, deactivation appeals, algorithmic management | Driver/passenger proof packets, appeal-ready records, safety and accident evidence, AI decision human-review receipts. |
| Human services / personal care | Credential checks, service receipts, consent, field notes, safeguarding, complaint pathways, human presence, non-clinical support boundaries | Provider and recipient proof packets, human service receipts, human presence receipts, refusal receipts, complaint/appeal-ready records. |
| Legal aid / immigration support | Deadline tracking, document readiness, referral boundaries, evidence packets, privacy rules, court/agency filing rules | Case-readiness support, AI summary receipts, deadline exports, and strict boundary that PlenaProof is not a law firm. |
Sector-specific entry points into AI-era institutional proof: trust, governance, human review, public verification, sector-specific records, travel occurrence, aviation custody, and mobility accountability.
Admissions, registrar, accreditation, research-origin, and international-credential proof workflows.
Safeguarding, clergy/staff records, school networks, annual review, and archive continuity.
Beneficiary evidence, donor reporting, safeguarding, program continuity, and case packets.
Document readiness, deadlines, referrals, evidence packets, and non-lawyer boundaries.
KYC, AML, source-of-funds, VASP/vendor review, and human-review receipts.
Authorship, peer review, DOI/ORCID metadata, AI-use accountability, and preservation receipts.
Hiring, staff credentials, training records, AI screening receipts, and appeal-ready records.
Public records, procurement, benefits, national ID/passport readiness, and central services.
Bookings, guest identity, travel readiness, service incidents, refunds, and complaint proof packets.
Passenger events, baggage custody, crew/vendor records, safety review, and disruption evidence.
Self-driving event logs, human takeover, consent, incident packets, and accountability records.
Trip occurrence, driver identity, passenger complaints, fare disputes, and deactivation appeals.
Caregiving, tutoring, coaching, chaplaincy, interpretation, home service, consent, service receipts, and complaint pathways.
Documents when AI was used, who reviewed the output, what was accepted or rejected, what was escalated, and what receipt or audit trail was produced. Anchored by the named-human-reviewer infrastructure and the VRX-1 Human Review Receipt.
Core platform: AEQUITA — the fairness, bias, appeal-rights, and AI-assisted-decision-making anchor.
Diagnostic modules: PROVA challenge-readiness · CONSERVA audit-trail survival · LEGIBLA AI policy & notice readability · DETECTA synthetic-content & AI-output risk signals
Suggested workflow: one AI-assisted decision receives human review, refusal/appeal path, and audit trail.
Buyer-ready output: Human Review & AI Decision Audit Pack.
Register systems, purpose, owner, jurisdiction, vendor, risk tier, human-review requirement, and related VRX-1 receipts.
Record who reviewed an AI output, what changed, why it was accepted or escalated, and which policy or right was involved. Reviewer name or role, review scope, date and time, evidence reviewed, decision made, reason, appeal or correction path, receipt generated.
Capture disputed outcomes, security incidents, model errors, evidence packets, deadlines, and required follow-up.
An institution can say we did not reject you arbitrarily; here is the documented reason, the missing item, and the correction or appeal path.
Track staff completion of practical AI literacy, policy awareness, appeal routing, and incident-escalation training.
Every AI-facing workflow states whether it is policy support, legal information, verification support, or professional referral.
PlenaProof does not certify AI systems or provide legal compliance guarantees. It helps institutions document review, accountability, and decision trails. Where the workflow is frontend-only, the page calls it a preview, sample workflow, or model record — never a live audit trail unless one exists.
Core platforms: CONSERVA durable records · FORTIA institutional resilience
Diagnostic modules: TEMPORA renewals / expiry / reporting windows · VERITA identity context attached to records · PROVA challenge-readiness of continuity records · SIGILLA sealed institutional transfer or handover
Suggested workflow: one institution's record set survives staff turnover or leadership change with full reviewability.
Buyer-ready output: Institutional Continuity Report.
Outgoing leadership or staff hand over a structured record set with attached identity context, preservation metadata, and recommended renewal dates.
Records survive donor review, board review, accreditation review, regulatory inquiry, or legal review with chain-of-custody intact.
Critical records remain reachable through disruption, displacement, infrastructure loss, or leadership crisis.
Receipts travel; databases stay home. PlenaProof does not silently share information with external or private systems. References happen by manual import, QR/verification link, or permissioned enterprise API for selected receipts only.
Core platforms: VERITA provider / service context · CONSERVA durability of encounter record
Diagnostic modules: PROVA challenge-readiness · TEMPORA follow-up dates / escalation · LEGIBLA service terms & consent language · SIGILLA sensitive handover
Suggested workflow: one human service encounter becomes a documented service receipt.
Buyer-ready output: Human Service Encounter Receipt.
Provider identity context, care interaction record, consent, follow-up obligations, complaint pathway.
Encounter receipt for tutoring sessions, coaching meetings, pastoral support, interpretation, or home services.
Sensitive handover from one service provider to another with sealed packet preparation where needed.
PlenaProof does not license professionals, guarantee service quality, replace authorities, or provide legal, medical, financial, immigration, or therapeutic advice unless a qualified professional is separately involved.
Core platforms: NAVIGA guided routing · VERITA applicant & document context
Diagnostic modules: TEMPORA appointments / expiry / correction windows · CONSERVA long-term service-continuity records · PROVA challenge-readiness · SIGILLA sealed handover / cross-border packets
Suggested workflow: one citizen journey becomes a public-service continuity receipt.
Buyer-ready output: Public Service Journey Receipt.
What was submitted to the agency, when, by whom, with what supporting documents, and what receipt was given.
What was flagged as missing or incorrect, what was corrected, what was escalated, and what deadlines apply to the next step.
What was handed over to the citizen, to the next agency, or sealed for cross-border use.
Truth boundary. PlenaProof does not issue identity documents, passports, visas, or official government records. It does not access government identity databases, does not connect to live government systems unless a specific authorized integration exists, and does not perform biometric verification. It helps document the service journey around official documents. National ID systems prove who a person is. PlenaProof proves how the identity service was handled.
A receipt grammar for PLENA verification records. It supports controlled interoperability without database consolidation and makes verification open while creation, management, and high-assurance registry services remain paid or permissioned.
Export JSON/PDF from one PLENA workflow and upload or cite it in another selected workflow. Safest first implementation.
A QR code or receipt URL verifies one selected receipt, not an entire account or database.
Permissioned API verification with role-based access, expiry, logging, and no broad system-wide sync.
The suites guide institutional buyers. The full platform directory remains available.
Institutions buy outputs, not platforms. Each of the eight suites produces one named, buyer-ready output. Sector buyers map to the suite whose output most directly reduces their procurement risk.
| Suite | Buyer-ready output | Common sector buyers |
|---|---|---|
| 1. Institutional Trust & Proof | Institutional Proof Packet | Universities, publishers, churches, employers, NGOs |
| 2. Partner Trust & Due Diligence | Counterparty Due Diligence Record | Banks, fintech, crypto, NGOs, employers, foundations |
| 3. Cross-Border Proof & Sealing | Sealed Cross-Border Document Packet | Universities, immigration support, churches, NGOs, government |
| 4. AI Accountability & Human Review | Human Review & AI Decision Audit Pack | Universities, employers, banks, government, ride-hailing, autonomous mobility |
| 5. Rights, Risk & Protection | Appeal & Evidence Readiness Pack | Legal aid, NGOs, employers, universities, churches |
| 6. Institutional Continuity | Institutional Continuity Report | Churches, NGOs, foundations, universities, government |
| 7. Human Service Trust Layer | Human Service Encounter Receipt | Human services, tourism, aviation, legal aid, NGOs |
| 8. National ID / Public Service Continuity | Public Service Journey Receipt | Government, immigration support, legal aid, diaspora organizations |
Human Review Receipts, AI Harm Defense, AI Agent Action Receipts, and Proof of Human Agency let individuals and institutions document who acted, who reviewed, who approved, and what evidence was available.
The strongest primitives for individuals and institutions: Proof Yearbook, agent authorization, author provenance, issuer portal, insurance wedge, standards engagement, refusal publication, and the 100-year commitment.
Each institutional suite routes into an evidence binder, sample receipt, public verification result, issuer pilot kit, and reviewer workflow.
The six gating receipt types of the VRX-1 catalogue (d19.75 lock, Part 3) each have a working reference implementation that builds, verifies, and saves receipts entirely client-side. All six follow the same canonical-JSON SHA-256 integrity model and the same self-attested truth boundary. The consolidated schema page lists every type with its schema_version constant, receipt_id pattern, required fields, and published schema JSON.
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.
PlenaProof should not become dozens of disconnected SaaS products. The d19.108 foundation adds a shared proof engine, global trust map, receipt builder, evidence packet builder, verification preview, export center, pilot centers, demo room, and VRX-1 universal receipt standard.
Use the market-readiness center to move from buyer pain to sector demo, proof builder, evidence packet, verification preview, procurement answers, and pilot proposal.
The coverage ledger records the sector universe, platform crosswalk, built surfaces, and live-test boundary before broad deployment testing.
The outreach pack narrows the pitch to buyer pain, small pilots, demo routes, and proof outputs for the strongest early markets.
Eight sector packs translate the shared engine into enterprise, finance, public integrity, justice, health and safety, faith, university, and community proof demos. This keeps PLENA unified while making every serious trust institution see its own accountability problem.
d19.110 repairs inherited inline JavaScript breakage in four platform pages, upgrades duplicate-ID and local-link validation, and adds a practical site-health page for post-deployment testing before pitching buyers.
d19.111 adds a buyer room, procurement-readiness answers, and a risk-readiness calculator so the ProofOps engine can be explained safely to enterprises, banks, insurers, public bodies, justice institutions, churches, and universities.