Fictional project
Demo project: Luma
This fictional project shows how a documentary history can be built in Provenia. The example follows Luma from an initial idea to a consolidated product concept using different file types across four successive records.
No real person, company, or product is represented in this project.
How Luma evolved
- 1Milestone 1
Initial concept — TXT
The first record captures the idea in its simplest form: the problem, initial proposal, features under consideration, and the principles that could guide the product.
- 2Milestone 2
Requirements and decisions — XLSX
The idea becomes a structured requirements set. Features are prioritized and product decisions are explicitly kept, postponed, or discarded.
- 3Milestone 3
Main interface wireframe — PNG
The earlier decisions become a first visual representation showing how note capture, search, organization, and related information could work in the interface.
- 4Milestone 4
Consolidated product concept — PDF
The final milestone brings together the proposal, selected requirements, product decisions, and first wireframe in a consolidated product concept.
See the complete history in the Dossier
After the records are created, Provenia brings the documentary history together in a chronological Dossier. The PDF makes it easy to review the records, their relationships, and the evidence associated with each milestone.
Verify the Dossier yourself
For technical verification, use the complete ZIP package exported by Provenia. The PDF above is provided for convenient reading; by itself, it does not contain everything used by the public verifier.
Verifying the package lets you check the Dossier and inspect the records it contains.
The four Luma Records form a documented sequence from the initial concept through requirements, a wireframe, and the consolidated product concept. When the package verifies and retained files match their registered hashes, a reviewer can check those artifacts' correspondence, their relationship to the Records, and the available time evidence. If a retained artifact's bytes change, its recalculated SHA-256 will no longer match the registered hash. See how hash, timestamp, and signature answer different questions and the evidentiary limits. These checks do not by themselves establish authorship, ownership, originality, or legal priority over third-party evidence.
Verification instructions
- 1.Download the complete ZIP package.
- 2.Open Provenia’s public verifier.
- 3.Upload the ZIP without extracting or modifying its contents.
- 4.Review the verification result.