PLENA Publisher & Journal AI Trust Suite
Part of the Institutional Trust & Proof Suite

Publisher, Journal & Research Integrity AI Trust Suite

For academic publishers, scholarly journals, university presses, preprint servers, and research-integrity offices that need AGI-era proof workflows for authorship, peer review, DOI provenance, and the preservation of research-of-record.

Parent suite

Institutional Trust & Proof Suite

Institutional Trust & Proof helps institutions make identity context, origin/authorship, and durable record continuity easier to review, preserve, and prepare for verification.

The buyer-ready output of this suite is the Institutional PLENA Proof Packet. Sector pages translate the suite’s workflow into the buyer’s standards vocabulary; the suite carries the underlying architecture.

Back to the eight locked suites

How sector pages relate to suites

The institutional surface is organised around eight locked suites. Each sector page lives under one parent suite and reuses that suite’s workflow, named human-reviewer pattern, and buyer-ready output. The sector page changes the vocabulary, the named standards, and the workflow language so the buyer recognises their own world.

Diagnostic modules are recommended on top of the suite’s core platforms when the workflow reveals deeper risk — not as passive optional extras.

The AGI-era proof layer

PlenaProof emphasises what AI and AGI cannot easily replace — 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.

Three lines

  • AI can generate. PlenaProof proves.
  • AI can simulate. PlenaProof records what actually happened.
  • AI can advise. PlenaProof proves who reviewed, accepted, rejected, appealed, or sealed the decision.

Challenge-ready

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.

AGI-era buyer language

Authorship · peer review · DOI provenance · research preservation

  • Authorship, contribution, and AI-use statements need origin and review trails that survive retraction request, correction, and post-publication review.
  • AI-assisted screening, translation, or peer-review summary needs a visible human reviewer of record, not an opaque output the editor cannot defend.
  • Research preservation — manuscripts, datasets, images, code, correspondence — needs continuity beyond any single platform, journal owner, or staff transition.

Named standards, regulators, and references

Examples for buyer recognition and checklist design. Confirm the applicable jurisdiction before treating any reference as binding. Not legal advice; not regulator endorsement.

  • COPE guidance and publication-ethics expectations
  • ORCID author identifiers
  • Crossref, DOI, metadata, and citation infrastructure
  • CRediT taxonomy and contribution statements
  • ICMJE authorship criteria where relevant
  • NIST AI RMF and ISO/IEC 42001 as AI governance references

Sector-specific PLENA proof workflow

Every institutional workflow follows the same universal flow shape: Intake → Review → Receipt → Escalation → Archive. The sector page translates each step into the buyer’s standards vocabulary; the underlying pattern is locked across all eight suites.

Intake. ORIGINA origin record is created for the manuscript, dataset, image, code, or creative work; contribution and AI-use statements are captured at submission.
Review. A named human reviewer of record (editor, peer reviewer, integrity officer) examines the PROVA evidence packet for revisions, permissions, and correspondence.
Receipt. A Human Review Receipt is issued when AI helps screen, summarize, translate, detect duplication, or assist review; a PLENA VRX-1 submission receipt is generated for the record.
Escalation. Retraction request, correction, authorship dispute, or research-integrity inquiry follows a documented escalation path through AEQUITA and TEMPORA.
Archive. Selected records are preserved in PLENA CONSERVA; public-safe PLENA VRX-1 verification receipts are exposed where appropriate, with the underlying file under publisher control.

Recommended PLENA route

ORIGINAPROVAPLENA CONSERVAVERITAAEQUITAPLENA SIGILLA

ORIGINA anchors authorship and origin. PROVA builds the editorial evidence packet. PLENA CONSERVA preserves research-of-record. VERITA carries author and institutional context. AEQUITA carries the fairness and appeal axis. PLENA SIGILLA seals sensitive integrity packets when needed.

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.

Front-end preview output

{ "sector": "Publisher, Journal & Research Integrity AI Trust Suite", "parent_suite": "Institutional Trust & Proof Suite", "buyer_ready_output": "Institutional PLENA Proof Packet", "route": [ "ORIGINA", "PROVA", "PLENA CONSERVA", "VERITA", "AEQUITA", "PLENA SIGILLA" ], "universal_flow": [ "Intake", "Review", "Receipt", "Escalation", "Archive" ], "receipt_logic": "Human Review Receipt + PLENA VRX-1 submission receipt; refusal receipt where the institution declines; sealing receipt where cross-border or formal handover applies", "export_note": "Editorial, integrity-review, or research-preservation packet; public-safe PLENA VRX-1 verification receipts.", "boundary": "Preview workflow only; not legal advice, not formal certification, not a backend institutional registry unless implemented." }

What PlenaProof is, and is not

The truth-boundary block carried across every institutional and sector surface. It is non-negotiable across the eight suites.

PlenaProof provides

  • Verification-readiness for credentials, claims, documents, and institutional records.
  • Proof organization, evidence packets, and reviewable receipts.
  • Human-review documentation with named reviewer, scope, date, decision, reason, and appeal path.
  • Diagnostic routing across the fourteen platforms and recommended modules.
  • Public-safe verification surfaces where institutions choose to expose them.
  • Durable record continuity across staff turnover, audit cycles, and institutional handover.

PlenaProof does not

  • Does not issue passports, national IDs, visas, official credentials, court records, or government documents.
  • Does not replace universities, registrars, legal offices, compliance teams, banks, courts, governments, or regulators.
  • Does not provide legal advice.
  • Does not guarantee regulatory compliance.
  • Does not certify AI systems unless a real certification program exists.
  • Does not claim formal partnerships or blockchain anchoring unless actually implemented.
  • Does not replace apostilles, notarization, embassies, government seals, official certification, or legal authentication.