docs: show the explanation timeline in the README - #3
Merged
Conversation
The only screenshot showed the live session giving advice, which is the half a sceptical reader already distrusts: an app telling you your tone is wrong, with nothing behind the claim. The timeline is the other half, and it was not pictured. The new one is from the scripted demo, so it needs no microphone. It shows the two tracks kept apart — acoustic read from the waveform, semantic read from the transcript — and both reminders the demo fires, each carrying the arithmetic that fired it: loudness 72% and a very fast pace for +19, the AI reading "aggressive" at intensity 90 for +36, the matched phrasing for +9, and the sentence that was on screen at the time. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
The only screenshot showed the live session giving advice — which is the half a
sceptical reader already distrusts: an app telling you your tone is wrong, with
nothing behind the claim.
The timeline is the other half, and it was not pictured.
The new screenshot comes from the scripted demo, so it needs no microphone. It
shows the two tracks kept apart — acoustic read from the waveform, semantic read
from the transcript — and both reminders the demo fires, each carrying the
arithmetic that fired it:
That is the claim and its evidence in one frame.
Verified:
tsc -bclean,npm test163/163.🤖 Generated with Claude Code