01
Overview
Verifolio is a local-first evidence layer for academic and creative work. It checks whether the available source evidence supports what a user claims about their work.
A dossier can include a source record, claim review, contribution disclosure, optional process evidence, and an evidence score. The goal is a readable local record that helps reviewers see what is supported and what still needs human judgment.
Plain English summary
Verifolio records what evidence exists, compares that evidence to the claim, and shows the limits of the record.
02
Verification Method
Verifolio follows five steps to turn source material into a reviewable evidence dossier.
01
Capture
Upload a source file or paste source evidence text. This can be English or another language. The browser generates a SHA-256 hash locally. Nothing is sent to a server.
02
Preserve
The hash, file metadata, and timestamp are saved to browser localStorage. This creates a local record that the exact file version existed at capture time.
03
Verify
Verifolio compares the source evidence with the claim to review. Both can be in English, or the source can be in another language. It checks role level differences, unsupported scope, and missing nuance.
04
Score
The Evidence Strength Score measures how strongly available evidence supports the dossier claims. It measures evidence support, not quality or truth.
05
Present
A reviewable dossier is generated with source records, finding summaries, safer claim wording, and optional modules when added.
03
SHA-256 Source Record
A SHA-256 hash is a fingerprint of a file. If the file changes, the hash changes. Verifolio uses this to create a local browser record that a specific file version existed when it was captured.
The record can include the file hash, timestamp, file name, file size, and browser capture time. It is metadata-only proof. The source file is not uploaded in this MVP. The source file can be in English or any other language.
File hash
SHA-256 fingerprint of the exact file bytes.
Timestamp
When the browser generated the source record.
Local browser record
Stored in your browser localStorage in this MVP.
If the file changes
The SHA-256 hash changes and no longer matches the saved record.
What it does not prove
It does not prove who created the file or when the first draft began.
04
Claim Review
Claim review compares source evidence against the claim to review. It checks whether the claim says more than the source supports. The source evidence and the claim can both be in English, or the source can be in another language.
Verifolio can flag role inflation, unsupported scope, and missing nuance. It can also generate safer wording that stays closer to the source evidence.
Role inflation example
Source says the student assisted with data collection under faculty supervision. The claim says the student independently led the experimental analysis. Verifolio flags the role gap and suggests wording that matches the source.
Role inflation
The claimed role is higher than the role supported by the source.
Unsupported scope
The claim includes work, results, or ownership not found in the source.
Safer wording
A revised claim that keeps the meaning closer to the evidence.
Human review
Low confidence or unclear evidence should be reviewed by a person.
05
Role Level Taxonomy
Verifolio uses role levels to compare what the source says with what the English claim implies.
| Level | Role | Meaning |
|---|---|---|
| L1 | Observer | Watched, attended, or learned about the work. |
| L2 | Assistant | Helped or supported under supervision. |
| L3 | Contributor | Created documented portions, collected data, or analyzed materials. |
| L4 | Collaborator | Worked jointly on decisions or implementation. |
| L5 | Lead | Led design, research, or analysis independently. |
| L6 | Sole Creator | Built or invented the work entirely alone. |
06
Evidence Score
The Evidence Strength Score measures evidence support. It is not a quality score. It is not a truth score.
What the score means
A higher score means more available process evidence supports the dossier. It does not mean the work is better or factually correct.
| Category | Weight | What it measures |
|---|---|---|
| Revision Depth | 25% | Revisions, drafts, rewrites, design iterations, research analysis, and structural changes. |
| Iteration Consistency | 20% | Active days, revision days, log days, service dates, and preparation spread. One-day dumps are penalized. |
| Human Process Density | 20% | Bug fixes, feedback rounds, data sessions, assets, materials, hours, and practice sessions. |
| AI Transparency | 15% | Disclosure categories and explanation of AI use. |
| Source Integrity | 10% | File hash when present, source text, reference details, and warning severity. |
| Contribution Clarity | 10% | Direct role, mentor role, verifier details, and AI categories where provided. |
07
Optional Modules
Process Evidence is optional. A dossier can include one or many process evidence modules. Process Evidence is separate from Original Source Evidence. Original Source Evidence is the source material compared against the claim. Process Evidence records how the work developed over time.
Manual entry in this MVP
Manual entry is supported now. Automatic imports are planned later. GitHub and Google Docs imports are not connected in this MVP.
08
Common App Draft
The Common App draft is optional. It formats evidence into activity-style wording that can be reviewed and edited.
This does not imply Common App partnership. It is a formatting helper inside the local dossier flow.
| Field | Limit |
|---|---|
| Position or leadership description | 50 characters |
| Organization name | 100 characters |
| Activity details | 150 characters |
09
Login Roadmap
Login and Register are planned for later. They are visible in the navigation so the product direction is clear, but they are not active in this MVP.
This MVP stores records in your browser. Future accounts may support account vaults, cross-device access, and cloud sync.
Now
Local records are stored in your browser.
Coming later
Account vaults, cross-device access, and cloud sync may be added.
Not active now
Login, Register, GitHub import, and Google Docs import.
10
Limitations
Limitations are part of the dossier. Reviewers should read them before treating any evidence record as complete.
What Verifolio does not prove
Verifolio does not prove human authorship, legal status, factual accuracy, or active third-party imports.
Not an AI detector
Verifolio does not detect whether AI wrote any content. It checks whether the process claim is supported by source evidence.
Not legal proof
A local dossier is not legal proof, institutional endorsement, or active account verification.
Not a guarantee of authorship
Verifolio does not prove 100 percent human authorship. It shows what the available evidence supports.
Not proof of factual accuracy
A supported claim can still contain factual errors. Reviewers still need judgment and context.
Manual evidence can be incomplete
Manually entered records depend on what the user provides. Missing or weak entries should be reviewed.
Browser records can be lost
Records are stored in your browser. Clearing local data can remove saved dossiers.
Imports are not connected
GitHub and Google Docs imports are not connected in this MVP. Process evidence uses manual entry.