eric/notarius
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document the PromptKit integration

Browse Source
This commit is contained in:
Eric Rakestraw
2026-07-28 16:52:49 +00:00
parent 4bca6d3103
commit f1a6574013
9 changed files with 121 additions and 181 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/roadmap/future.md
View File

@@ -95,9 +95,9 @@ safety checks, and deterministic application of accepted changes.
### Native Session Propagation
- Once upstream Scriptorium exposes a session identifier on its run request,
- Once upstream PromptKit exposes a direct request-level session identifier,
propagate the existing `StructuredCompletionRequest.SessionID` through the
Scriptorium adapter's native session field.
PromptKit adapter's native session field.
- Preserve the current `--session-id` invocation contract and its run-wide
propagation to every prompt-facing module and validator. Do not introduce a
second session configuration surface.
@@ -110,10 +110,11 @@ safety checks, and deterministic application of accepted changes.
concurrent-run isolation, and unsupported-provider behavior once the
upstream contract is available.
This work is blocked on native session support in the upstream Scriptorium
package. Notarius already carries a run-scoped session ID through its CLI,
pipeline requests, checkpoint identity, and prompt variables; the missing
capability is native propagation across the LLM adapter boundary.
This work is blocked because PromptKit v0.1.0 does not expose the required
direct request-level session field. Notarius already carries a run-scoped
session ID through its CLI, pipeline requests, checkpoint identity, and a
`session_id` prompt variable; that prompt-variable propagation is not native
provider session support.
## Further Reference Evolution

6
docs/roadmap/implementation.md
View File

@@ -3,9 +3,9 @@
## Status
In progress. The dependency, framework adapter, version 4 PromptKit
configuration migration, provider-neutral module prompt-asset support, and
provenance alignment are implemented; canonical documentation and final
repository verification are still planned.
configuration migration, provider-neutral module prompt-asset support,
provenance alignment, and canonical documentation are implemented; final
repository verification is still planned.
## Objective