Skip to content
Proof artifact index

Governed handoff

Evidence bundles

A packet of generated files, findings, screenshots, route history, and linked source documents for audits or handoffs.

Why this proof matters

Teams can move a PDF from review to release with the context needed to defend what changed and why.

3

Workflows

3

Toolbox links

3

API routes

Product story

Where the artifact appears in the product

Open screenshot story
app.docuzeus.local/provenance-ledger

Active tool

Provenance Ledger

Events
27
Actors
4
Ready
Yes

NIST Cybersecurity Framework 2.0

National Institute of Standards and Technology

Ready
Uploaded
Approved
Exported

Version context

Every report references the source document, selected revision, and generated artifact.

Decision trail

Approvals, comments, compare decisions, and redaction verification remain visible.

Export packet

Ledger output is designed for release records, audit packages, and incident notes.

Document set

NIST Cybersecurity Framework 2.0

32 pages

Adobe FY2025 Form 10-K

134 pages

Recent events

10:42Preflight report
10:38Access changed
10:31Upload created
Mock DocuZeus screenshot showing Provenance Ledger with public-document examples including NIST Cybersecurity Framework 2.0, Adobe FY2025 Form 10-K.

Generated outputs

  • Evidence export
  • Artifact manifest
  • Workspace activity trail

Verification signals

  • Source document lineage
  • Generated artifact list
  • Reviewer and job timestamps

Workflow coverage

How teams produce this artifact

Browse workflows

Next steps

Turn the proof type into a repeatable path

Start with a public PDF, inspect the screenshot story, then copy the route pattern into an API recipe or run the interactive builder with a matching workflow.