#15: bounded outcome dataset provider/model filters #52
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/llm-log!52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rage/15-outcome-dataset-metadata-red"
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?
Closes the next bounded #15 corpus-selection slice without changing outcome authority semantics.
Canonical design:
research/LLM-LOG-RESEARCH-050-outcome-dataset-request-metadata.orgRED evidence:
evidence/LLM-LOG-EVIDENCE-042-outcome-dataset-request-metadata-red.orgGREEN evidence:
evidence/LLM-LOG-EVIDENCE-043-outcome-dataset-request-metadata-green.orgAdds a llm-log-owned, versioned Tek9
usage-request-idsecondary index and bounded provider/model filtering/projection toquery_outcome_dataset. Existing corpora get a one-time guarded index rebuild. No Tek9 repo mutation, no Python rules, and no Prolog inference changes.Exact evidence-only head
558d714bdbf419d41c786fcb54cc78ddf0d13775passed workflow 33465664814 across Common Lisp/Tek9/SWI-Prolog, Python expert policy/transport, and Home Manager.Issue #15 remains open after this PR for later bounded dataset/corpus work.