#15: bounded outcome dataset export RED #48
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!48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rage/15-outcome-dataset-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?
Consumes #15 after the GREEN outcome evidence + supersession/history substrate.
Canonical design:
research/LLM-LOG-RESEARCH-047-outcome-dataset-export.org.This PR is RED-first only at creation: it adds the bounded
query_outcome_datasetcontract and wires it into the existing Common Lisp/Tek9/SWI-Prolog integration suite. No production expert behavior has been changed yet.Expected untouched-baseline failure:
query_outcome_datasetis not declared and the bounded outcome corpus index/export projection do not exist.Architecture remains: Python capture/transport; Common Lisp typed runtime/Tek9 access; Tek9 durable KB; SWI-Prolog owns inference. Export reads stored immutable outcome assertions; it never re-labels data.
WIP: #15: bounded outcome dataset export REDto #15: bounded outcome dataset export REDPull request closed