AN EVIDENCE RECORD FOR AI WORK

Built something with AI? Capture what you actually know.

Describe one AI task, its limits, rationale, and falsifier. Your browser builds a local evidence pack with SHA-256, no account required.

A first-record example

Self-authored / not verified by EOL
Statement
A weekly AI competitor digest helps the team make decisions.
Scope
Public sources only, with no external distribution.
Falsifier
No decision references the digest for one month.

ResultAn evidence pack and real SHA-256 address are created after assembly.

One record. Three steps.

Move from a real piece of work to a file you can verify.

  1. Describe one AI task

    Name the statement, scope, rationale, and falsifier.

  2. Download the evidence pack

    Your browser creates the JSON and a real SHA-256 address locally.

  3. Check the pack in Demo

    Demo checks structure and digest, not whether your statement is true.

Try the path with one repeatable piece of your own AI work.

Create a recordOpen Demo

See what happens to the record

This example is assembled and checked by the same logic used in Build and Demo.

Prepared record

Weekly AI competitor digest

Statement
Bound a weekly AI competitor digest for the team.
Scope
Public sources only; no external distribution; no more than 30 minutes per week.
Why
The digest already shapes decisions, but nobody can see its sources and boundaries.
Falsifier
Withdraw the record if no decision references the digest for one month.

Evidence pack

Portable JSON

Schema
eol.demo-evidence-pack/1
Records
1
SHA-256 record address
sha256:e4265948fc4de0e9a181826c7b7829d1f5908212c31bd8e7b92573a4e561391e

Demo result

Technical verification

The structure, links, and SHA-256 digest match.

This does not establish that the statement is true.

Open Demo

What you get

An addressed record

Statement, scope, rationale, and falsifier stay together under one SHA-256 address.

A portable evidence pack

Plain JSON that you can download and verify again.

An honest boundary

It shows what was checked technically and what remains self-authored or unknown.

What is established, and what is not

Build creates the file. Demo checks its technical integrity. Everything else is stated plainly.

Facts

  • No account is required.
  • Your answers stay in the browser.
  • An unfinished draft stays in this browser and disappears after the record is assembled.
  • The file is not sent to a server.
  • A real SHA-256 digest is created.
  • Demo checks structure, links, and digest.

Boundaries

  • This is a self-authored record.
  • It is not verified by EOL.
  • It is not an audit.
  • It is not legal advice.
  • It is not an automatic check of your entire application.

Ready to create your first evidence record?