#13: bounded task graph + usage/cost accounting substrate #35

Merged

lost-rob0t merged 13 commits from rage/13-task-accounting-red into main

2026-08-31 15:32:00 +00:00

lost-rob0t commented

2026-08-31 15:31:35 +00:00

(Migrated from github.com)

Parent: #8
Tracks: #13

Document-first bounded Auto-ARADR/RAGE slice.

Canonical design: research/LLM-LOG-RESEARCH-040-task-graph-usage-cost.org
RED evidence: evidence/LLM-LOG-EVIDENCE-021-task-accounting-red.org
GREEN evidence: evidence/LLM-LOG-EVIDENCE-022-task-accounting-green-attempt.org

Implements the first bounded #13 substrate after an independently executed RED:

Common Lisp owns typed task/usage/pricing/cost materialization and Tek9 writes;
SWI-Prolog owns the declared task_cost inference;
immutable pricing snapshots and provenance-bearing cost assertions;
explicit unknown pricing;
finite payload bounds and request-id deduplication;
exact durable arithmetic with JSON-normalized response representation;
no Python rule engine and no Tek9 repository mutation.

Exact tested head: 982f4dea839f459db04799919a55e0389b1b0ac9
Exact-head workflow: https://github.com/lost-rob0t/llm-log/actions/runs/33408766713 — GREEN across Common Lisp/Tek9/SWI-Prolog, Python expert-policy, and Home Manager.

This does not close the full #13 epic: parent/child recursive rollups, durable restart totals/query surfaces, provider/client/classification/outcome analysis and expensive retry/token-burn queries remain follow-on RED-first slices.

Dotfiles and ~/Documents/AI/proxy are untouched. Provider census #6 remains separate backlog. PR #5 remains a separate transaction.

Parent: #8 Tracks: #13 Document-first bounded Auto-ARADR/RAGE slice. Canonical design: `research/LLM-LOG-RESEARCH-040-task-graph-usage-cost.org` RED evidence: `evidence/LLM-LOG-EVIDENCE-021-task-accounting-red.org` GREEN evidence: `evidence/LLM-LOG-EVIDENCE-022-task-accounting-green-attempt.org` Implements the first bounded #13 substrate after an independently executed RED: - Common Lisp owns typed task/usage/pricing/cost materialization and Tek9 writes; - SWI-Prolog owns the declared `task_cost` inference; - immutable pricing snapshots and provenance-bearing cost assertions; - explicit unknown pricing; - finite payload bounds and request-id deduplication; - exact durable arithmetic with JSON-normalized response representation; - no Python rule engine and no Tek9 repository mutation. Exact tested head: `982f4dea839f459db04799919a55e0389b1b0ac9` Exact-head workflow: https://github.com/lost-rob0t/llm-log/actions/runs/33408766713 — GREEN across Common Lisp/Tek9/SWI-Prolog, Python expert-policy, and Home Manager. This does not close the full #13 epic: parent/child recursive rollups, durable restart totals/query surfaces, provider/client/classification/outcome analysis and expensive retry/token-burn queries remain follow-on RED-first slices. Dotfiles and `~/Documents/AI/proxy` are untouched. Provider census #6 remains separate backlog. PR #5 remains a separate transaction.