RAGE #10: expert-plane Tek9/Prolog substrate #25
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!25
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rage/10-expert-runtime-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?
Supersedes draft PR #24 only because the connected ready-for-review mutation is broken (
Repository.fullDatabaseId). #24 had zero reviews and zero conversation comments, so no review history is being discarded.Consumes #10 under parent #8.
Canonical authority:
research/LLM-LOG-RESEARCH-004-symbolic-expert-plane.orgresearch/LLM-LOG-RESEARCH-033-expert-authority-regression-reconciliation.orgresearch/LLM-LOG-RESEARCH-035-draft-pr-recovery.orgArchitecture remains unchanged: Python owns transparent HTTP/SSE/WebSocket capture/transport and expert availability policy; Common Lisp owns the expert runtime, typed objects, Tek9 access, bounded fact materialization, SWI-Prolog supervision/result validation and durable derived assertions; Tek9 is the durable KB; SWI-Prolog owns facts/rules/inference. No Python rule engine.
The exact branch head must be GREEN before merge.
mainis reported unprotected and repository rulesets are empty, so there is no repository-enforced review requirement; zero reviews must not be described as approval.PR #5 remains a separate configuration transaction. Dotfiles PR #172 stays RED-only until this substrate is merged. No Tek9 repository mutation is included.