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

Complete policy alignment documentation handoff

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-28 01:47:05 +00:00
parent 417522f08c
commit df762c3735
5 changed files with 23 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/roadmap/configkit.md
View File

@@ -3,9 +3,10 @@
## Status And Intent ## Status And Intent
Implemented feature direction, drafted on 2026-09-26 and delivered through the Implemented feature direction, drafted on 2026-09-26 and delivered through the
[implementation plan](implementation.md). This roadmap records the target historical plan at
behavior and changes from the reviewed baseline; the implementation plan owns `git show 8452b54809b99425a97940da485daaa48c77aeb8:docs/roadmap/implementation.md`.
sequencing, concrete interfaces, and verification evidence. This roadmap records the target behavior and changes from the reviewed baseline;
that Git record owns sequencing, concrete interfaces, and verification evidence.
The user is adopting ConfigKit across an application suite to standardize The user is adopting ConfigKit across an application suite to standardize
configuration semantics. Scriptorium will make a clean cutover to ConfigKit's configuration semantics. Scriptorium will make a clean cutover to ConfigKit's

8
docs/roadmap/implementation.md
View File

@@ -248,7 +248,13 @@ identify their own file at the selected full commit.
## Stage 5: Verify Language Parity And Complete The Documentation Handoff ## Stage 5: Verify Language Parity And Complete The Documentation Handoff
**Status: Pending.** **Status: Complete.** All seven policies were compared directly with the pinned
upstream files; differences are limited to metadata, removed template text,
the selected project example and topic rows, and the identified local sections.
The copied license matches byte-for-byte. A Markdown-aware check resolved 86
local links; historical plan references resolve to Git objects. Attribution,
notice scope, release navigation, and the final documentation-only diff were
reviewed without changing application or publication artifacts.
Files: this plan, the feature roadmap, and only affected documentation needing Files: this plan, the feature roadmap, and only affected documentation needing
correction within the preceding stages' scope. correction within the preceding stages' scope.

7
docs/roadmap/policy.md
View File

@@ -2,12 +2,17 @@
## Status And Intent ## Status And Intent
Agreed on 2026-09-28; implementation is pending. This roadmap replaces the Agreed and delivered on 2026-09-28. This roadmap replaces the
earlier licensing-only proposal with alignment of the complete applicable earlier licensing-only proposal with alignment of the complete applicable
policy set and its supporting documentation. It defines the targeted end state policy set and its supporting documentation. It defines the targeted end state
and required changes; the [implementation plan](implementation.md) owns ordered and required changes; the [implementation plan](implementation.md) owns ordered
stages and their verification. stages and their verification.
The next release summary should mention the policy and licensing alignment,
the already-selected GPL-3.0-or-later application grant, and the separate
CC-BY-SA-4.0 treatment of adapted policy material. Version selection and
publication remain release preparation, not part of this delivery.
The goal is identical policy language across adopting projects except where a The goal is identical policy language across adopting projects except where a
substantive, locally significant requirement or decision warrants customization. substantive, locally significant requirement or decision warrants customization.
Adopt upstream wording verbatim for non-substantive differences. Existing local Adopt upstream wording verbatim for non-substantive differences. Existing local

5
docs/roadmap/promptkit-v0.9.0-adoption.md
View File

@@ -3,8 +3,9 @@
## Status ## Status
Complete. This document records the delivered feature scope and targeted end Complete. This document records the delivered feature scope and targeted end
state. The completed delivery plan is maintained in state. The completed delivery plan is preserved at
[implementation.md](implementation.md); current behavior remains defined by `git show e4405966c87c8a7843b340146e90cc1e515bef42:docs/roadmap/implementation.md`;
current behavior remains defined by
the canonical application contracts linked below. the canonical application contracts linked below.
The durable product and integration boundary for this work is established by The durable product and integration boundary for this work is established by

5
docs/roadmap/upgrade-kit.md
View File

@@ -8,7 +8,8 @@ and publication remain separate release preparation. The baseline descriptions
below record the state when this roadmap was written, not current behavior. below record the state when this roadmap was written, not current behavior.
Upgrade directly from Promptkit v0.9.0 to v0.11.0, including the intervening Upgrade directly from Promptkit v0.9.0 to v0.11.0, including the intervening
v0.10.0 catalog transition. This document defines the desired end state and v0.10.0 catalog transition. This document defines the desired end state and
the changes from the current baseline. The [implementation plan](implementation.md) the changes from the current baseline. The historical plan at
`git show 43eea5c7c41d2a8134b3dece60f3af5c98b8fd1c:docs/roadmap/implementation.md`
owns sequencing, concrete interface choices, verification steps, and unresolved owns sequencing, concrete interface choices, verification steps, and unresolved
implementation decisions. implementation decisions.
@@ -268,6 +269,6 @@ boundaries.
the version-matched note remain release preparation. the version-matched note remain release preparation.
Concrete interface decisions and the selected distribution approach are recorded Concrete interface decisions and the selected distribution approach are recorded
in the completed [implementation plan](implementation.md). They do not expand in that completed historical plan. They do not expand
the product into conversations, follow-up messages, application-owned semantic the product into conversations, follow-up messages, application-owned semantic
retry loops, prepared-handle coordination, or multi-step workflows. retry loops, prepared-handle coordination, or multi-step workflows.