PLENA Institutional Suite

Institutional Trust & Proof Suite

For universities, employers, professional bodies, credentialing organizations, publishers, NGOs, and any institution that needs identity context, authorship and origin proof, and durable record continuity around the credentials, claims, and evidence they intake.

View suite workflowOpen VERITAOpen ORIGINAAI OversightRequest pilotPricing

AGI-era buyer language

Credential intake · authorship and origin · durable records · verification readiness

  • AI can fabricate transcripts, ID photos, reference letters, draft essays, and credentialing documents. Institutions need a reviewable proof layer that survives the moment of intake.
  • Authorship and origin are now the scarcer good: ORIGINA documents who created what before any AI was involved.
  • Verification readiness is more useful than a single static certificate: receipts let later reviewers re-check context without re-running the whole intake.

Named standards, regulators, and references

Examples for buyer recognition and checklist design. Confirm the applicable jurisdiction before treating any reference as binding.

  • ISO/IEC 17024 personnel certification and ISO 19011 audit references where applicable
  • Education credential evaluation: NARIC, ENIC, WES, AACRAO references where applicable
  • Lisbon Recognition Convention and the Groningen Declaration on digital student data portability
  • Publishing and peer-review integrity standards (COPE, ICMJE) where applicable
  • Professional body codes of practice and continuing-education obligations where applicable
  • GDPR, FERPA, and applicable national education and employment data-protection rules
  • NIST AI RMF and ISO/IEC 42001 as AI governance references

Suite-specific PLENA proof workflow

Universal institutional flow: Intake → Review → Receipt → Escalation → Archive. The goal is not to replace official systems. The goal is to prove who acted, who reviewed, what evidence existed, what changed, and how the record can be verified or preserved.

Intake: open the credential, claim, or evidence file in VERITA with submitted documents, named issuer context, and intake metadata.
Review: attach ORIGINA authorship/origin notes where authorship matters, and PROVA evidence-readiness packets where the claim may be challenged.
Receipt: issue the Verification-Readiness Receipt and, when AI assists triage, an AI Oversight Receipt anchored to the named human reviewer.
Escalation: TEMPORA tracks any deadline windows for additional documents, appeals, or renewals; SIGILLA seals the packet when cross-border or formal handover is required.
Archive: preserve the full intake-and-review record in CONSERVA with selected VRX-1 public-verification links for external reviewers.

Recommended PLENA route

VERITAORIGINACONSERVAPROVASIGILLATEMPORA

Open Verify, Paid Create: public verification can be open, while creation, management, renewal, preservation, staff training, registry controls, and audit exports remain paid or permissioned services. Buyer-ready output: Institutional Proof Packet.

Open VERITAOpen ORIGINAOpen CONSERVAAI OversightOpen procurement packPublic VerifyAll institutional suites

Front-end preview output

{ "suite": "Institutional Trust & Proof Suite", "cores": ["VERITA", "ORIGINA", "CONSERVA"], "diagnostic_modules": ["PROVA", "SIGILLA", "TEMPORA"], "buyer_ready_output": "Institutional Proof Packet", "workflow": "Intake -> Review -> Receipt -> Escalation -> Archive", "boundary": "Preview workflow only; not legal advice, not official certification, not live registry unless implemented." }

Buyer pilot, sample output, and platform flow

A buyer should see the use case, the output, and the PLENA route in one glance. This section keeps the suite practical without claiming official verification or live registry status.

Best-fit buyers

University admissions officeEmployer credential deskProfessional bodyPublisherNGO credential intake teamResearch or grant office

30-day pilot package

30-day proof-packet pilot: credential intake, origin note, verification-readiness receipt, escalation rule, and preserved audit record.

Suite-to-platform flow

VERITA → ORIGINA → CONSERVA → PROVA → SIGILLA

Each platform keeps its role. The suite shows the buyer how the route works together.

Sample output preview

{ "suite": "Institutional Trust & Proof Suite", "sample_output": "Institutional Proof Packet", "status": "sample_preview_not_live_registry", "flow": "Intake -> Review -> Receipt -> Escalation -> Archive", "platform_route": [ "VERITA", "ORIGINA", "CONSERVA", "PROVA", "SIGILLA" ], "boundary": "Front-end preview. Not official verification, legal advice, government action, or a live registry unless separately implemented and verified." }
Request this pilotCompare all suitesSee pricing path