i am a retarded llm and wrote this in the wrong language #20

New issue

Closed

opened 2026-08-29 19:20:30 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-29 19:20:30 +00:00

(Migrated from github.com)

Superseded architecture experiment

This issue proposed deleting Python and moving transparent HTTP/SSE/WebSocket proxying into Common Lisp.

That direction is superseded by the current explicit architecture and the canonical reconciliation in research/LLM-LOG-RESEARCH-033-expert-authority-regression-reconciliation.org.

Current ownership:

Python llm-log: transparent capture/transport, provider/upstream compatibility, HTTP/SSE/WebSocket forwarding, raw immutable capture/redaction, expert availability policy.
Common Lisp expert service: runtime lifecycle, Tek9 access, typed objects, bounded fact materialization, SWI-Prolog supervision, result validation, durable derived assertions.
Tek9: canonical durable document/graph KB.
SWI-Prolog: facts, rules and inference.

No second Python rule engine is allowed. Existing zero-Python research remains historical context only and does not authorize deleting the accepted Python transport implementation.

Active implementation: #10 / PR #24.

## Superseded architecture experiment This issue proposed deleting Python and moving transparent HTTP/SSE/WebSocket proxying into Common Lisp. That direction is **superseded** by the current explicit architecture and the canonical reconciliation in `research/LLM-LOG-RESEARCH-033-expert-authority-regression-reconciliation.org`. Current ownership: - **Python llm-log:** transparent capture/transport, provider/upstream compatibility, HTTP/SSE/WebSocket forwarding, raw immutable capture/redaction, expert availability policy. - **Common Lisp expert service:** runtime lifecycle, Tek9 access, typed objects, bounded fact materialization, SWI-Prolog supervision, result validation, durable derived assertions. - **Tek9:** canonical durable document/graph KB. - **SWI-Prolog:** facts, rules and inference. No second Python rule engine is allowed. Existing zero-Python research remains historical context only and does not authorize deleting the accepted Python transport implementation. Active implementation: #10 / PR #24.