Files
scriptorium/docs/roadmap/step6.md

2.8 KiB

Migration Step 6: Extract And Stabilize Promptkit

Status

Complete as of 2026-07-28.

Result

Promptkit is now the independently published owner of Scriptorium's reusable prompt-execution framework. The extraction used Scriptorium commit c7263ab2a8e58f7fb97280082d327a820c7cece7 as its source snapshot and was accepted at Promptkit commit 9e68a2bbf779545995270c47842048a3bc6c85dc.

The accepted commit is published as the annotated Go module tag v0.1.0. Promptkit now provides:

  • the supported root Go facade and public error contract;
  • internal prompt, profile, artifact, rendering, validation, model-client, and orchestration packages;
  • the 24 characterized built-in execution profiles;
  • deterministic offline contract and package tests;
  • current consumer, framework-format, integration, internal, development, testing, and release documentation; and
  • a maintained offline Go preparation example.

Promptkit remains an importable library. It does not provide a command, inbound HTTP service, application configuration, deployment policy, hosted CI, or binary release.

Acceptance And Publication

The exact Promptkit release commit passed ordinary and race-enabled tests, vet, build, formatting, repository hygiene, link validation, architecture checks, public-inventory comparison, asset comparison, and its maintained example from a fresh checkout with GOWORK=off.

The remote annotated tag object resolves to the accepted commit. A separate temporary Go module then resolved gitea.maximumdirect.net/eric/promptkit@v0.1.0 from the configured remote, selected exactly v0.1.0, and built and ran a root-package consumer without a workspace or replacement.

Scriptorium also passed its complete pre-cutover test, vet, and executable build checks before publication.

Retained Application Boundary

Scriptorium intentionally remains at the pre-cutover boundary after this step. Its CLI, HTTP adapters, application configuration, transport policy, restricted HTTP artifact reader, current public facade, and framework copy remain unchanged so the application is independently buildable.

No Scriptorium production import, dependency, consumer document, or executable example adopts Promptkit in this completion record.

Next Gate

Migration Step 7 is authorized to adopt the published v0.1.0 module, wire Scriptorium through Promptkit's supported root API, and remove the duplicated Scriptorium framework. That work must retain the application-owned CLI, HTTP, configuration, and deployment boundaries and pass the Step 7 gate before any later consumer migration begins.

The implementation completion record records the executed validation and release evidence. The main migration roadmap owns the remaining sequence.