Artifact Inventory
Controlled listing of the files included in the project.
UCAC Proof
Record the version. Check whether its bytes changed.
Create a verifiable record of a digital file, its hash, metadata, manifest, registry entry, and verification state without pretending a local integrity record is blockchain notarization or a legal certification.
$195 Founding Proof Packet — up to 10 related artifacts
Purchases temporarily unavailable.
Online payment for this service is on hold during the local business-license review. The package description remains available for reference. Please do not send payment or sensitive files through an inquiry.
The question
Can you identify the version in your approval record?
Files get renamed, re-exported, emailed, copied, edited, and replaced. UCAC Proof creates a controlled integrity record so a later comparison has something concrete to verify against.
Core principle
UCAC does not trust claims. UCAC verifies artifacts.
The Proof Packet records what can actually be demonstrated from the supplied digital artifacts and processing record.
PROOF / BROWSER INTEGRITY DEMONSTRATION
A small change.
A different fingerprint.
Hash a short piece of text and optionally compare it with a recorded SHA-256 digest. Computation runs in this browser; the demonstration sends no text to UCS and saves no registry record.
The sample “abc” is ready. Compute its digest, then change one character and compare.
What does the comparison establish?
- A match means the computed digest matches the reference you supplied for this text.
- A mismatch means the digests differ. It does not identify who changed the text or why.
- The reference itself needs a trusted custody record; replacing both text and digest can defeat an uncontrolled comparison.
- No approval, author identity, rights, legal certification, signing, trusted timestamp, or external anchoring is established here.
How does this relate to a Proof Packet?
This demonstration performs one browser SHA-256 computation. A full packet also needs a controlled artifact inventory, provenance manifest, registry relationships, verification checks, and receipts. Those are separate from this page. No UCAC core execution or deterministic replay is claimed.
Proof Packet
What you receive.
SHA-256 Hashes
Cryptographic digests used to detect whether file bytes differ from the recorded version.
Provenance Manifest
Structured metadata tying files, identifiers, processing information, and verification records together.
Manifest Hash
A digest of the controlled manifest itself.
UCAC Registry Entry
A registry record that links the project and artifact identifiers to the verification package.
Verification Receipt
Human-readable status plus machine-readable evidence for future comparison.
Process
Original artifact → verifiable record.
Receive the artifact set
Up to 10 related digital artifacts in the founding package.
Canonical processing
Inventory, metadata and identifiers are structured consistently.
Hash + manifest
SHA-256 digests and the provenance manifest are generated.
Registry + verification
The packet records what was processed and whether verification gates pass.
Deliver Proof Packet
Human-readable receipt plus JSON/machine-readable evidence are packaged together.
Boundaries
Integrity evidence without inflated claims.
The founding Proof Packet uses local deterministic integrity and registry controls unless a separately approved real signing, storage, timestamping, or anchoring service is explicitly part of the engagement.
We do not automatically claim
- Legal notarization
- Blockchain anchoring
- Real IPFS publication
- Real GPG/PGP signing
- Government certification
- Proof of authorship beyond available evidence
Founding Proof Offer
Create the integrity record before the next version becomes a dispute.
$195 for up to 10 related digital artifacts in one project.