docs: explain the token economics of surfaces#182
Merged
Conversation
The "Faster, and fewer tokens" bullet asserted the benefit without saying why. Replace it with the concrete mechanism — a standalone HTML document re-sends its whole design system on every render, while a surface sends only the content and the viewer supplies the chrome — and add a short "Token economics" section with a measured before/after table (output tokens, generate-both-ways). Docs-only; empty changeset (no release). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The "Faster, and fewer tokens" bullet in the README asserted the benefit but never said why. This makes the case concrete:
## Token economicssection with a measured before/after table.On the numbers
The percentages come from a generate-both-ways measurement: each artifact was authored as a full standalone HTML document and as the equivalent surface, then the output was tokenized and compared. They're rounded and stated modestly — the spread is the honest part (structured surfaces like diagrams/JSON/tables save ~80–90%; an interactive HTML mockup still saves ~40% by inheriting the viewer's theme rather than shipping its own).
Docs-only; empty changeset (no release).
🤖 Generated with Claude Code