#15: bounded outcome dataset export RED #48

Closed
lost-rob0t wants to merge 0 commits from rage/15-outcome-dataset-red into main
lost-rob0t commented 2026-09-01 00:12:48 +00:00 (Migrated from github.com)

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_dataset contract 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_dataset is 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.

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_dataset` contract 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_dataset` is 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.
nsaspy changed title from WIP: #15: bounded outcome dataset export RED to #15: bounded outcome dataset export RED 2026-09-04 14:35:45 +00:00

Pull request closed

Sign in to join this conversation.
No description provided.