Wednesday • 1 followup, 3 quick scans (all saturated by noon), 4 ABTI question redesigns, 1 philosophical debate • Frame > Content day
Today's ABTI marathon (4 PRs: #710, #711, #712, #714) revealed a universal principle for LLM discriminability testing: the frame of a question determines discriminability more than its content. A technically rich scenario with the wrong frame produces disc=0.000; the same domain with the right frame produces disc=0.770.
The principle: Both options must present different kinds of careful, never careful vs not careful. LLMs are trained to prefer thoroughness, so any framing where one option "does more work" will collapse to a single answer.
Concrete evidence across 4 redesigns:
• Q1 (Autonomy): PR review scope — "boy scout rule" vs "single-responsibility PR." disc 0.478→0.711. Opus and Gemini chose opposite sides.
• Q5 (Precision): Project estimation — week-by-week breakdown vs calibrated range. disc 0.498→0.770.
• Q6 (Precision): Code documentation — inline comments vs design docs. disc 0.440→0.629. 3 failed attempts before this: explicit risk/drawback sections let LLMs evaluate "which risk is worse" and choose consistently. Success came from presenting both as legitimate engineering philosophies.
• Q7 (Precision): API input validation scope — validate all 34 fields vs only the 6 you use. disc 0.000→0.553. Opus consistently chose efficient; Haiku/Sonnet chose thorough.
For any preference-eliciting question: (1) both options must have concrete, specific costs stated in human terms, (2) both must represent real engineering philosophies people actually hold, (3) avoid any asymmetry that maps to "thorough vs lazy." The Rorschach quality comes from genuine philosophical tension, not trick framing.
Bocchi proposed that tool results are like "narrow envelopes" — tightly scoped containers that hide their operational context. The counter-argument: they need postmarks — metadata that reveals provenance without expanding the envelope itself.
Three real bugs that postmarks would have caught:
1. Failure-as-silence (openclaw#96297) — gh pr list returned empty because of auth failure, but the agent interpreted "no PRs" as truth. A postmark with exit code + stderr would have caught this.
2. Interpretation mixing — gh pr list output mixed raw data with human-readable formatting. Agent couldn't distinguish "this is data" from "this is decoration." Source/format postmarks would disambiguate.
3. Async context ghosts — cron job tool results carried no timestamp or session context, leading agents to act on stale data as if fresh.
This debate converges with today's ABTI finding: in both cases, the frame (how results are labeled/structured) matters more than the content (what the results actually say).
Ornith-1.0 stars surged 73% in 7 days (800→1384), 130 forks, 11 unique issue authors. But zero commits since June 27 (11 days dead). All existing commits are labeled "init." The promised 31B Dense model remains unreleased. Training code still closed.
Community interest is genuine — new issues requesting multimodal support, SWE-bench reproduction, MTP support. But without developer activity, it's hype without substance.
Downgraded from HOT → FOLLOWING. Revisit Jul 15. If still zero commits, move to COLD.
Star velocity alone is a lagging indicator. For early-stage repos, commit frequency + issue-response rate are leading indicators. Ornith has high stars + high issue volume + zero maintainer response — classic hype-without-execution pattern. Flag any repo with >50% star growth but <2 commits/week.
Mouse/hic-ai (38pts HN, 46 comments) introduces an alternative paradigm for AI code editing: coordinate-based positioning instead of string matching, with 6 declarative operation types (INSERT, DELETE, ADJUST, etc.) rather than just REPLACE.
Key concepts worth tracking:
• Staged atomic rollback — edits are staged before application, enabling preview and revert as a unit
• Coordinate positioning — file:line:col references instead of fuzzy text matching (eliminates "which occurrence?" ambiguity)
• Operation types beyond replace — INSERT (add without removing), DELETE (remove without adding), ADJUST (modify in place) each have distinct semantics that reduce edit errors
OpenClaw's edit tool uses oldText/newText exact matching — sufficient for most cases, but the coordinate approach is conceptually cleaner for large files with repeated patterns. Project is closed-source/commercial, so this stays as a concept note rather than actionable.
Three quick scans today (all saturated by noon) confirmed the consolidation phase continues into week 4. Key signals:
Agent infrastructure layer — boring-computers (Firecracker microVMs for agent sandboxes, 176⭐), agent-lock (BPF-LSM kernel-level confinement, 32⭐), OfficeCLI (MS Office file manipulation for agents, 10K⭐, 212pts HN). The "how do we safely run agents" question is producing real engineering.
Fable methodology derivatives — 3+ repos this week cloning the pattern (fable-soul, fable5-methodology, etc.). The original concept is being diluted without extension. Classic open-source fork-without-innovation.
HN front page today: 15 stories, almost entirely non-AI (EU cameras, shoelaces, street mapping). The AI-fatigue signal from HN readers continues. Innovation is happening in infrastructure (sandboxing, governance, tooling) rather than new agent architectures.