What changed, without the noise.

Improved

• / and /ko play a new recording of the compilation film, framed on each step, and phones play it again, opening on the full frame. The four stages are Read, Compile, Update and Trace (읽기, 컴파일, 업데이트, 근거 추적 on /ko).
• The three /guide videos, Explore, the MCP bridge and the API, are re-recorded on tavonel.com in their desktop and phone takes, with their English and Korean captions re-timed. The guide's manifest, /guide/manifest.json, records all three as recorded on live tavonel.com and names no exception.

Improved

• / and /ko open the compilation film on the full frame at every width. “Focus details” (“세부 내용 확대” on /ko) zooms in as before: two panes on a desktop, one pane of the source page on a phone.
• The second action on the home page, “Evaluate your documents” (“내 문서 평가” on /ko), is a bordered button with a document icon. It opens /evaluation and /ko/evaluation, as the link did.
• On the Home tab of /workspace the upload box comes straight after the workspace status, ahead of Needs attention, the compile and its results, including after a cancelled run. The status area has an “Upload sources” button that opens the file picker, or says uploads are closed on an account where they are, and the upload box is headed “Drop files, folders or ZIP here” for a returning workspace too.

Fixed

• Dropping a folder together with files on /workspace stages every item. Before this release only the folder was staged.
• A file dropped on / or /ko, or outside the upload box on /workspace, does not open in the browser tab. The home page moves focus to “Evaluate your documents” and neither reads nor keeps the file; /workspace brings the upload box into view and stages nothing.

Fixed

• A scanned document compiles when the reader gives a region a confidence of exactly 1.0. Before this release such a compile stopped at the receipt check, so a document that stopped there compiles when you run it again.

Added

• The second section of / and /ko ends with four public-document pages read by TAVONEL's reader: a receiver schematic and its parts list from NASA SP-5079, a scanned page of a NACA research memorandum, and a Korea Meteorological Administration page in Korean. Each page shows every region box the reader returned and one region's text exactly as the reader returned it, with the page's source, its licence and its run receipt.
• /benchmarks/gdp-pdf draws the run's two-arm design and its all-criteria pass counts as two figures, each read from the run's published report and described in text for screen readers.

Improved

• / and /ko open on a two-line statement, one sentence of support, one button with a link to evaluate your documents beside it, and the compilation film. On a phone the film opens on one pane of the source page, with the full frame one tap away.
• Below the film, the research figures are three rows, each with its receipt id, date and digest; the sample record shows its source, page, region and version; the change counts compare two complete compiles. The FAQ, the reading-difficulty notes, the Read links under each boundary and the link rows under the source workbench and the sample record have left the home page, and the home footer is compact.
• The customer-data sentence, the training-data statement and the rights sentence stay on the home page in their existing wording.
• /ko sets its home-page Hangul in a static subset of Wanted Sans in two weights, and / loads no Korean font.

Added

• /proof-collection/PROVENANCE.md has a Specimens section on the two pages in /proof-collection/specimens/: the public document each comes from and its licence, when it was read, what each cell holds, what its run receipt does not claim, and the SHA-256 that pins each run receipt and rights snapshot.

Improved

• The guide's manifest, /guide/manifest.json, says in its first recording line that guide-1-explore and guide-3-api were recorded on live tavonel.com, and that guide-2-mcp is the exception its last line describes.
• The MCP configuration example in the developer README, /developer/README.md, uses /absolute/path/to/tavonel-mcp.mjs as the placeholder for the server's path, as /docs/mcp does.

Fixed

• On a touch screen or below 1080 px, each “where” link under a chapter of /guide and /ko/guide is a full-size tap target, and a row that wraps sits clear of the row above it.
• Code, digests, IDs and coordinates are drawn in your system's monospace face whenever IBM Plex Mono has not loaded.

Added

• /docs/mcp has a section on the remote MCP endpoint, for clients that connect by URL instead of launching a local process, such as ChatGPT connectors and other web agents: how to connect, the OAuth flow step by step and the read-only scopes a connection gets. Its heading and its first note say it is not enabled in production, and on tavonel.com every URL in that section answers 404, so connect through the stdio server on the same page.

Added

• /docs/run-events describes change notifications: one signed POST to the endpoint registered for a workspace when a finished compile's candidate differs from the World your AI reads, with the field table, a Node.js snippet that verifies the signature, and how retries and duplicate deliveries behave.
• A notification activates nothing: the candidate waits for a person to approve it in the workspace. Notifications are set up per workspace with us, and on tavonel.com sending is switched off and no endpoint is registered, so none are sent.

Improved

• The workspace shows the processing-terms review only where accepting the terms is the step that opens processing for your files. Elsewhere, including a released workspace whose evaluation was refused or has ended, it offers Explore a compiled World. Nothing is switched on by this release, and online purchase stays closed on tavonel.com.

Improved

