The strongest market position is narrow: PlenaProof records accountable human trust events after identity, authorship, review, consent, refusal, or institutional action has occurred.
Positioning sentence: PlenaProof does not compete to identify everyone, notarize everything, sign every agreement, or become the universal media provenance layer. PlenaProof records accountable human trust events that other systems usually leave undocumented: refusal, human review, authorship declaration, consent, evidence handover, correction, revocation, and public verification.
These markets already have strong incumbents, regulatory privileges, network effects, or formal standards. PLENA interoperates with, cites, wraps, or complements them.
Government eID, passport, national wallet, and civil registry systems carry legal authority PlenaProof does not claim.
Identity verification, sanctions screening, biometric matching, and regulated onboarding belong to specialized providers.
Digital signature, agreement execution, notarization, and remote online notary workflows are separate legal-operational lanes.
Media provenance and content credentials should be treated as inputs or companion evidence, not as PLENA’s replacement target.
The wedge is not raw identity. The wedge is durable, public-readable human accountability.
A named reviewer can decline to certify a claim and preserve the reason without exposing private evidence.
Writers, researchers, students, publishers, and institutions can preserve draft history, AI-use disclosure, and human revision trails.
PlenaProof can record who reviewed, escalated, corrected, appealed, or declined a trust claim.
Families, counsel, clergy, caregivers, and institutions can receive organized proof archives without needing a full enterprise system.
PlenaProof turns scattered documents, messages, dates, and reviewer notes into a structured packet with scope limits.
A third party can check a receipt status in plain language without logging in or learning a new technical vocabulary.
PLENA appears beside established tools, not against them.
| Incumbent lane | What the incumbent proves well | What PlenaProof adds |
|---|---|---|
| Official ID / eID | Who a person or organization is under a recognized authority. | What an accountable human or institution did after identity was established. |
| KYC / AML / fraud screening | Identity risk, onboarding checks, sanctions exposure, document validity, or counterparty screening. | A receipt that a review occurred, was refused, was corrected, or was escalated with scope limits. |
| E-signature / online notary | Agreement execution, signature workflow, notarial act, or witness procedure. | Pre-signature evidence preparation and post-signature accountability, refusal, or preservation trail. |
| Content provenance / C2PA-style credentials | Media source, edit history, capture context, or content credentials where available. | Human authorship declaration, human review receipt, refusal receipt, and institutional handling record. |
| Digital credentials / badges | Achievement, course completion, credential metadata, or issuer-backed recognition. | Challenge, appeal, review, correction, preservation, and public verification around claims. |
| W3C Verifiable Credentials / Decentralized Identifiers (DIDs) | Portable, cryptographically signed credential schemas and decentralized identifier resolution under open W3C standards. | Refusal, human review, authorship, consent, correction, and accountability receipts that can reference VC/DID credentials where institutions use them. |
| Enterprise IAM / SSO | Login, access, authorization, workforce identity, and session control. | Portable trust-event receipts that survive beyond a login session or a single institution. |
Each row describes a real category of established tools by their public positioning. PLENA complements them — it does not replace them, and none of the companies named below partner with, endorse, or integrate with PLENA.
Microsoft Entra Verified ID, Dock / Truvera, Trinsic. These verify a person's or organization's attributes and issue reusable credentials. PlenaProof adds the event layer on top — the record that a review, refusal, consent, or service actually happened — and a PLENA wallet can hold credentials from these systems rather than replace them.
Credo AI, Holistic AI, IBM watsonx.governance. These serve the deployer's internal model governance, risk, and audit. PlenaProof produces the affected person's portable, externally-verifiable receipt that a human review occurred — the artifact the person keeps, not the deployer's internal log.
eyeWitness to Atrocities, ProofMode. These capture court-grade, tamper-evident atrocity and field evidence. PlenaProof does not compete on court-admissible capture. It provides a portable, person-held receipt and multi-forum handoff, and interoperates with such tools as inputs.
The records below are not produced by credential vendors, AI-governance platforms, or evidence apps. This is PLENA's uncontested ground.
A named reviewer can decline to certify a claim and preserve the reason, with scope limits and without exposing private evidence.
A specific, accountable human is recorded as the person who reviewed, escalated, corrected, or declined — not an anonymous system output.
Trust events between people and within communities are preserved as portable records, not locked inside one institution's account.
Work, service, and agreement records that the affected person holds and can present anywhere — for people the formal credential stack never reaches.
These rules keep PLENA credible while moving toward production.
PlenaProof can sit beside official ID, notary, e-signature, credentialing, KYC, and content provenance systems.
A receipt records a bounded action or review. It does not claim universal truth or automatic legal admissibility.
The verifier shows status, scope, date, issuer, redaction, and limits in language a stranger understands.