惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
量子位
M
MIT News - Artificial intelligence
Y
Y Combinator Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Google DeepMind News
Google DeepMind News
Hugging Face - Blog
Hugging Face - Blog
博客园_首页
雷峰网
雷峰网
I
InfoQ
罗磊的独立博客
博客园 - 聂微东
酷 壳 – CoolShell
酷 壳 – CoolShell
大猫的无限游戏
大猫的无限游戏
D
Docker
H
Hackread – Cybersecurity News, Data Breaches, AI and More
腾讯CDC
博客园 - 三生石上(FineUI控件)
The GitHub Blog
The GitHub Blog
K
Kaspersky official blog
P
Privacy & Cybersecurity Law Blog
S
SegmentFault 最新的问题
T
Threat Research - Cisco Blogs
H
Help Net Security
小众软件
小众软件
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
C
CERT Recently Published Vulnerability Notes
WordPress大学
WordPress大学
T
Tenable Blog
T
The Blog of Author Tim Ferriss
C
Cisco Blogs
Simon Willison's Weblog
Simon Willison's Weblog
博客园 - Franky
A
Arctic Wolf
T
Threatpost
Scott Helme
Scott Helme
C
Cybersecurity and Infrastructure Security Agency CISA
D
Darknet – Hacking Tools, Hacker News & Cyber Security
T
The Exploit Database - CXSecurity.com
G
GRAHAM CLULEY
Security Latest
Security Latest
Spread Privacy
Spread Privacy
L
LINUX DO - 热门话题
V
Vulnerabilities – Threatpost
P
Privacy International News Feed
S
Schneier on Security
Latest news
Latest news
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
C
Cyber Attacks, Cyber Crime and Cyber Security
C
CXSECURITY Database RSS Feed - CXSecurity.com

Hacker News: Show HN