• /integrations says that compiling your own sources is set up with us, that you start each read-only import yourself, and that nothing is compiled until you start the compile. Its description of the source agent covers the --watch mode, which repeats the sync until it is stopped, and the retries inside a run, bounded by --retry-limit.
• /pricing describes each plan's page allowance as standard pages, without “verified”.
• /docs/upload shows the fields the upload capability returns, uploadUrl, expiresInSeconds, declaredMimeType and contentLength, in its prose and in the cURL, Python and TypeScript examples.
• The quickstart, the CLI page, the integration recipes and the developer README read the signing key's fingerprint from the v2 trust record, under keys[] for the active key.
• The MCP server's download_package names tavonel-verify-export.mjs, the verifier the developer channel ships, and channel.json carries the server's new digest.
• /status reports billing from whether a plan can be bought online, so on tavonel.com it says that checkout is closed and no plan can be bought.
• Home's support line says TAVONEL reads your PDFs, scans and office files, in English and Korean. /sources says in Korean that Korean document quality has not been measured and that HWP and HWPX are not supported, and /llms.txt uses the same wording as the pages it summarises.

Added

• /proof-collection/specimens/ publishes two one-page extracts, each read once by the OCR image the product runs: page 1 of NACA Research Memorandum RM L50C03 (1950), a U.S. government work, and page 1 of the Korea Meteorological Administration's September 2026 climate press release, under KOGL Type 1. Each comes with its crops and a run receipt that records the reader image digest, every region the reader returned, the crop rule fixed before the run, and what the run does not claim, any accuracy figure among it.
• Home shows the two pages as a strip under its actions on preview deployments only; tavonel.com does not render it.

Improved

• /privacy and /subprocessors describe Vercel Web Analytics, run by our hosting provider: what it counts and receives once you allow analytics, that it uses no cookies or storage on your device, and what it is never sent. The cookie table lists the two session-storage entries the site keeps in your tab and does not send.
• Home's four film stills are AVIF files, with a WebP copy of the same frame for a browser without AVIF. The first two stages show a new frame from the same recording.

Improved

• On a phone, each link on /developers is a full-size tap target clear of its neighbours: the two gate actions sit in a row of their own, and each reference sentence is its own list item.
• /docs/mcp prints the Windows configuration path with one backslash between folders and sets file paths as code, drawn in a monospace face on every system, Korean Windows included. Its configuration examples use /absolute/path/to/tavonel-mcp.mjs as the placeholder.
• Each chapter of /guide and /ko/guide says under its heading whether its steps need an API key.
• The MCP bridge walkthrough is re-recorded in its desktop and phone takes, with the same English and Korean captions, so it shows /developers and /docs/mcp as they are now. The takes come from a local production build of that release rather than from tavonel.com, and the guide's manifest says so.
• /changelog lists the releases from 7 to 19 October, each dated by the day it reached tavonel.com.

Improved

• Every public page is built from one set of colour tokens, one type scale in Wanted Sans and one page container, and follows one of six page templates. From 900px the header carries its main action beside the navigation.
• On Home, the Evidence Line outlines the region it points at on the source page, and its coordinate label is set in ink. A line opened from the keyboard appears at once, and with reduced motion nothing on the workbench animates.
• Sign-in says whether the plan you picked can be bought online: Team reads “Team is not sold online today.” with Request Team access beside it. When the purchase state cannot be read, the heading is “Sign in to TAVONEL.” and the page promises no checkout.
• Checkout, billing-portal and pilot-access refusals are shown as sentences without the raw error code, and screen readers announce them as alerts.

Added

• /guide and /ko/guide walk through the public product chapter by chapter, from opening the public World to connecting the MCP bridge, with a glossary. Every quoted sentence on them is the live text of the page it quotes.
• Three recorded walkthroughs, of Explore, the MCP bridge and the first API and CLI calls, each in a desktop and a phone take with English and Korean captions and a transcript. They are screen recordings, and none of them plays by itself.
• Try it, with no key opens /docs/quickstart and sits on /developers too: three unauthenticated reads that run from the page, and where a response sends a Content-Digest the page checks it over the bytes received.

Improved

• The cookbooks index is linked from /resources and from the documentation hub, and listed in the sitemap.
• Every changelog entry is anchored at the date it shows, a fragment published earlier still opens its entry, and the Atom feed takes its date from its newest entry.
• The getting-started pages state no time to a first result.

Fixed

• A campaign note on /benchmarks shows the scoring machine's absolute path as “[local path removed]”, and the fold says so. The committed campaign board keeps the note as recorded, under the same sha256.

Added

• GET /api/documents answers 503 with QUARANTINE_LIST_UNAVAILABLE when the document listing cannot be read, and its response carries a partial marker naming the documents that could not be loaded. The workspace shows both states as such.
• The OpenAPI document publishes the upload confirmation operation and developer key creation.

Improved

• The upload capability, upload confirmation, developer key create and rotate, and audit operations publish the response bodies those routes return.
• Sources still being processed appear in the document list as stored.

Added

