Build the held-out set and the fixed replay score for os-me #940
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#940
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The os-me skill cannot improve without a way to measure how well it predicts Jared's responses.
Question
How does a fixed script, outside the Store, score a Prediction against Jared's real reply?
Context
Map: #936
Build in
plugins/os-me/(Shell):~/.claude/projects/*/transcripts: an assistant output, then a typed reply from Jared that accepts, corrects, or redirects. Skip sessions with no reply from Jared.docs/eval-discipline.md. Read~/Documents/SecondBrain/howto/running-autoresearch-skill-evals.mdbefore you design the judge.AFK.
Start: building the fixed eval (bin/os-me-eval, lib, test, eval) on branch os-me.
Resolution
Done: bin/os-me-eval built: deterministic 15 percent held-out split by SHA-256 of the session id, exchange finder, context renderer, headless predictor and judge with JSON verdicts, score log. Review bug fixed: predictor reads are limited to the Store and the context directory.
Evidence: main
5e3ffbc5; 32 runs 76 assertions 0 failures; rubocop clean; cc-os counts: 159 train sessions, 23 held-out sessions, 74 held-out exchanges; a real call proved a transcript read is denied.Follow-ups: none; the score-measure question for Jared is listed on #942