TabTwinProofTwin← Back to home
Subsystems/ProofTwin

Capture

ProofTwin

Turn browser work into verifiable evidence.

ProofTwin creates an evidence package for important browser activity. It combines timestamps, identity, action history, relevant page state, visual proof, and integrity metadata so an auditor can understand what happened and when.

01
Why this capability exists

From friction to a clear outcome

The user problem

Important submissions, approvals, and outsourced browser tasks often leave weak evidence. A screenshot can be incomplete or altered, while a long video makes it difficult to verify the exact action, time, page state, and outcome.

The TabTwin answer

ProofTwin creates a sealed activity package with timestamps, relevant URLs, action history, state snapshots, visual evidence, and integrity metadata. A reviewer can understand what happened without receiving unrelated browsing data.

02
Real-world scenario

Prove that a regulatory filing was submitted correctly

  1. 1

    Start a proof session for the filing workflow

  2. 2

    Complete the required review and submission steps

  3. 3

    Capture the confirmation state and reference number

  4. 4

    Redact information outside the evidence scope

  5. 5

    Seal and export the timestamped proof package

03
End-to-end workflow

How ProofTwin works

  1. 01

    Start a proof session before the regulated or high-value action.

  2. 02

    Capture relevant steps while masking unrelated or sensitive information.

  3. 03

    Seal and export the evidence package with integrity and session metadata.

04
What is included

Core capabilities

01

Trusted timeline

Orders relevant page actions and confirmation states with timestamps.

02

Scoped URLs & state

Includes the routes and page evidence needed to understand the activity.

03

Visual confirmation

Captures useful screenshots around approvals, submissions, and final outcomes.

04

Integrity metadata

Adds hashes and session metadata that reveal later changes to the evidence.

05

Identity context

Associates the proof with the approved actor or operating process where configured.

06

Audit export

Packages the evidence in a format suitable for review and retention.

05
Where it wins

Best use cases

  • ✓Tax or regulatory submissions
  • ✓Financial operations and approvals
  • ✓Outsourced process verification
06
What the user gets

Expected outputs

  • →Timestamped evidence package
  • →Action history and state snapshot
  • →Integrity hash and audit metadata
Business value

What changes for the team

  • ↗Create clearer evidence for audits and operational review
  • ↗Verify outsourced or high-value browser tasks
  • ↗Reduce the effort required to reconstruct what happened later
Built for control

Safe by design

  • ✓Evidence scope is defined before or reviewed after capture
  • ✓Unrelated and sensitive data can be redacted before sealing
  • ✓Sealed packages expose integrity changes and retain access controls
Why ProofTwin is different

ProofTwin creates structured, scoped, integrity-aware evidence rather than treating a screenshot as proof of an entire workflow.

One shared technical foundation

Powered by the Browser Session Engine.

ProofTwin consumes the same structured DOM events, timeline, context, snapshots, and safe execution primitives as the rest of TabTwin—without requiring another extension.