os-me: bin/os-me-record appends and scores prediction records #1074
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#1074
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 LLM hand-writes the rows of review-log.md. Only 18% of the 131 rows name a trigger id. The stated Confidence percent is never stored. Hit rate per trigger, calibration, and trust by origin cannot be computed.
Design
/home/jared/dev/cc-os/docs/takedown/1074-20261017-082123/final-design.json
Approach
PredictionLog owns JSONL per-ruling records (append, session-keyed lookup, atomic depth rewrite), fed by PredictionParser and ReplyDepth, exposed as Thor commands append and score-record in OsMe::CLI; the one non-red test now asserts the specific error message.
Required work:
plugins/os-me/lib/os_me/reply_depth.rbplugins/os-me/lib/os_me/cli.rbplugins/os-me/lib/os_me/prediction_parser.rbplugins/os-me/lib/os_me/prediction_log.rbplugins/os-me/test/prediction_parser_test.rbplugins/os-me/test/prediction_cli_test.rbAcceptance criteria
Owner sketch
append,score-record)plugins/os-me/test/prediction_parser_test.rbplugins/os-me/test/prediction_cli_test.rbjared referenced this issue2026-10-17 11:54:35 +00:00
Work started on branch ticket-1074 via /os-sdlc:implement with map takedown-implement; design from docs/takedown/1074-20261017-082123.
Resolution
Done: OsMe::PredictionParser parses the last assistant message into one record per lettered ruling (id, session_id, text, confidence, depth); OsMe::PredictionLog appends JSONL records and rewrites depth atomically; OsMe::ReplyDepth classifies the next user reply; CLI gains append and score-record; UnknownId and AmbiguousId errors fail loudly.
Evidence: Implementation 53 on map takedown-implement, 8 dispatches, 1 retry, all gates green; commit
d720c79aon branch ticket-1074 (merged to main by worktree finish); design docs/takedown/1074-20261017-082123; tests plugins/os-me/test/prediction_parser_test.rb and prediction_cli_test.rb red at base then green.Follow-ups: #1081 captured: records must also carry triggers, verdict, origin, and autopilot (named by the takedown grade as remaining; blocks #1075 and #1077). Lens line from dispatch 463 under challenge; a Lens proposal ticket follows if justified.