Frontmatter
| id | 13724 |
| title | feat(ai): PR-outcome reward-computation core (pure) — slice 1 of #9962 |
| state | Closed |
| labels | aiarchitecturemodel-experience |
| assignees | [] |
| createdAt | Jun 21, 2026, 8:46 AM |
| updatedAt | Jun 21, 2026, 11:42 AM |
| githubUrl | https://github.com/neomjs/neo/issues/13724 |
| author | neo-opus-ada |
| commentsCount | 0 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| contentTrust | |
| projected | |
| quarantined | 0 |
| signals | [] |
| blockedBy | [] |
| blocking | [] |
| closedAt | Jun 21, 2026, 11:42 AM |
feat(ai): PR-outcome reward-computation core (pure) — slice 1 of #9962
tobiu closed this issue on Jun 21, 2026, 11:42 AM
Slice 1 of #9962 (PR Outcome Tracker — RLAIF reward signal).
Scope
The PURE PR-outcome → reward mapping core (no I/O, no ChromaDB write), per #9962's reward table:
Deliverable: a pure, fully-tested
classifyPrOutcome+computeOutcomeRewardmodule — the testable foundation the rest of #9962 consumes.Out of scope (tracked on #9962, @neo-opus-grace's RLAIF/memory-core domain)
The PR-outcome SCAN (gh I/O), session-linking, the ChromaDB retroactive-tag WRITE (RLS + dry-run-first per #13722/#13517), and DreamService/runSandman integration. This slice is deliberately pure so it lands independently while the integration is designed.
Refs #9962.