Propagate permanent RLM context to internal model calls #201
No reviewers
Labels
No labels
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/prolog-rlm!201
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rage/200-permanent-rlm-context"
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?
Closes #200.
RAGE state
TDD-first. The branch starts from
2ceba4c0f4a64e95233849a92def6e4fbf95b8b7and the first commit adds the deterministic provider-context regression contract only. Production implementation follows after the red contract is observed.Approved design authority: #183. Related provider-surface gate: #176.
Invariant
The root planner's already-compiled permanent RLM operating context must be inherited by provider calls made by model-selected internal/nested/retry plan steps, exactly once per request. This is provider visibility only and must not widen capabilities, authority, handlers, or effects.
Raw standalone
llm_query/3remains raw.Keep draft until exact-head deterministic, Nix/clean-pack, Tree-sitter, and configured Paid OpenRouter gates are green and the final head is reviewed against #183.
Exact-head verification on
8f7add3fcefc21520e760acefe90b29cdffad4a7is green across every repository gate: CI (deterministic unit/load checks + credentialed REAL OpenRouter), Paid OpenRouter, Nix flake/package/out-of-checkout load, Tree-sitter FFI, and Clean SWI pack install. Review submissions: none. Unresolved review threads: none.mainremains the original base2ceba4c0f4a64e95233849a92def6e4fbf95b8b7; PR is mergeable. Final audit remains within #183:rlm_completioncompiles the permanent skill projection once; root planner uses the ordinary provider; plan execution receives only a host-ownedprovider_context(SkillMessages, Provider)wrapper;rlm_planis unchanged; rawllm_query/3is unchanged; visibility grants no capability/authority/effect. The automation attempted to transition this PR out of draft, but the connected GitHub mutation was blocked by the tool safety layer, so merge could not proceed even though all repository gates are satisfied.