docs(README): retire "runs on your computer" claim, align with shipped state#247
Merged
operatoruplift merged 1 commit intomasterfrom Apr 28, 2026
Merged
Conversation
…d state
The repo README's headline claim contradicted the line two sections
below it ("This is a Next.js 16 app deployed on Vercel"). Two
internally-inconsistent claims about hosting on the same page is the
exact pattern the homepage honesty sweep (#225-#246) was retiring.
Three changes:
1. Top pitch paragraph:
- "It runs on your computer (not a cloud), and every action waits
for your tap." was replaced with "The web app pauses for your
tap before any action and emits a signed receipt afterward. The
desktop+Ollama build on the roadmap removes the provider hop
entirely for users who need full on-device inference."
- This matches the homepage Privacy Policy + Compliance + blog
post copy that landed in the sweep.
2. "Pick any AI" bullet:
- "Claude, ChatGPT, Gemini, Grok, or a model running on your
laptop via Ollama" -> "Claude, ChatGPT, Gemini, Grok per turn
(the desktop build adds Ollama on the roadmap)"
- Ollama as a roadmap is honest; framing it as already-shipped
was not.
3. CI checks section:
- "grep-guards: copy-check, capability-check, trust-gate" ->
adds fabrication-rot (the 4th guard, covering 20 anchored
patterns of retired fabrications).
- The honesty-regression description now lists local-machine
claims (Runs on your computer, AES-256 encrypted local storage,
Your agent ran locally, Encrypted on your computer) alongside
LLM Council / Gold Agent / dev-jargon items.
Verification: pnpm check 4/4 passes (20 fabrication-rot rules clean,
no source-text changes that would trip a guard).
|
Deployment failed with the following error: Learn More: https://vercel.com/operatoruplift?upgradeToPro=build-rate-limit |
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.
Summary
The repo README claimed "It runs on your computer (not a cloud)" two paragraphs above "This is a Next.js 16 app deployed on Vercel." Two internally-inconsistent claims about hosting on the same page is the exact pattern the homepage honesty sweep (#225–#246) was retiring.
Changes
Why
A documentation surface has the longest shelf life — anyone discovering the project from GitHub reads the README. Leaving the centerpiece of the cleaned-up fabrication intact in the README would have meant the next person opening the repo lands on a contradiction the rest of the codebase has already walked back from.
Test plan