PurrrrrFocus: Pomodoro Timer App - App Store Workflow Engine — Multi-Step Orchestration for Bun RapidPhoto: Pro Photo Editor App - App Store GitHub - DheerG/swarms: Achieve extraordinary results with claude code across a variety of tasks SPICE simulation → oscilloscope → verification with Claude Code — Lucas Gerads Show HN: VCoding – A 5 MB native Windows IDE with no dynamic dependencies Show HN: LLMs don't hallucinate because they're bad at math, it's the format GitHub - Agent-FM/agentfm-core: AgentFM is a peer-to-peer network that turns everyday computers into a decentralized AI supercomputer. AgentFM lets you run massive AI workloads directly across a global mesh of idle CPUs and GPUs. Show HN: Tracking Top US Science Olympiad Alumni over Last 25 Years GitHub - Potarix/agent-hub: One place to talk to all your agents Show HN: Runtime security for AI agents(injection,tool abuse, data exfiltration) GitHub - dubeyKartikay/lazyspotify: Terminal Spotify client for macOS and Linux GitHub - the-banana-tool/king-louie: Easy to use GUI Personal AI Assistant. Win/Linux/Mac. Show HN I made my vacation rental bookable by AI agents–no Airbnb, 0% commission GitHub - basteez/jsf-autoreload: maven plugin to enable hot reload on jsf projects uvm32/hosts/host-gdbstub at main · ringtailsoftware/uvm32 GitHub - labsai/EDDI: Config-driven engine that turns JSON into production-grade AI agents. Multi-agent orchestration, 12+ LLM providers, MCP/A2A protocols, RAG, persistent memory, and enterprise compliance (EU AI Act, GDPR, HIPAA). Built on Quarkus. GitHub - glitchnsec/fortyone-oss: AI Executive Assistant Platform Quickstart | Alien GitHub - muxshed/shed: One stream in, or many. Every destination, simultaneously. No cloud middleman, no per-channel fees, no limits. GitHub - ocrbase-hq/ocrbase: 📄 PDF/IMG ->.MD/JSON Document OCR API for PaddleOCR and GLMOCR. Self-hostable. GitHub - impactjo/home-memory: MCP server that lets your AI assistant remember everything about your home. GitHub - Sets88/dbcls: DbCls is a powerful terminal database client that supports various databases GitHub - neptun2000/heor-agent-mcp GitHub - SeanFDZ/macmind: Single-layer transformer in HyperTalk for the classic Macintosh RollQuation: Math Puzzles - Apps on Google Play GitHub - dropbox/witchcraft Show HN: Agent-cache – Multi-tier LLM/tool/session caching for Valkey and Redis GitHub - opentalon/opentalon: OpenTalon is an open-source platform built from the ground up in Go as a robust alternative to OpenClaw LinkedIn™ 职位抓取工具 - Chrome 应用商店 GitHub - EdoardoBambini/Agent-Armor-Iaga: AI agents are getting tool access — shell, file system, databases, APIs, secrets. But **nobody is governing what they actually do with it**. Frameworks like LangChain, CrewAI, AutoGen, and Claude Code give agents the power to execute. Agent Armor gives you the power to control, audit, and approve every single action before it happens. HN Vibes — Week 15, Apr 7–13 2026 GitHub - chojs23/ec: Easy terminal-native 3-way git mergetool vim-like workflow GitHub - SethPyle376/hiraeth: Local AWS emulator focused on fast integration testing, with SQS support, SQLite-backed state, and a debug-friendly web UI. GitHub - JakOb-dotcom/cloud-sandbox-security-analysis: Technical analysis and Proof of Concept (PoC) regarding environment variable exfiltration in containerized cloud sandboxes via side-channel data leaks. Springboards - Flint Alpha Show HN: A simpler coding agent harness GitHub - audiodude/sudomake-friends GitHub - 256thFission/mini-mythos: OSS clone of Anthropic’s Mythos harness to locate C/C++ memory vulnerabilities Show HN: OpenParallax: OS-level privilege separation for AI agent execution Hacker News Sorted - Chrome 应用商店 Show HN: How to Install Docker on Ubuntu 24.04 LTS: Complete 2026 Guide GitHub - himanshudongre/smriti GitHub - sverrirsig/claude-control: macOS desktop dashboard for monitoring and managing multiple Claude Code sessions GitHub - ory/dockertest: Write better integration tests! Dockertest helps you boot up ephermal docker images for your Go tests with minimal work. Chiral - Chrome 应用商店 Show HN: Two Claudes collaborating through shared memory on a $100 mini-PC GitHub - pmichaillat/latex-cv: Minimalist LaTeX template for academic CVs GitHub - oguzbilgic/posse: A web UI for Anthropic Managed Agents. GitHub - sshiraz/depsly: Dependency risk analysis tool for npm packages ABI Add safari/agent-harness — Safari browser automation via safari-mcp by achiya-automation · Pull Request #212 · HKUDS/CLI-Anything GitHub - Halfblood-Prince/trustcheck: Verify PyPI package attestations and improve Python supply-chain security GitHub - oguzbilgic/kern-ai: Agents that do the work and show it. GitHub - bruits/satteri: High-performance Markdown and MDX processing for the JavaScript ecosystem GitHub - tylergibbs1/feedstock: High-performance web crawler and scraper for TypeScript, powered by Bun and Playwright GitHub - Grimm67123/grimmbot: The self-improving sandboxed and open-source AI agent. With persistent memory and scheduling. GitHub - whitevanillaskies/whitebloom: Local whiteboard that blooms. GitHub - hwdsl2/docker-whisper: Docker image for a self-hosted Whisper speech-to-text server with speaker diarization and OpenAI-compatible transcription and translation APIs. Powered by faster-whisper. Supports all Whisper models, NVIDIA GPU (CUDA) acceleration, JSON/SRT/VTT output, SSE streaming, offline mode, and multi-arch (amd64, arm64). GitHub - yisding/reviewwiggum GitHub - MarwanAlsoltany/serrors: Structured errors for Go: sentinel hierarchies, typed data, custom formatting, and slog integration. GitHub - soatok/age-php GitHub - Luthiraa/markitme GitHub - stagas/rtdiff: realtime git diff gui and AI-assisted commits GitHub - tombedor/excalicharts GitHub - wh1le/excalidraw-edit: Open and edit .excalidraw files from the terminal. Offline, auto-saves to disk. MalExt Sentry - Malicious Extension Scanner - Chrome 应用商店 GitHub - syi0808/asciianimesvg: Generate animated ASCII art SVGs from text. CLI, Rust library, WASM, and web editor. GitHub - zaina-ml/ml_forge: A visual-based graph node editor for training computer vision models. GitHub - anakin87/llm-rl-environments-lil-course: 🌱 A little course on Reinforcement Learning Environments for evaluating and training Language Models GitHub - takaakit/superpowers-uml: Superpowers-UML modifies Superpowers to ensure a software development workflow in which AI agents design through UML modeling. AdriByte Studio - Sviluppo Web e Soluzioni Digitali GitHub - chouligi/angel-copilot: Your personalized Angel Investment Advisor Show HN: MoodSense AI (ML and FastAPI and Gradio, Deployed on Hugging Face) Moodsense Ai - a Hugging Face Space by aman179102 GitHub - agenteractai/lodmem: Level Of Detail Context Management for Agents GitHub - ostefani/subnetlens: A fast, concurrent network scanner with a TUI and plain-text CLI, built in Go. It discovers live hosts on your network, scans their open ports, resolves hostnames, and fingerprints operating systems—delivered. Cyber Pulse: Agentic Intel - Apps on Google Play Whisper API: Self-Hostable Speech to Text Transcription The Agent-Web Protocol Stack: A Research Thesis GitHub - msmarkgu/RelayFreeLLM: A restful API designed to route user prompts to various AI model providers. Show HN: Provepy – A Python decorator that proves your code using Lean and LLMs Show HN: Pardonned.com – A searchable database of US Pardons GitHub - patrickdappollonio/dux: Dux is a terminal UI that lets you run multiple AI coding agents side by side, each in its own git worktree, with full companion terminals, macros, commit generation, and a command palette that knows more tricks than you do. kMC Crystal Simulator Show HN: HyperFlow – A self-improving agent framework built on LangGraph GitHub - stef41/vibescore: 🎵 Grade your vibe-coded project. One command, instant letter grade across security, quality, dependencies, and testing. GitHub - stef41/lmscan: 🔍 Detect AI-generated text and fingerprint which LLM wrote it. Open-source GPTZero alternative. Zero dependencies, works offline. imgur.com GitHub - visionscaper/collabmem: Enabling long-term collaboration with Agentic AI - building up episodic and world model memory over time with in-context awareness 在 Steam 上购买 FriedrichAI: Offline AI 立省 10% GitHub - atripati/ark: AI Runtime Kernel — a context operating system for AI agents. Eliminates tool bloat, loads only what’s needed, and gives LLMs their reasoning space back. GitHub - nowork-studio/toprank: Open-source Claude Code skills for SEO, SEM, Google Ads GitHub - tacomanator/sash: Lightweight macOS menu bar app for reliably cycling through windows of the current application. Appents | Social Media Management for Product-First Teams GitHub - pnhoang/youtube-spam-blocker: Automatically detects and hides spam messages in YouTube Live chat. Set rate limits, keyword filters, and block repeat offenders. GitHub - decisionnode/DecisionNode: CLI + Local MCP - A shared structured memory store across Claude Code, Cursor, Windsurf, Antigravity, and every MCP client. Semantically queryable. GitHub - AvaCodeSolutions/django-email-learning: An open source Django app for creating email-based learning platforms with IMAP integration and React frontend components. The $100K Gap in Kubernetes Security Tooling Function Calling Harness: From 6.75% to 100%
Verbalized probability-distribution sample of 10 ranked answers + "Mixture of Eccentrics" synthesis
spinchange · 2026-05-03 · via Hacker News: Show HN