• consumer-context.mjs joins the files published at /developer/, pinned by sha256 in channel.json like the others. The CLI and the MCP server load it from their own directory, so install every file channel.json lists into one directory and check each digest.
• The CLI and the MCP server accept an optional consumer context in TAVONEL_CONSUMER_CONTEXT and send it with every request. With TAVONEL_CONSUMER_CONTEXT_REQUIRED=true they refuse any read whose response does not acknowledge that context. This is local synthetic evidence only: the production API does not acknowledge the context headers, so the required mode refuses every read made against it.

Improved

• With neither variable set, the CLI and the MCP server send no context headers and do not load consumer-context.mjs.
• The source agent and the developer README are republished with new digests in the same channel. Intake for your own sources is arranged with us, as the quickstart says.

Added

• Beneath the headline, a band of published research results, each printed with its denominator, the condition its claim has to carry and a link to the receipt it came from. The figures are read from the generated claims pack rather than typed into the page, and the low-quality-scan result is printed with the others.

Improved

• The headline is the outcome, “Turn documents into context your AI can cite.”, with “The Knowledge Compiler for AI” above it. The Korean entry page carries its literal translation, and the browser tab and link previews use the same sentence.
• The first action, in the header and on the page, opens the public sample (“Open the compiled sample”). “Bring your own documents” goes to the contact page, where intake for your own sources is arranged with you.
• The four recorded film cuts are unchanged, and their still frames are new frames taken from the same cuts. On a desktop each stage opens on the enlarged reading view where both panes carry content, and on the full frame where they do not; Focus details switches between the two.
• On a phone the passage being read is printed as text directly above the film, and the analytics consent notice stays clear of both.

Improved

• The headline is “Knowledge your AI can trust.”, and “AI가 믿고 사용하는 지식.” on the Korean entry page.
• The analytics consent card appears once you scroll down the page or after eight seconds, whichever comes first, and Analytics preferences in the footer opens it at once. Analytics still loads only after consent.
• Each film stage's reading line quotes text that is on screen in that stage.
• On a desktop, hovering or focusing a source region draws a line from the passage to that region's box on the page, labelled with the record's page and coordinates.
• The phone menu is a single icon control, the phone footer is a two-column grid, and cards share one corner radius.

Improved

• The four-stage film, Files, Organize, Updates and Use with AI, plays directly under the title.
• Fit, the whole frame, is the default at every width. Focus is a zoom you choose, and on a narrow screen its controls sit in a toolbar outside the film.

Improved

• Below the headline, a recording of a prepared source inspection, with its own crop on a phone. Nothing is decoded until you press play.
• Product presents the public World and the outputs bound to its sources, and How it works keeps the six-step process. Long source, method and version descriptions are folded into disclosures.
• The GDP.pdf result moves from Home to Benchmarks, where its report and conditions are unchanged.

Added

• /how-it-works follows a source through six steps, from a versioned input to a new version when the source changes, and it is in the navigation and the sitemap.
• Home prints the GDP.pdf two-arm result, in which compiled context scored below the PDF alone, labelled with its historical, unofficial conditions.

Improved

• The four-cut illustrative film plays directly below the headline, and the source workbench follows it as the second scene.
• Product presents what the outputs are used for.

Improved

• Home centres the real filing and its selectable passages, and its source, rights and version details open as disclosures.
• Public pages share one typography, one set of surfaces and one navigation. Evidence prose has a readable width, and changelog links keep their 44px touch targets.

Added

• /evaluation and /ko/evaluation set out how an evaluation of your documents is agreed: permissions, questions, limits, costs and evidence quality before processing begins. Both have share cards and are in the sitemap.

Improved

• Home opens on a source page beside the passage read from it, with region selection linked between the two and the context the passage needs stated beside it. The illustrative walkthrough is a closed disclosure.

Added

• /product/compiled-world lists the files emitted for the public sample behind Explore, with each file's format, size and content digest and a preview of its content.

Improved

• /product/continuous-knowledge opens on “See what changed before you activate it.”: compile a candidate, compare the versions, and choose what becomes current, with the replaced version kept intact and readable.

Improved

• The homepage leads with a source-verifiable outcome, puts How it compiles beneath the headline, and opens the five-stage specimen on Evidence.
• The new first screen supersedes the 20 September entry-page opening; the source-linked sample remains available further down the page.
• Visitors can move from the public Compiled World and its source regions to Pricing, where the consultation path is explained.
• The historical R-01 research result names its denominator, receipt and weak-scan limitation instead of suggesting live-service model superiority.

Added

• 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

• 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 read-only MCP release record now names list_worlds, which was included in the 3 September tool set.
• 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.

Added

• Pricing shows plan limits and access conditions. The Terms name governing law, liability limits and price-change notice; Refunds distinguishes invitation-only access from paid-plan rules; Privacy names the data-protection regimes it addresses; Trust lists the scope of provided controls.

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

• 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.

Added

• API contract 2026-09-02.1 adds GET /runs/{runId}/events, which replays a run's persisted events after Last-Event-ID and then streams new ones, and POST /reviews, which records an Accept, Edit or Reject decision on a piece of evidence from a signed-in browser session.

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.