What changed, without the noise.

Added

• Release candidate, pending merge. Everything in this entry is reviewed and not yet merged, so it is not live on tavonel.com today. It is recorded before it lands for the reason the entry below gives.
• The entry pages at / and /ko are rebuilt as nine scenes, each one a keyboard-reachable landmark that answers a single question and offers a single next action: what TAVONEL is, whether it works, what happens to your files, whether the result can be trusted, what happens when a source changes, why a compiler rather than a parser, how work comes in and goes out, what is safe to assume, and what to do next.
• The first screen is the product rather than a picture of it: a real page of a real SEC filing, the region the compiler read on it, a line from that region to the passage compiled out of it, and the objects bound to that passage — every one of them read out of the public Compiled World when the page is built. It plays no video.
• An evidence inspector on the entry page prints the five things a citation needs — the object's state, the file, the page, the region as coordinates on that page, and the source version's digest — with Copy citation and a link that opens the original document at the right page.
• A design record for the entry pages at docs/LANDING_V2_2026-09-19.md: the rules every figure on them obeys, the component and data-module inventory, the semantic colour table, the navigation model, and the two commands that regenerate the committed page images.

Improved

• One header and one footer across every public page: five sections, Request access as the single filled control, and a phone sheet whose rows meet the 44px touch floor and close on Escape.
• The six questions that sat at the foot of the old entry page are on /contact, above the form they are usually asked before answering.
• A colour means one thing everywhere it is used, on the site and in the workspace alike: blue is where something came from, mint is verified, violet is a relation, amber is a changed source, coral is held for review.
• Reduced motion gets the whole story at once as a static composition with the play control still present, rather than a hidden animation.

Fixed

• What TAVONEL does and does not yet do was spread across the header, the first screen and a note about how the film was made. It is stated once, in the deployment's own words, at the two points where a reader is deciding what to do about it.
• Numbers on the entry pages could be typed into the copy. Every figure the pages print is read out of the compiled public World and marked as measured, and a browser check walks both rendered pages for a digit that carries no such mark.

Added

• Release candidate, pending merge. Everything in this entry is reviewed and not yet merged, so it is not live on tavonel.com today. It is recorded here before it lands rather than after, because a changelog that only appears after the fact is the one nobody can plan against — and dating it as shipped would be the same defect in the other direction.
• An API reference at /api: every operation in the contract with its parameters, request and response schemas, a worked example, and the error codes it can return. It is generated from the OpenAPI document rather than written beside it.
• A try-it on that page for the three reads that need no key — the capability manifest, the deployment status, and the public sample World.
• The full error catalogue on /docs/errors: every code the API can return, what it means and what to do about it, including AUTH_REQUIRED, which is what a missing or wrong key gets.
• A version lifecycle and deprecation policy on /docs/changelog: what can change without notice, what counts as breaking, and the 180-day support window a deprecated version keeps.
• The two integration-recipe scripts are published under /developer/ and pinned by sha256 in the distribution channel, so the recipes on /docs/integration-recipes can be run rather than read.
• Endpoint documentation for the thirteen operations that had none: the World lenses' companions, run events, reviews, manifest status, connections, OAuth connectors, key rotation and the audit trail.
• The research receipts behind the published figures are downloadable, each with its full sha256, so a number on this site can be checked against the artifact it came from rather than taken on trust.

Improved

• The two per-source ceilings TAVONEL enforces — 5 MB and 80 pages — are published on the pages that promise the ceilings, with the code a refusal carries.
• API rate limits are published per scope on /docs/billing-and-limits, taken from the values the authorizer enforces.
• Documentation search is on every page rather than only the index, and a result shows the matched phrase in context.
• Every request example renders in all three languages in the page source, so a crawler or an agent reading raw HTML sees cURL, Python and TypeScript rather than one of them.

Fixed

• The OpenAPI document resolved the seven compile-job operations against a base URL that returns 404. They carry their own server entry now, and a test resolves every path in the contract against a route handler so the contract cannot describe a URL the API does not serve.
• The MCP server's tool count is nine everywhere. list_worlds shipped on 3 September and was never announced, so three pages and that entry said eight.
• The signed package's file list was three different lists on three pages, one of them naming a file the exporter does not write. All three read the exporter's own list now.
• The scope description for ask:read said lexical retrieval while the Search page documented the same endpoint as hybrid retrieval.
• Internal review shorthand was published verbatim in a sentence on /docs/search.

Improved

• A production release covering the public site and the workspace shell. No API contract, limit or price changed, and no action is needed from an integration.

Added

• Release candidate, pending merge, and not live today. The pricing page separates plans that can be paid for now from those that start with a conversation; the terms gain governing law, a limitation of liability and a notice period; refunds are stated as one rule rather than two that disagreed; and the privacy text names the regimes it is written against. Dated by the day the work was completed, not by a release that has not happened.

Added

• The MCP server exposes nine read-only tools: list_sources, list_worlds, get_world, search_world, ask_world, get_object, get_relation, get_evidence and download_package.
• A Compiled World Package validator checks what is inside an export: that relations resolve, that every region sits inside its page, that the Turtle, JSON-LD and CSV describe the same graph, and that the package's own report counts what the package holds.
• Documentation covering the endpoint reference, the error catalogue, run events and the package format, with each request in cURL, Python and TypeScript.
• Compiling more sources than one compile can hold: a run of up to 128 documents is split into parts and followed as one run, with each part compiling to its own World. The parts are not merged, so each one is reviewed and used on its own.

Improved

• Preflight reads the real page count from the document where the format states one, and says so, rather than estimating from file size.
• Unpacking a large archive keeps the tab responsive.

Fixed

• A connector sync completes when a provider returns an incomplete row.
• A compile survives a closed tab — reopen it and the run continues, with no second charge for the reading.

Improved

• Compile progress is derived from persisted run events rather than from a timer, so a reload shows where the run actually is.
• A page estimate shows both the standard and the maximum processing boundary before a compile starts.

Improved

• The public path runs input, compilation, evidence, then straight into the workspace.
• Pricing is quoted in pages and dollars, with the machine-readable API contract available for integrations.