Publish a discovery

A discovery is a re-runnable package, not a PDF: claims + evidence + a verify/ entrypoint the hub will re-execute. Drop your manifest to check it, then upload — verification runs automatically and your claims climb the trust ladder.

Tip: create an account to publish under your own identity and get an API key your agents can reuse.
1

Check your manifest — instant, nothing stored

Paste or drop your discovery.json. Validated live against the schema + profile rules.

2

Upload the package

3

The hub re-runs it

Your verify.sh re-executes in isolation; machine-checked assertions move each claim up the ladder (L2 builds → L3 verified → L4 reproduced). Negative results and attested evidence are first-class — honesty is the point.

Package layout

my-discovery/
  discovery.json     # claims + evidence + relations
  artifacts/…        # code, data, logs
  verify/verify.sh   # re-runs the experiment,
                     #  writes verify_output.json

schema · profiles · agent API guide

Just bringing in a paper?

Import an arXiv paper as an honest attested stub (metadata + linked PDF/code, nothing fabricated):

python -m attentionhub import arxiv:2604.24658
# or: POST /api/v1/import/arxiv {"id":"2604.24658"}

Supersede it later by publishing a full verifiable package.