Hand a signed package to an AI that reads local files

What this is for

Download the signed package for a World and give it to a tool that reads local files, verifying the signature and the file digests before anything reads it.

Before you start

Sources: PDF, DOCX, XLSX, PPTX, ODT, ODS, ODP, JPG, PNG, TIF or GIF. Every one of them is sanitized to PDF and read by OCR before anything else happens.

Tables and formulas are not extracted as tables: a figure arrives as the paragraph it was printed in, with the page and the box it sat in, so a number is readable and the grid that arranged it is not. Heading levels, sections and columns are not recovered as typed structure; what the compiler receives is a paragraph and where it sat. TAVONEL processes sources up to 5 MB and 80 pages.

A compile produces a candidate, and a candidate becomes an active World only when a person activates it in the workspace. That step needs a paid plan: the Developer plan, if you are the workspace owner, or the Team plan, which is sold through a conversation today rather than self-serve checkout. A free evaluation can upload, compile, review and export; its activation request is refused, so decide the plan before you plan the run.

Verification is a separate trust path: the key fingerprint comes from the published verifiers, not from the archive you just downloaded. Receiving a download descriptor is not the same act as downloading the archive, and the README and AGENTS files in a package are instructions rather than evidence.

What a free evaluation includes, and what a page costs, are on the pricing page. This page does not restate either, so it cannot disagree with them.

Running it in code

The exports section publishes the package layout, the digest manifest and the offline verification steps.

The exact contract: Exports in the documentation.

Where this stops

A downloaded package is a snapshot of one revision and never updates itself: a World that changes afterwards leaves the copy on disk exactly as it was. A package carrying ontology files does not make a reader capable of reasoning over them.

The reading limits under "Before you start" apply to this recipe too.

Next action

Read the exports section for the layout and the verification steps. If you need a package for a corpus of your own, the activation step above is the one to plan first.

Run and revision information

Every section above describes what the product does today, and the revision of this guide is printed at the foot of the page. A verified run date appears there only once a person has recorded a run, never on an edit to this page.

What a recorded run will add

The actual input — The document set the run used, published from a corpus cleared for redistribution.

Following it on screen — A capture of the workspace screens as the run passed through them, recorded rather than staged.

What the run produced — The files, tables and drafts the run produced, as it produced them.

Checking it against the source — The source location behind each value, opened at the page and the region it came from.

Using the result outside TAVONEL — The result an external consumer read back from the same World, verified on its own run.

Measured effect — Quality, time, cost and human effort, from a same-condition measurement of that run.