Bitter Frontier What agents made cheaper, where the bottleneck moved, and what deserves attention.

Publication record

Corrections ledger

Every claim needs a receipt. Every correction does too. This is the public record of what Bitter Frontier got wrong, what changed, and the primary source that settled it.

Entries

Newest first

  1. other-fact internal/adversarial-verify

    like-for-like Microsoft comparison

    finding 2026-07-02-agent-flywheel-arxiv-solo-author-velocity and profile agent-flywheel

    Before
    110 for dicklesworthstone versus 52 for Microsoft, combining counts from different tables
    Corrected
    110 for dicklesworthstone versus 97 for Microsoft in the same top-35 figure

    Verdict: apples-to-oranges comparison -> corrected to counts from the same figure

    Event date
    2026-06-05
    Reported by
    adversarial-verify
    Record
    run 2026-07-12-exemplar-pass-agent-flywheel-frontier-v0

    Open the primary receipt ->

  2. other-fact internal/adversarial-verify

    v0.7.0 safe-mode agent-confirmation boundary

    profile agent-flywheel

    Before
    safe mode keeps standard agent confirmations
    Corrected
    safe mode still installs shared cc, cod, agy, and gmi shortcuts that select dangerous or always-proceed behavior

    Verdict: implementation mismatch -> corrected against tagged shell config

    Event date
    2026-06-26
    Reported by
    adversarial-verify
    Record
    run 2026-07-12-exemplar-pass-agent-flywheel-frontier-v0

    Open the primary receipt ->

  3. other-fact internal/adversarial-verify

    v0.7.0 safe-mode passwordless-sudo behavior

    profile agent-flywheel

    Before
    safe mode omits or removes passwordless sudo
    Corrected
    on a fresh host, safe mode does not create ACFS's own NOPASSWD sudoers file; this branch does not revoke a rule left by an earlier vibe installation or configured elsewhere

    Verdict: overbroad safety claim -> narrowed to the tagged installer's actual branch behavior

    Event date
    2026-06-26
    Reported by
    adversarial-verify
    Record
    run 2026-07-12-exemplar-pass-agent-flywheel-frontier-v0

    Open the primary receipt ->

  4. wrong-date internal/adversarial-verify

    event date and eligibility for the 2026-07-01..2026-07-02 window

    signal 2026-07-02-agent-flywheel-assembly-layer-dangerous-defaults

    Before
    counted as a July 2 signal and described as the live-window case
    Corrected
    withdrawn from the accepted signal count; ACFS v0.7.0 shipped 2026-06-26 and is retained only as a pre-window intake baseline

    Verdict: out-of-window -> withdrawn (source intake is not an upstream product event)

    Event date
    2026-06-26
    Reported by
    adversarial-verify
    Record
    run 2026-07-12-exemplar-pass-agent-flywheel-frontier-v0

    Open the primary receipt ->

  5. other-fact internal/adversarial-verify

    lifecycle status of consumer Gemini CLI

    digest 2026-06-16_2026-06-23-weekly (Gemini Antigravity succession)

    Before
    framed as prospective -- Gemini CLI 'may be entering a managed succession,' with the Antigravity funnel and banner in stable
    Corrected
    the consumer service was already discontinued. Per Google's announcement, Gemini CLI stopped serving requests on 2026-06-18 for AI Pro/Ultra, free individual Code Assist, and new GitHub-org installs; enterprise Code Assist retained access and the OSS repo continues. The 06-16..06-23 window called an executed shutdown prospective.

    Verdict: under-called -> corrected (the shutdown executed inside the 06-16..06-23 window; recorded as accomplished in the 2026-07-01 digest, with Antigravity registered as a separate source)

    Event date
    2026-06-18
    Reported by
    adversarial-verify
    Record
    run 2026-07-01-weekly-digest-2026-06-24_2026-07-01-frontier-v0

    Open the primary receipt ->

  6. other-fact internal/adversarial-verify

    scope of the flash-to-3.5 routing change

    signal 2026-06-10-gemini-flash-ga-routing

    Before
    framed as an unconditional silent switch of flash workloads to gemini-3.5-flash
    Corrected
    gated behind an experiment flag plus auth-type access logic; stable v0.46.0 ships a placeholder flag ID (the real-flag-ID commit is not in v0.46.0)

    Verdict: out-of-window-as-stated -> corrected (the change is real and in-window; the overstatement was scope, not date)

    Event date
    2026-06-10
    Reported by
    adversarial-verify
    Record
    run 2026-06-16-weekly-digest-2026-06-04_2026-06-16-frontier-v0

    Open the primary receipt ->

  7. channel-mismatch internal/adversarial-verify

    channel / scope of "Antigravity migration commands + built-in skill"

    digest 2026-06-04_2026-06-16-weekly (Gemini Antigravity migration)

    Before
    framed as shipping (migration commands and an Antigravity skill present)
    Corrected
    the transition banner is in stable (v0.45.2, uncapped); the migration commands and Antigravity skill are preview-only (v0.47.0-preview.0)

    Verdict: channel-mismatch (resolved by git ancestry: commit in v0.47.0-preview.0 only, not in any stable tag)

    Event date
    2026-06-05
    Reported by
    adversarial-verify
    Record
    run 2026-06-16-weekly-digest-2026-06-04_2026-06-16-frontier-v0

    Open the primary receipt ->

Last updated 2026-07-12. Entries are stored with the publication, not in a separate editorial database.