Evidence Console preview: this environment is under active development. Content and workflows may change while we iterate.

Evidence Launchpad

Start from one place after registration: run your first submission, confirm billing posture, and wire verification delivery paths.

First Evidence Run

Run upload, integrity hash, and attestation, then load your latest evidence bundle for reviewer handoff.

Workspace Progress

Onboarding status will appear after account telemetry sync.
Completed steps0 / 0
Next stepn/a

Stripe Billing

Launch secure checkout for paid plans and open the Stripe portal for payment updates.

Choose a paid plan, then click Start secure checkout.

Plan + Usage Meter

Usage metrics will appear after billing reads succeed.
Plan tiern/a
Successful jobs0
Included jobsn/a
Projected overage0
Billing staten/a
Next paymentn/a
Attentionnone
Billing health will appear after status sync.

Activity Snapshot

Live status of jobs currently loaded in this Evidence Console session.

Jobs loaded0
Success0
Pending0
Failed0
Launchpad ready. Connect your API key and refresh jobs to populate usage telemetry.

Workspace Connection

Connect your API base URL and scoped key. Values are stored only in this browser profile.

Not connected yet.

Submit New File

Upload a file and submit a verification job. Registration metadata helps enrich the OCI evidence card attached to this run.

Select a file to start.

Evidence Activity

Search by job ID, hash, contract, or status, then open detailed evidence cards for validation and handoff.

Job Status Level Contract Job Hash Input Hash Created Completed Evidence Cards

Selected Job Snapshot

Core lifecycle, integrity, and anchoring fields for the active job.

No job selected.

Evidence Artifacts

Load attestation, journal, and bundle outputs for external verification, customer delivery, and audit trails.

No artifact loaded.

Operations Rhythm

Suggested weekly cadence for teams running high-assurance integrity workflows.

  1. Run submissions using signed_manifest by default, with hash_only for integrity-only lanes.
  2. Review failed jobs daily and export evidence for unresolved exceptions.
  3. Capture compliance evidence bundles weekly using documented runbooks.
  4. Re-run verification checks before customer or auditor handoff.
  5. Track queue and retry metrics for operational reliability drift.
  6. Maintain least-privilege key scopes and rotate credentials on schedule.