RAGE #10: restore expert-plane boundary + Tek9/Prolog substrate #24

Closed

lost-rob0t wants to merge 0 commits from rage/10-expert-runtime-red into main

lost-rob0t commented

2026-08-30 09:19:12 +00:00

(Migrated from github.com)

Scope

Consumes #10 only.

Accepted architecture:

Python remains transparent HTTP/SSE/WebSocket capture/transport.
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 canonical durable expert KB.
SWI-Prolog owns declared facts/rules/inference.
No second Python rule engine and no Common Lisp transport rewrite.

Canonical authority:

research/LLM-LOG-RESEARCH-004-symbolic-expert-plane.org
research/LLM-LOG-RESEARCH-033-expert-authority-regression-reconciliation.org
research/LLM-LOG-RESEARCH-034-pr24-review-gate-resolution.org

Executed expert evidence

Tek9 + SWI substrate: RED e763c740... / GREEN 42657f7...
derived assertions: RED e4c61b7... / GREEN b7a9bc7...
reasoner failure/recovery: RED cc0df4b... / GREEN 89173d6...
Python expert availability policy: RED 30b33cf... / GREEN c1a455b...
concrete Python -> Common Lisp adapter: hosted RED adabdf5...; production e87d51d...
HTTP/WebSocket lifecycle: RED 15f3056... / GREEN b213923...
normal CLI expert launch: RED baf99df... / GREEN 76e2252...
Home Manager/systemd expert wiring: RED 7230b5c... / GREEN b6111a5...

Consumer gate

dotfiles PR #172 remains test-only RED at 0a23f6a80c9219f8ac5082f93cf90762053614ac.
~/Documents/AI/proxy remains the capture path.
no production dotfiles pin/config mutation until an eligible upstream revision exists.

Exact-head status

Current head: 8f0a0e89631ce0887affceb48db63f5568cf5f78 (docs: resolve #10 review gate evidence).

Workflow run 33356338741 executed this exact SHA and completed GREEN on 2026-08-31. This is the current exact-head CI evidence; it is not inherited from an older implementation SHA.

Previous exact head 448be1744b06d13ec59f5287fa41e3185ffb519a is independently GREEN in run 33353087562.

Review/tooling status

PR #24 remains draft with zero submitted reviews, zero PR conversation comments, and no requested reviewers.

Fresh governance research found:

repository rulesets endpoint is empty;
classic main branch-protection state is unreadable to the installed integration (403 Resource not accessible by integration), so empty rulesets are not proof that no classic review requirement exists;
ready-for-review mutation was retried after exact-head GREEN and still fails because the connector requests nonexistent Repository.fullDatabaseId;
same-author bookkeeping is not independent review evidence.

Do not infer not required from not observable.

Isolation

PR #5 remains a separate configuration transaction.
no Tek9 repository mutation is justified by the current public API boundary; fresh remote inspection still shows zero open Tek9 issues and zero open Tek9 PRs.
provider census #6 remains backlog.
#12/#13/#15/#17 remain blocked behind #10.

Merge status

Exact-current-head GREEN and mergeability are satisfied. Remain unmerged until the PR is non-draft and required review/discussion state is positively satisfied.

Next #10 boundary

Once an eligible upstream revision exists, advance dotfiles PR #172 from its already-executed RED to GREEN by updating the pin and enabling services.llm-log.expert with initial require = false, while preserving ~/Documents/AI/proxy, existing provider/client routing, and separate expert mutable state.

## Scope Consumes #10 only. Accepted architecture: - Python remains transparent HTTP/SSE/WebSocket capture/transport. - 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 canonical durable expert KB. - SWI-Prolog owns declared facts/rules/inference. - No second Python rule engine and no Common Lisp transport rewrite. Canonical authority: - `research/LLM-LOG-RESEARCH-004-symbolic-expert-plane.org` - `research/LLM-LOG-RESEARCH-033-expert-authority-regression-reconciliation.org` - `research/LLM-LOG-RESEARCH-034-pr24-review-gate-resolution.org` ## Executed expert evidence - Tek9 + SWI substrate: RED `e763c740...` / GREEN `42657f7...` - derived assertions: RED `e4c61b7...` / GREEN `b7a9bc7...` - reasoner failure/recovery: RED `cc0df4b...` / GREEN `89173d6...` - Python expert availability policy: RED `30b33cf...` / GREEN `c1a455b...` - concrete Python -> Common Lisp adapter: hosted RED `adabdf5...`; production `e87d51d...` - HTTP/WebSocket lifecycle: RED `15f3056...` / GREEN `b213923...` - normal CLI expert launch: RED `baf99df...` / GREEN `76e2252...` - Home Manager/systemd expert wiring: RED `7230b5c...` / GREEN `b6111a5...` ## Consumer gate - dotfiles PR #172 remains test-only RED at `0a23f6a80c9219f8ac5082f93cf90762053614ac`. - `~/Documents/AI/proxy` remains the capture path. - no production dotfiles pin/config mutation until an eligible upstream revision exists. ## Exact-head status Current head: `8f0a0e89631ce0887affceb48db63f5568cf5f78` (`docs: resolve #10 review gate evidence`). Workflow run `33356338741` executed this exact SHA and completed **GREEN** on 2026-08-31. This is the current exact-head CI evidence; it is not inherited from an older implementation SHA. Previous exact head `448be1744b06d13ec59f5287fa41e3185ffb519a` is independently GREEN in run `33353087562`. ## Review/tooling status PR #24 remains draft with zero submitted reviews, zero PR conversation comments, and no requested reviewers. Fresh governance research found: - repository rulesets endpoint is empty; - classic `main` branch-protection state is unreadable to the installed integration (`403 Resource not accessible by integration`), so empty rulesets are not proof that no classic review requirement exists; - ready-for-review mutation was retried after exact-head GREEN and still fails because the connector requests nonexistent `Repository.fullDatabaseId`; - same-author bookkeeping is not independent review evidence. Do not infer `not required` from `not observable`. ## Isolation - PR #5 remains a separate configuration transaction. - no Tek9 repository mutation is justified by the current public API boundary; fresh remote inspection still shows zero open Tek9 issues and zero open Tek9 PRs. - provider census #6 remains backlog. - #12/#13/#15/#17 remain blocked behind #10. ## Merge status Exact-current-head GREEN and mergeability are satisfied. Remain unmerged until the PR is non-draft and required review/discussion state is positively satisfied. ## Next #10 boundary Once an eligible upstream revision exists, advance dotfiles PR #172 from its already-executed RED to GREEN by updating the pin and enabling `services.llm-log.expert` with initial `require = false`, while preserving `~/Documents/AI/proxy`, existing provider/client routing, and separate expert mutable state.

nsaspy changed title from ~~WIP: RAGE #10: restore expert-plane boundary + Tek9/Prolog substrate~~ to RAGE #10: restore expert-plane boundary + Tek9/Prolog substrate

2026-09-04 14:35:41 +00:00

nsaspy referenced this pull request

2026-09-04 14:35:41 +00:00

RAGE #10: expert-plane Tek9/Prolog substrate #25