Skip to content

docs: replace fabricated local-machine claim in MarketOpportunity#232

Merged
operatoruplift merged 1 commit intomasterfrom
honesty/market-opportunity-narrative
Apr 28, 2026
Merged

docs: replace fabricated local-machine claim in MarketOpportunity#232
operatoruplift merged 1 commit intomasterfrom
honesty/market-opportunity-narrative

Conversation

@operatoruplift
Copy link
Copy Markdown
Owner

Summary

  • Rewrites the "Why now?" narrative in `src/sections/MarketOpportunity.tsx` away from "one assistant on your computer" / "on your machine instead of theirs"
  • New copy describes what the product actually is: one assistant that can sit across the SaaS apps you juggle, with approval + signed receipt for every action

Why

The web app is Vercel-hosted and routes prompts through Anthropic / OpenAI / Google / xAI / DeepSeek per user selection. It is not a local-only product. The desktop+Ollama path is roadmap-only (documented in FAQ + Privacy Policy). PRs #227#231 cleaned other surfaces; this finishes the homepage's last "on your machine" assertion.

Test plan

  • `pnpm check` (4/4: copy-check, capability-check, trust-gate, fabrication-rot-check)
  • `pnpm exec tsc --noEmit` (clean)
  • Visual inspection of MarketOpportunity "Why now?" narrative

The "Why now?" narrative said "one assistant on your computer can
replace the dozens of productivity apps you juggle today. We're
building it before big tech does, and putting it on your machine
instead of theirs."

The web app is Vercel-hosted and routes prompts through Anthropic /
OpenAI / Google / xAI / DeepSeek per the user's selection per turn.
It is not a local-only product. The desktop+Ollama path is roadmap-
only, documented as such in the FAQ and Privacy Policy.

Rewrite the narrative around what the product actually is:
- One assistant that can sit across many SaaS apps and move work
  between them (true: Gmail+Calendar via Google OAuth, more on the
  roadmap).
- Approval before every action and a signed receipt afterward
  (true: ed25519 receipts anchored on Solana via the audit-trail
  Anchor program).

This continues the honesty positioning sweep that PRs #227-#231 did
across Privacy / Compliance / ProblemStatement / Pricing / Comparison
/ FAQ / CloudVsLocal / dataService / ProductPage. After this lands,
the only remaining "computer/machine" framing on the site is the
explicit roadmap copy in the FAQ and Privacy Policy pointing at the
future desktop app.

Verification:
- pnpm check (4/4: copy-check, capability-check, trust-gate,
  fabrication-rot-check)
- pnpm exec tsc --noEmit (clean)
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 28, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
website Ready Ready Preview, Comment Apr 28, 2026 11:28am

@operatoruplift operatoruplift merged commit 2579c98 into master Apr 28, 2026
4 checks passed
operatoruplift added a commit that referenced this pull request Apr 28, 2026
#233)

The /app dashboard rendered three stat tiles with sublabels that did
not match what the code actually does:

- Chat sessions tile: "On your computer"
- Memories saved tile: "Local, encrypted"

Both values come from localStorage (chat-sessions-v2, memory-engine-v1).
That data lives in the browser, not on disk in the OS sense, and there
is no encryption applied to either. The "encrypted" claim is
particularly misleading because the encryption helpers in lib/encryption
have no callers from these features.

Replace both sublabels with "In this browser", which:
- Is literally true (localStorage is browser-scoped)
- Doesn't claim cryptographic protection that isn't there
- Doesn't imply "your data never leaves the device" — chat prompts are
  still routed through the AI provider the user picked

This matches the honesty positioning sweep landing across the homepage
in PRs #227-#232 (Privacy / Compliance / ProblemStatement / Pricing /
Comparison / FAQ / CloudVsLocal / dataService / ProductPage /
MarketOpportunity).

Verification:
- pnpm check (4/4: copy-check, capability-check, trust-gate,
  fabrication-rot-check)
- pnpm exec tsc --noEmit (clean)
operatoruplift added a commit that referenced this pull request Apr 28, 2026
)

Add 4 anchored patterns to scripts/fabrication-rot-check.mjs that fail
the build if a future PR reintroduces the local-machine fabrications
that PRs #231-#232 retired:

- "on your machine instead of theirs" -> retired in #232
  (MarketOpportunity)
- "Everything lives on your computer" -> retired in #231
  (dataService product card #1)
- "AES-256 encrypted local storage" -> retired in #231
  (dataService security section)
- "your data never leaves your environment" -> retired in #231
  (dataService security features.security)

Each pattern is anchored to the exact phrasing that was in the
retired copy. The COMMENT_LINE_RE skip means rule comments and
audit-trail commentary in code are still allowed, only live source
strings fail.

Total rules: 10 -> 14.

Verification:
- pnpm check: 4 passed (4/4: copy-check, capability-check, trust-gate,
  fabrication-rot-check) with 14 rules across 197 files.
- pnpm exec tsc --noEmit (clean - no source changes).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant