aboutsummaryrefslogtreecommitdiff
path: root/working/triage-telegram-down-launch
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-27 13:46:32 -0500
committerCraig Jennings <c@cjennings.net>2026-07-27 13:46:32 -0500
commitd74d98d03e7321b6c69dae9ef427da66b0f6fbc6 (patch)
tree4d61b604085afc019b40903a9e8db9072b46147c /working/triage-telegram-down-launch
parent2c664cb5651fbf03bc52d7848add0c571708adcd (diff)
downloadrulesets-d74d98d03e7321b6c69dae9ef427da66b0f6fbc6.tar.gz
rulesets-d74d98d03e7321b6c69dae9ef427da66b0f6fbc6.zip
docs: correct the rightsizing docs against live measurements
I had the goal backwards in the lead. Craig's framing is output quality first, with token reduction real but second, and where they conflict quality wins. Anthropic's 80% was a finding rather than a target, and aiming at it directly optimizes the thing we don't care about. P4 falls to that and is dropped: lowering effort buys tokens by spending quality. P5 rises for the same reason, since positive framing over prohibition is what actually targets guardrails working against output. My token figures were low by about 45%. I converted word counts at a guessed ratio when /context reports real per-file numbers, so I used an estimate because it was easier to compute from inside the repo. The live ratio is 2.28 tokens per word. commits.md is 12,800 tokens rather than the 7,000 I estimated, and claude-rules was near 57,800 per session before today. I also conflated two loading paths. Memory files come in through the harness at session start. protocols.org and the workflows are read by startup and land in Messages, so they never appear under Memory files at all. They shrink by editing the workflow, not by scoping a rule, and treating them as one surface made protocols.org look like it competed with commits.md for the same fix. Path-scoping is confirmed working at user level, and the de-duplication holds. That splits the remaining work: anything scopable to a file type or directory ships with no trial, because a glob match is deterministic. Only the semantic rules need the skills route and the stop conditions, and commits.md is the one that matters there at 12,800 tokens of publish machinery that only applies when a commit is in play. I recorded one caution the confirmation doesn't cover. Path-scoping fires when a matching file is read, so creating a new org file from scratch never triggers todo-format.md. Edits are safe because Edit requires a prior read. I also wrote up the day's two guard failures, both mine. wrap-org-table reflowed a table into a worse shape and lint-org certified it clean, and the teardown hook consumed a stale sentinel and killed a live work session. The plan leans on mechanical detectors because they have no stake, which is still right, but a detector can be confidently wrong and a green check from a guard that never looked is indistinguishable from one that did.
Diffstat (limited to 'working/triage-telegram-down-launch')
0 files changed, 0 insertions, 0 deletions