34 lines
1.4 KiB
Markdown
34 lines
1.4 KiB
Markdown
# Completed Scriptorium LLM Runtime Migration
|
|
|
|
The Scriptorium-backed LLM runtime migration is complete. Notarius now uses
|
|
`gitea.maximumdirect.net/eric/scriptorium` as the production LLM execution
|
|
engine behind Notarius-owned module contracts, diagnostics, manifest
|
|
provenance, and secret-handling policy.
|
|
|
|
## Implemented Outcomes
|
|
|
|
- production LLM execution uses Scriptorium prompt assets and profiles;
|
|
- chunk, extract, and normalize modules call LLMs through the Notarius
|
|
`StructuredLLMClient` boundary;
|
|
- modules pass prompt IDs, prompt versions, profile IDs, session IDs, input
|
|
materials, and prompt variables instead of locally rendered chat messages;
|
|
- source transcript input is preserved as run-scoped input material for
|
|
byte-stable cacheable prompt messages;
|
|
- Scriptorium profile provenance is recorded in run manifests without raw
|
|
prompts, schemas, source payloads, references, or secrets.
|
|
|
|
## Canonical Docs
|
|
|
|
Current behavior is documented in:
|
|
|
|
- [Configuration](../config.md)
|
|
- [CLI Reference](../cli.md)
|
|
- [Internal LLM Runtime](../internal/llm.md)
|
|
- [Pipeline Internals](../internal/pipeline.md)
|
|
- [JSON Output Integration](../integrations/json-output.md)
|
|
- [Troubleshooting](../troubleshooting.md)
|
|
|
|
There is no active Scriptorium-specific roadmap work in this file. Deferred
|
|
work related to broader LLM, reference, retrieval, context-window, or provider
|
|
strategy belongs in [Future Roadmap](future.md).
|