Ev

MRGI EVIDENCE / PDF EDITING & REVIEW

COMING SOON

Edit PDFs.
Review every page.

Read, annotate, organize, and redact PDFs. Assemble reviewed documents and their sources into a verifiable evidence packet.

For research teams, reviewers, and anyone who needs to show how a conclusion was reached.

Try the interactive demo Browse all 15 apps

MEET THE WORKSPACE

A closer look at Evidence.

Enlarge preview
Concept image of MRGI Evidence with a PDF page, page thumbnails, annotation tools, and a review sidebar.
AI-generated interface concept

PDF pages in the center, page organization on the left, and annotations, redaction decisions, and verification context on the right.

Proposed design with synthetic content. This is not a released application; features and appearance may change.

MRGI Evidence · Concept preview

Concept image of MRGI Evidence with a PDF page, page thumbnails, annotation tools, and a review sidebar.

AI-generated proposed interface. Not a released application.

Interactive demoFeature breakdownThe MRGI directionFull workflow guide ↗

EXPLORE THE IDEA / HANDS ON

Verify a packet. Then change it.

Generate a SHA-256 fingerprint of a synthetic document, alter its text, and check the mismatch against the original fingerprint.

INTERACTIVE BROWSER LAB

A small example.
A closer look.

Generate a SHA-256 fingerprint of a synthetic document, alter its text, and check the mismatch against the original fingerprint.

Synthetic inputs. Local computation. No uploads.

This browser hashes sample text only. It does not parse PDFs, perform redaction, authenticate reviewers, or sign a manifest.

Read the full Evidence workflow guide
Explore the future interface design

Inside MRGI Evidence

INTERFACE CONCEPT
EvMRGI Evidence
Field study / evidence packetSYNTHETIC PROJECT
FIELD STUDY / 2026

What supports
the conclusion?

Selected observations from the synthetic field study.

[01] Observations.csv · Q2 snapshot
SOURCE DOCUMENT / 01
PACKET CONTENTS
PDFStudy brief.pdfSource ID / 001
CSVObservations.csvSource ID / 002
DOCReview report.docxSource ID / 003

Manifest preview · SHA-256

3 source recordsConcept UI · No files processed

Original interface mockup with synthetic content. This is a design concept, not a screenshot of a released application. Switch views to explore the proposed workflow.

01 / THE WORK BEHIND THE WORK

A reviewable packet that connects source files, decisions, and the final report.

A final PDF rarely tells the whole story. Which spreadsheet supplied the figures? Who reviewed the redaction? Evidence is being designed to carry that context alongside the documents, from first import to the distribution packet.

Where it stands

A shared evidence library and CLI have an internal prototype. The redesigned application, approval UI, and full cross-app experience shown here are planned.

02 / THE PLANNED TOOLKIT

Built around
your real work.

The intended Evidence experience.
Feature availability will be confirmed before release.

  1. 01

    Import and identify source documents

  2. 02

    Review PDF content and redaction decisions

  3. 03

    Link selected evidence to a report

  4. 04

    Assemble versioned distribution packets

  5. 05

    Record approval checkpoints

  6. 06

    Verify packet contents against a manifest

A CLOSER LOOK / FEATURE DESIGN

How Evidence
is intended to work.

Explore the behavior behind the feature names: what the product would do, and what the reviewer would still need to decide.

01Source registration

Intended behavior

An imported file would receive an identifier and a hash of its original bytes. The source register would distinguish the original from derived copies and record which report references use it.

What to inspect

Review the file identity and provenance. Matching bytes do not establish that the source is truthful.

02Decision-aware redaction

Intended behavior

A proposed redaction would capture the selected content, reason, intended audience, and review state. Applying the decision would create a separate distribution copy.

What to inspect

Inspect the output for residual text, imagery, metadata, and attachments. A visual black box alone is not sufficient.

03Packet release and verification

Intended behavior

A release would bind the report, selected sources, and review record to a manifest. Independent verification would report missing or changed contents.

What to inspect

Retain a trusted copy or signature for the manifest. A replaced manifest can describe replaced files without revealing the substitution.

03 / THE MRGI DIRECTION

Where we’re taking Evidence.

Three product-specific priorities shaping the proposed MRGI experience.

01

A packet with a paper trail

Keep source identifiers, hashes, report references, and review decisions together. Give the recipient a way to check the packet, not just read it.

02

Redaction with a review step

Separate a proposed redaction from an approved distribution copy. Capture the reason and reviewer so the decision remains understandable later.

03

Verification outside the workspace

Plan for independent verification of packaged file hashes. A hash can reveal a mismatch; it cannot prove a claim is true or prevent someone replacing an untrusted manifest.

These are development goals, not claims of shipped features or market exclusivity. AI, local operation, and automation are shared foundations—not the entire product distinction.

04 / BETTER CONNECTED

A next step
for every good idea.

Receive an approved Grid snapshot and an Author report, then package their supporting sources.

  1. 01

    Collect

    Identify the selected PDFs and data files.

  2. 02

    Connect

    Link reviewed facts to an Author report.

  3. 03

    Release

    Review the packet and export a verification manifest.

Assistance with a defined role.

Proposed AI assistance can suggest evidence references or flag missing context. The reviewer chooses what to cite and approve.

Cross-app access is planned around selected resources and explicit consent. Ordinary local editing should not require uploading your files.

BUILT ON OPEN-SOURCE FOUNDATIONS

PDF parsing, editing, redaction, signature, and automation code exists in the PdfCraft foundation. Those capabilities are the starting point, not an MRGI exclusivity claim. Read the source credits ↗

MRGI EVIDENCE / COMING SOON

A new way forward.
Taking shape.

Explore the suite today. Availability and pricing will follow.

Visit your Cyberplexs account ↗Existing identity portal · No app access yetExplore planned memberships ↗