Process Walkthrough

From original capture to later review.

Follow the operating sequence from capture through preservation, connection, verification, and later review.

Archive Origin preserves the artifact, its provenance, its context, and the relationship between source records and later outputs so a reviewer can inspect whether the record still holds up when it matters.

Review a sample verification Talk to the team
Five-Step Flow Review Oriented
1. Capture

Create the source artifact that later claims, outputs, and review depend on.

2. Preserve

Seal provenance, timestamps, contributors, and artifact relationships into the record.

3. Connect

Let credentials, reports, clips, and packets point back to the preserved artifact and context.

4. Verify

Check whether the reviewed record still matches the preserved history.

5. Review

People decide meaning, sufficiency, fairness, legality, and next action after integrity is known.

Concrete Example

One evidence path from demonstration to decision.

The example below applies across education, public documentation, and technical workflows because the operating sequence stays the same.

Source artifact

A video, image set, lab demonstration, inspection file, or field record is captured at the time of the event.

Preserved record

Archive Origin stores provenance, timestamps, source linkage, and any supporting contributor or review context.

Derived output

A portfolio artifact, credential packet, public clip, or review summary points back to the preserved record.

Later review

A reviewer checks whether the derived output and the reviewed artifact still map back to the original evidence trail.

What Gets Preserved

The process is useful because it keeps the evidence chain intact.

Archive Origin is not preserving a file in isolation. It is preserving the relationships around that file so later review is possible.

Preserved by the system

  • Artifact identity and integrity checks
  • C2PA provenance and source linkage
  • Timestamps and chronology
  • Contributors, issuers, and related reviewers
  • Relationships between source artifacts and derived outputs
  • Verification state and revocation-aware review paths

Still decided by people

  • Whether the artifact is complete enough for the decision at hand
  • Whether the artifact proves legal compliance, mastery, fairness, or truth
  • Whether privacy, consent, or access boundaries allow sharing
  • Whether the record is sufficient for a grade, credential, investigation, or report
Verification

PASS and FAIL are built to be easy to understand.

Verification is useful when the result is legible and the next step is obvious.

PASS

The reviewed artifact still matches its preserved history. That confirms integrity, not meaning.

FAIL

The reviewed artifact does not match its preserved history. Ask for the source artifact, inspect the derivation path, or pause the decision.

Next Step

Use the shared process, then choose the right branch.

Once the operating flow is clear, move into Public, Education, or Developers for the domain-specific logic that belongs there.

Go to Public Go to Education Go to Developers