From ce0bf8dafde0c9496c9221c397ecfa16dd84c482 Mon Sep 17 00:00:00 2001 From: Austin Schaefer Date: Wed, 19 Aug 2026 13:08:32 +0200 Subject: [PATCH] fix: restore doubleo7 rebrand in case-study intro The "Update rig to 0.42" commit (cd580f3) accidentally reverted this paragraph's `doubleo7` branding back to the old `deep_research` name and degraded the prose along with it -- unrelated to the rig version bump. Restore the rebranded wording from 5bb4ed1. --- docs/case-study.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/case-study.md b/docs/case-study.md index 99d3c6d..4b57357 100644 --- a/docs/case-study.md +++ b/docs/case-study.md @@ -1,9 +1,10 @@ # Case study: hardening an agentic pipeline against real failure -This is a walkthrough of how `deep_research`'s multi-agent pipeline went -from "works in the happy path" to an improved resiliency — driven by two real failures -it hit in normal use. The throughline: root-cause failure debugging via manual testing and -post-fix verification. +This is a walkthrough of how `doubleo7`'s multi-agent pipeline went +from "works in the happy path" to actually resilient — driven by two real +failures it hit in normal use, not by imagining edge cases in the abstract. +The throughline: root-cause failures instead of papering over them, and +verify fixes against a live run, not just a green test suite. ## The starting point