GTIXT // proof workflow

Integrity Beacon

A verification workflow for confirming that the published GTIXT state remains traceable, replayable, and institutionally defensible.

Executive VerificationLoading publication pointer

Continuity VerifiedLoading publication pointer

Replay Integrity StableAwaiting pointer

Compression Governance ActiveRepresentation policy enforced

Observed Layer PresentRecord count loading

No Future LeakageSnapshot time remains bounded

Download Snapshot Artifact

Run verification when the latest pointer has loaded.

Layer 2Structural TraceabilityOpen layer

This layer explains why the current public state is defensible before exposing raw hashes. It keeps lineage, artifact access, certification, and provenance grouped as a trust workflow.

LineagePublication object loading

CertificationSHA-256 pending

ArtifactSnapshot artifact pending

ProvenancePointer source loading

Pointer Published

The public pointer declares the latest artifact, expected hash, publication time, and record count.

Artifact Downloaded

The snapshot is downloaded as a governed artifact, not treated as an anonymous file.

Hash Computed

The browser computes SHA-256 locally and compares it to the published pointer.

Verification Complete

A match means the public artifact is unchanged from the declared publication state.

Publication Integrity

GTIXT treats integrity as proof of publication continuity, not as a decorative technical badge.

Replay Traceability

Pointer, snapshot, timestamp, and hash form the minimal public replay path for the current state.

Defensible Absence

If proof is unavailable, the workflow shows that state instead of filling the gap with confidence language.

Layer 3Forensic Verification LayerOpen layer

Raw pointer data, manual commands, API examples, and cryptographic endpoints stay available here for audit and reproduction.

Snapshot object

Loading pointer

SHA-256

Loading hash

Published proof

Timestamp

Records

Download pointer

curl /snapshots/universe_v0.1_public/_public/latest.json -o latest.json

Extract artifact path

cat latest.json | jq -r '.object'

Download snapshot

curl /snapshots/$(cat latest.json | jq -r '.object') -o snapshot.json

Compute hash

sha256sum snapshot.json

Compare pointer hash

cat latest.json | jq -r '.sha256'

The computed hash must equal the pointer hash for the artifact to remain publication-identical.

Latest pointer endpoint

GET

/snapshots/universe_v0.1_public/_public/latest.json

Browser verification example

async function verify() {
  const pointer = await fetch("/snapshots/universe_v0.1_public/_public/latest.json").then((res) => res.json());
  const snapshot = await fetch("/snapshots/" + pointer.object);
  const digest = await crypto.subtle.digest("SHA-256", await snapshot.arrayBuffer());
  const computed = Array.from(new Uint8Array(digest)).map((b) => b.toString(16).padStart(2, "0")).join("");
  return computed === pointer.sha256;
}

Provenance verification

POST

curl -X POST https://gtixt.com/api/provenance/verify   -H "Content-Type: application/json"   -d '{"type":"dataset","snapshot_uuid":"<snapshot_uuid>"}'

ReferenceCryptographic Features and Evidence ModelOpen layer

Multi-Level Hashing

Evidence snapshots, firm aggregates, pillar rollups, and dataset artifacts retain hashable proof boundaries for audit trails.

ECDSA Verification

Signature verification is available for institutional reproduction without turning the first screen into a cryptographic console.

Provenance Endpoints

Trace, graph, evidence, and verify endpoints keep raw proof accessible when an operator needs deeper inspection.