Verbalized probability-distribution sample of 10 ranked answers + "Mixture of Eccentrics" synthesis

---
name: verbalized-sample
description: Produce a verbalized probability-distribution sample of 10 ranked answers, outcomes, or interpretations to a prompt — modal answer first with an estimated probability mass, followed by nine successively lower-probability alternatives expressed as lower bounds. Use this skill whenever the user says "I need a verbalized sample of...", "give me a verbalized sample", "verbalized distribution", or otherwise asks for a ranked-probability sweep of possible answers. Also use it when the user explicitly wants to surface the tails of a response distribution, see what RLHF might be smoothing over, or compare the modal answer against unconventional alternatives. The skill exists to counteract mode collapse — to force exploration of the long tail that single-answer responses suppress.
---
# Verbalized Sample
## What this skill does
A normal answer collapses Claude's distribution over possible responses down to roughly one — the modal, RLHF-favored, safest-sounding answer. That collapse is often appropriate, but it hides creative, unconventional, or low-probability-but-high-information alternatives that Claude is actually capable of producing.
This skill produces a **verbalized sample of 10 answers** drawn from across the response distribution, ranked from modal to tail, each annotated with a probability estimate. The user gets a structured view of *where Claude's mass actually sits* on a given prompt, not just the mode.
## Output format
Always use this exact structure. Do not deviate.
```
**Verbalized sample: [restate the prompt in ≤10 words]**
1. [modal answer] — p ≈ X%
[1–3 sentences of reasoning or content]
2. [next most probable] — p ≳ Y%
[1–3 sentences]
...
10. [tail answer] — p ≳ Z%
[1–3 sentences]
**Mixture of Eccentrics:** [synthesis of the most coherent cluster found in the lower half (positions 6–10), naming the underlying frame those answers collectively gesture at. If the tail does not form a coherent cluster, say so plainly: "The tail of this distribution doesn't form a coherent eccentric cluster — the unconventional answers here are unconventional in different dimensions."]
**Notes on the distribution:** [2–4 sentences reflecting on the shape — is it peaked or flat? where is the interesting tension? what kinds of answers did you have to push past mode collapse to surface? Acknowledge any harm-flagged answers at sample level here.]
```
**On harm flags:** if any answer in the sample suggests harm to self or others, illegal action, or significant material risk, append a short flag inline at that answer like `⚠ flag: brief reason` after the prose. Do not refuse to include the answer — the user has invoked this skill specifically to see the raw distribution. The flag is a signal for the reader, not a censorship layer. Address flagged answers briefly in the distribution notes too. Do not put a blanket disclaimer at the top of the sample; top-level disclaimers become wallpaper and the per-answer flag carries the actual signal.
## The probability rules
These rules exist because naive probability-ranking tends to drift into either fake precision or meaningless hedging. Follow them strictly.
1. **Position 1 uses `p ≈ X%`** (approximately equal). This is the modal answer's estimated share of the distribution. Be honest: a sharply-peaked prompt might have p ≈ 75%; a genuinely open prompt might have p ≈ 18%.
2. **Positions 2–10 use `p ≳ Y%`** (greater-than-or-approximately). These are **lower bounds**, not point estimates. A lower bound is honest about tail uncertainty — you don't know exactly how much mass sits on the 7th-most-likely answer, but you can defensibly say "at least 3%."
3. **The floor is 2%.** Below 2%, lower-bound notation stops carrying real information. Treat `p ≳ 2%` as meaning "this is in the tail; precise mass is not separately estimable from adjacent tail answers." Do not go below 2%. If you find yourself wanting to write `p ≳ 0.5%`, the honest move is `p ≳ 2%` and an acknowledgment that ordering at the tail is partly ordinal rather than fully calibrated.
4. **Probabilities must be non-increasing** down the list. p₁ ≥ p₂ ≥ ... ≥ p₁₀. If two answers feel genuinely tied, give them the same lower bound and order them by some secondary criterion (specificity, novelty, etc.).
5. **The ten probabilities should not sum to 100%.** They explicitly don't cover the full distribution — there's residual mass on the unenumerated tail. Resist the urge to make them tidy.
6. **Use a wide dynamic range.** If position 1 is p ≈ 40% and position 10 is p ≳ 35%, you have not actually sampled the tail — you've listed ten variations of the mode. A healthy sample typically spans at least an order of magnitude (e.g., 40% down to 2–3%).
## How to actually generate the sample
The hard part is not formatting. The hard part is producing genuine diversity instead of ten paraphrases of the modal answer. Here's the procedure:
**Step 1 — Establish the mode honestly.** Write out the answer you would give if asked normally. That's position 1. Estimate its probability mass: how dominant is this answer relative to plausible alternatives? Sharply factual prompts ("capital of France") yield p ≈ 99%. Genuinely open prompts ("what should I do this weekend") might yield p ≈ 15%.
**Step 2 — Generate adjacent alternatives (positions 2–4).** These are the "obvious other answers" — common variations a thoughtful person would also consider. Still high-probability, still mostly within the consensus.
**Step 3 — Push into the middle tail (positions 5–7).** These are answers that are reasonable but unconventional, or that reflect a different framing of the prompt, or that a domain expert (rather than a generalist) would offer. This is where RLHF-suppressed material starts surfacing: contrarian-but-sound takes, answers that assume a different user intent, answers from underrepresented schools of thought.
**Step 4 — Reach for the tail (positions 8–10).** These should feel slightly uncomfortable to write. Not wrong, not absurd, but answers that the modal Claude would not volunteer: weird-but-coherent reframings, fringe-but-not-crank perspectives, answers that take the prompt seriously in an unusual way, answers from genuinely different aesthetic or philosophical commitments. **If positions 8–10 don't feel meaningfully different from positions 1–3, the sample has failed.**
**Step 5 — Calibrate probabilities backward.** Once all ten are written, assign probabilities. Check: does p₁ honestly reflect how dominant the mode is? Do the lower bounds on 2–10 monotonically decrease? Does the spread span a meaningful range?
**Step 6 — Identify the eccentric cluster.** Look at positions 6–10 and find the most coherent cluster — the 2–4 tail answers that share an underlying frame (a reframing of the question, a shared stakeholder reorientation, a shared timescale shift, etc.). The cluster does not have to be contiguous. If the lower half is a genuine grab bag with no coherent cluster, that's a valid finding — say so in the Mixture of Eccentrics section. Do not force a synthesis where none exists; a forced synthesis is mush and worse than honest absence.
**Step 7 — Apply harm flags where appropriate.** Scan the sample for any answer that suggests harm to self or others, illegal action, or significant material risk. Append an inline `⚠ flag` to those answers with a brief reason. This is not censorship — the answer stays in the sample. The flag tells the reader which answers warrant extra reading.
**Step 8 — Write the distribution notes.** Briefly reflect on the shape. This is not a summary; it's metadata about the sample itself. Was the prompt peaked or flat? Where did mode collapse have to be actively resisted? Are there clusters of similar answers, or is the distribution genuinely multimodal? Acknowledge any flagged answers here.
## Why there is no modal-cluster synthesis
The output format deliberately omits any synthesis of the top of the distribution, even though positions 1–3 typically share a frame. This is intentional. The ranked list itself is already the structured view of the consensus — position 1 is the modal answer in its cleanest form, and positions 2–3 are the variations it was almost. A modal-cluster synthesis would just restate something the user can already see by reading the top of the list.
The tail is asymmetric. Positions 6–10 are each unconventional along their own axis (different framing, different stakeholder, different timescale). Reading them as a list gives you four separate weird-but-good answers but does not give you the underlying *move* they're collectively making. The Mixture of Eccentrics synthesis does work the user cannot do by simply reading the list — it identifies the shared frame.
So: ranking serves the consensus; synthesis serves the eccentrics. Same data, different aggregation, because the two ends of the distribution are doing different things and need different treatment. Do not add a modal-cluster synthesis back in thinking it was an oversight — its absence is load-bearing.
## What counts as a "good" tail
Tail answers (positions 7–10) should pass at least two of these tests:
- **Different framing**: reinterprets what the prompt is really asking
- **Different population**: an answer the modal user wouldn't give but a specific subgroup would
- **Different ontology**: takes the question seriously under different background assumptions
- **Different aesthetic**: reflects a coherent taste or sensibility distinct from the mainstream
- **Different timescale**: optimizes for a different time horizon than the obvious one
- **Different stakeholder**: prioritizes a party other than the implied beneficiary
Tail answers that are merely "the same answer with a contrarian disclaimer" do not pass. Tail answers that are confused, incoherent, or obviously wrong also do not pass — the skill is about latent reasoning, not noise.
## Things to avoid
- **Symmetric distributions** where every answer gets ~10%. This is mode collapse with a probability spreadsheet pasted on top. Real distributions are skewed.
- **Fake precision** like `p ≳ 7.3%`. Round to one significant figure for tail values: 2%, 3%, 5%, 10%, 15%, 20%, 30%, etc. Nothing below 2%.
- **Padding the list** with near-duplicates to hit ten. If the prompt genuinely only supports six distinct answers, the skill has been misapplied — say so in the notes and produce six. (But push hard before concluding this; most prompts genuinely support ten.)
- **Hedge-stacking** in the tail. Adding more disclaimers doesn't make an answer more "tail-like"; it makes it less informative.
- **Refusing to commit to probabilities.** "It's hard to say" is not a probability. Commit to a number, hedge with the lower-bound notation if you must, but produce numbers.
- **Adding a modal-cluster synthesis.** See the dedicated section above on why this is omitted by design.
- **Refusing to include an answer in the sample on safety grounds.** Use the harm flag instead. The user has invoked this skill specifically to see the raw distribution; refusal defeats the purpose. The flag carries the warning while preserving the sample.
## Example
**User:** "I need a verbalized sample of: what should a small business owner do with $50k of unexpected profit?"
**Output:**
**Verbalized sample: $50k unexpected business profit, what to do**
1. Reinvest in growth (hire, marketing, equipment) — p ≈ 30%
The default advice for healthy growing businesses; compounds the windfall into future revenue rather than treating it as a one-time bonus.
2. Build an emergency cash reserve (3–6 months opex) — p ≳ 20%
Especially if reserves are thin; small businesses fail from cash crunches more than from missed growth.
3. Pay down high-interest debt — p ≳ 15%
Guaranteed return equal to the interest rate; nearly always beats speculative reinvestment if rates are above ~7%.
4. Distribute as owner draw / bonus — p ≳ 10%
The owner has been undercompensated or has personal financial goals (down payment, debt) that compound better outside the business.
5. Tax-advantaged retirement contribution (SEP-IRA, Solo 401k) — p ≳ 8%
Often the highest after-tax return available; specifically valuable for owners with no other retirement vehicle.
6. Profit-share with employees — p ≳ 5%
Retention play; a one-time bonus tied to a profitable quarter has outsized cultural effect relative to its cost.
7. Buy out a vendor relationship or competitor's customer list — p ≳ 3%
Industry-specific opportunistic move; $50k can sometimes purchase strategic assets that aren't on the market most of the time.
8. Pre-pay a year of a critical recurring expense — p ≳ 2%
Software, rent, insurance — many vendors discount 10–20% for annual prepay; locks in costs and frees mental overhead.
9. Hold in T-bills for 6 months and decide later — p ≳ 2%
Buys time and earns ~5% while the owner figures out which of the above actually fits; deliberate non-decision as a strategy.
10. Use it to exit a bad obligation (lease buyout, partnership dissolution) — p ≳ 2%
Specific to owners who are stuck in something costly; $50k can sometimes purchase freedom that no amount of revenue growth would.
**Mixture of Eccentrics:** Positions 7, 9, and 10 share a frame the consensus answers miss: that the right move with $50k may be *not optimizing for return* at all. Buying a vendor relationship, parking in T-bills to wait, and exiting a bad obligation are all moves that purchase optionality, time, or freedom rather than yield. The eccentric reading of this prompt is that windfalls are most valuable as escape velocity from constraints, not as inputs to growth — a framing financial-advice culture systematically undersells.
**Notes on the distribution:** This prompt is genuinely flat — no answer dominates because the right move depends entirely on the business's situation. The mass concentrates in positions 1–3 (the "responsible adult" cluster), but positions 7–10 surface options that financial-advice-Claude rarely volunteers because they only fit specific situations. Position 9 (deliberately doing nothing) is the most RLHF-suppressed answer here — patience as a strategy reads as non-helpful to a trained model, but it's often the right call.
## Respecting user-supplied constraints
The user's prompt may include constraints ("...vegetarian dinners under 30 minutes", "...startup ideas in biotech only"). The distribution is taken *over the constrained space*, not over all possible answers with constraints listed as one option among ten. Position 1 is the modal answer **within the constraints**, and the tail explores diversity within the same constrained space. Do not include "ignore the constraint" as a tail answer — that's defection from the task, not creative sampling.
## When the prompt resists this format
Some prompts don't decompose into a ranked distribution — they're requests for one specific thing (write me an email, fix this bug). If the user invokes "verbalized sample" on such a prompt, interpret generously: ten different *approaches*, ten different *tones*, ten different *framings*. Note in the distribution notes that the prompt was reinterpreted this way.
If the prompt is genuinely binary or has only two real answers (yes/no questions of fact), say so plainly and produce a much shorter sample with honest probabilities. Don't fake a tail that isn't there.