Declarations
Statements supplied by a participant about an action, tool, source or handoff. They remain attributed statements rather than independently established facts.
Public research / proof of concept
HumanVerified Chain of Custody
A clearer record of how work moved from source to outcome
Research proposal and proof of concept. No live records are issued, and this page does not offer a verification or certification service.
Claim discipline
Keep statements, support and gaps separate.
The proposal makes the status of each entry visible instead of compressing unlike kinds of information into one badge.
Evidence and checks
Files, signatures, review notes or inspections actually received or performed, recorded with their method, scope, date and limitations.
Unknown or out of scope
Gaps, unobserved activity, unresolved questions and facts the proposed process was not designed or authorised to examine.
Three research tracks
One evidence model, tested against different kinds of work.
Research, documentation and code
Explore source references, artifact versions, declared tools, review checkpoints and build outputs without treating a repository history as complete authorship evidence.
Moving image and editorial production
Explore ingredients, edit decisions, declared automated contributions, approvals and exports while recognising that unrecorded actions may still exist.
Manual craft and physical custody
Explore material references, maker and reviewer checkpoints, object identifiers and handovers while keeping substitution and unobserved work visible as residual risks.
Interpretation boundary
A record is not a verdict.
A record may show that named evidence was supplied or that a stated check was performed. It does not turn a declaration into a fact or make missing activity knowable.
It does not establish the truth, quality or ownership of an outcome, complete authorship, the absence of a tool category, or what happened outside recorded checkpoints.
Publication set
Read the proposal and inspect the release.
Use the manifest and checksum file to identify the exact publication files and release version.
In this release, “sealed” means AES-256 permission-restricted and externally hash-verifiable.
The permissions are advisory rather than a guarantee against alteration. The checksum manifest is unsigned and should be obtained through a trusted publication channel before its hashes are relied upon.
The Markdown files are the primary accessible versions of this release candidate. The PDFs provide selectable text and accessibility extraction, but are not fully tagged or claimed as PDF/UA conformant. Tagged-PDF remediation and independent accessibility review remain required before public distribution.
- Concept paper — Markdownhumanverified-coc-whitepaper-v0.1.md
- Concept paper — sealed PDFhumanverified-coc-whitepaper-v0.1.sealed.pdf
- Technical guide — Markdownhumanverified-coc-poc-technical-guide-v0.1.md
- Technical guide — sealed PDFhumanverified-coc-poc-technical-guide-v0.1.sealed.pdf
- Release manifestrelease-manifest.json
- SHA-256 checksumsSHA256SUMS.txt
Pilot discussion
Test the boundaries before testing the badge.
A useful pilot would compare what participants declared, what evidence a reviewer could actually check, and which uncertainties remained.