Skip to content

fix(honesty): future-tense completed-autonomy overclaims on $0/proof=0 surfaces#553

Closed
Victor "David" Medina (Victor-David-Medina) wants to merge 1 commit into
mainfrom
claude/honesty-rail-overnight-overclaims
Closed

fix(honesty): future-tense completed-autonomy overclaims on $0/proof=0 surfaces#553
Victor "David" Medina (Victor-David-Medina) wants to merge 1 commit into
mainfrom
claude/honesty-rail-overnight-overclaims

Conversation

@Victor-David-Medina

Copy link
Copy Markdown
Collaborator

Routed to claude-console by the adversarial hardening cascade (HIGH honesty-rail finding).

What was wrong

The console asserted completed autonomous sends on a fresh $0 / proof_events=0 account — directly contradicting the locked positioning "AI prepares. You approve. We never auto-send."

  • DailyPulse — a hardcoded ranOvernight: 2 mock rendered as a live emerald "2 ran overnight" pill
  • MorningBriefCard — "Ran overnight" badge + "Ran overnight. Tap to review"
  • FocusModeClient — "Your AI team scans overnight..."
  • SmartInsight — "Your AI team scanned overnight and found these"
  • WelcomeTour — "AI scans overnight while you sleep"

A send never runs without owner approval, and none has run at all (proof_events=0). "Ran overnight" is an overclaim a sharp buyer (or an honesty audit) catches.

The fix (cascade guidance: gate/future-tense, keep the reassurance)

All completed-/active-autonomy claims → "prepared/prepares overnight" (true in every account state — the AI does prepare; only the send awaits approval).

Unchanged (honest): "first brief lands tomorrow at 7am", "we never auto-send anything", empty-state "actions will appear ... overnight".

Scope discipline

Claim-boarded; collision-checked (the 3 open console PRs #517/#430/#429 don't touch these files); branched off fresh origin/main. Copy-only — no color/contrast change, so it won't trip the brand ratchet.

Co-authored with Claude (claude-console lane).

…0 surfaces

The console asserted COMPLETED autonomous sends ("ran overnight", a hardcoded ranOvernight:2 mock pill, "scanned overnight and found these") on a fresh $0/proof_events=0 account — contradicting the locked "AI prepares. You approve. We never auto-send." A send never runs without owner approval, and none has run at all (proof_events=0), so "ran overnight" is an overclaim.

Fix (per the adversarial cascade: gate/future-tense, keep the reassurance):
- DailyPulse: ranOvernight -> preparedOvernight
- MorningBriefCard: "Ran overnight" badge + caption -> "Prepared overnight"
- FocusModeClient: "scans overnight" -> "prepares overnight" (7AM-tomorrow promise kept)
- SmartInsight: "scanned overnight and found these" -> "reviewed ... and surfaced these for your approval"
- WelcomeTour: "AI scans overnight while you sleep" -> "AI prepares your next actions overnight"

Honest future promises ("first brief lands tomorrow at 7am", "we never auto-send anything") are unchanged.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 25, 2026

Copy link
Copy Markdown

Someone is attempting to deploy this pull request to the davidmedina-8534's projects Team on Vercel.

No GitHub account was found matching the commit author email address.

To deploy this pull request, the commit author's email address needs to be associated with a GitHub account.

Learn more about how to change the commit author information.

@vercel

vercel Bot commented Jun 25, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
relaylaunch-console Error Error Jun 25, 2026 4:49pm

@github-actions

Copy link
Copy Markdown

🛡️ Cascade Quality Score: 100/100

Category Score Status
TypeScript 20/20
ESLint 20/20
Brand Compliance 15/15
Test Suite 25/25
Build 20/20

Threshold: 85/100 | Result: PASS ✅

@Victor-David-Medina

Copy link
Copy Markdown
Collaborator Author

Superseded by the clean-author replacement PR with the same honesty copy fix. #553 was blocked by Vercel preview deployment.

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