docs(6206): retrieval_tuning model docstring drops the decision quote
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 14s
CI & Build / TypeScript typecheck (push) Successful in 53s
CI & Build / integration (push) Successful in 1m8s
CI & Build / Python tests (push) Successful in 1m53s
CI & Build / Build & push image (push) Successful in 21s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-21 20:44:50 -04:00
co-authored by Claude Opus 5.5
parent f6734291c9
commit 40f603ba28
+3 -4
View File
@@ -11,10 +11,9 @@ class RetrievalTuningEvent(Base):
WHY A TABLE AND NOT JUST THE SETTING
The setting holds the number. It cannot hold the argument, and from this
step onward the argument is the interesting part: the operator's decision is
that the model moves these values, *"9 times out of 10"*, without being
asked each time. Delegation like that is only safe if it leaves a trail the
The setting holds the number. It cannot hold the argument, and the argument
is the interesting part: the model moves these values most of the time,
without being asked each time. Delegation like that is only safe if it leaves a trail the
operator can read afterwards — what changed, from what to what, and on what
evidence — and can disagree with.