Lineage integrity
Reviewers can inspect whether a record still matches its original lineage.
Acceptable Use
Acceptable use keeps lineage verification useful and defensible.
Archive Origin should be used for authorized evidence capture, lineage verification, review, reporting, and support workflows.
What this page clarifies.
Archive Origin keeps the lineage boundary explicit so teams know what verification does — and what it does not do.
Human decision boundary
The platform does not decide truth, fairness, legality, mastery, or final interpretation.
Operational path
Each route points users toward the right workflow, support channel, or policy boundary.
Acceptable use examples.
These are the kinds of workflows Archive Origin is meant to support.
Education and CTE evidence
Capture and review student demonstrations, labs, projects, assessments, and competency attempts with institutional authorization.
Public and civic evidence
Preserve public-event documentation, inspection media, civic records, and contributor evidence paths for later review.
Commercial review
Support claims, compliance, legal, safety, and documentation review where evidence origin and integrity matter.
Prohibited or high-risk use.
Verification should not be used to intensify harm, bypass consent, or make unsupported records appear valid.
Harassment or surveillance
Do not use the platform to stalk, harass, intimidate, or covertly monitor people outside authorized workflows.
Misleading presentation
Do not strip context, hide edits, or present lineage verification as support for claims the record does not establish.
Restricted data
Do not submit sensitive, regulated, or protected records unless the workflow has the required permissions and safeguards.
Need Archive Origin for an institutional or public workflow?
Start with a pilot conversation so lineage requirements, policy boundaries, and review workflows are clear before launch.