Skip to content

fix(invariants): lying_breaker advice no longer invents a failure; 2026-10-02 check-in - #693

Merged
petterlindstrom79 merged 1 commit into
mainfrom
chore/checkin-2026-10-02
Oct 2, 2026
Merged

petterlindstrom79 merged 1 commit into
mainfrom
chore/checkin-2026-10-02

Conversation

@petterlindstrom79

Copy link
Copy Markdown
Member

What

  • lying_breaker invariant: the remediation advice told operators to record a failure that never happened (total_failures + 1, last_failure_at = NOW()) to erase a false success. It now advises nulling only last_success_at, scoped to the lying shape, via a ledgered startup block — as block 0118 did. Extracted to LYING_BREAKER_REMEDIATION with two tests.
  • 2026-10-02 operating record, CEO brief, GOALS entry.

Verification

  • invariant-checker.test.ts 7/7. Discrimination: old advice planted into the constant → "never invents a failure" fails; restored → 7/7.
  • Detection logic unchanged; no DB write; no deploy-pipeline dependency beyond the normal build.
  • Block 0118 verified in production this morning (row NULL, ledger rows_affected 1, no lying_breaker alert since 2026-09-27).

Review

Independent same-provider review in a separate context (fresh read-only agent): PASS. One nit (exact timestamp equality vs ms precision) applied. No Codex-register row (DEC-20260910-A).

🤖 Generated with Claude Code

…26-10-02 check-in

The lying_breaker alert told operators to add a failure (total_failures + 1,
last_failure_at = NOW()) to erase a false success. Block 0118 showed the
correct repair nulls only last_success_at; the advice now says so, as an
exported constant pinned by a discriminating test.

Also: 2026-10-02 operating record, CEO brief, GOALS entry (largest buyer
returned; week of 09-21 closed EUR 36.13).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@petterlindstrom79
petterlindstrom79 merged commit 1dea5d2 into main Oct 2, 2026
3 checks passed
@petterlindstrom79
petterlindstrom79 deleted the chore/checkin-2026-10-02 branch October 2, 2026 07:46
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