Record catalog contract preparation

This commit is contained in:
2026-09-22 12:11:24 +00:00
parent 3bc624ec3f
commit 7389410966
2 changed files with 11 additions and 9 deletions

View File

@@ -66,6 +66,8 @@ and blockers; do not treat an unrun check as successful.
## Stage 1: Prepare Both Catalog Modules For The New Contract
**Completed:** 2026-09-22
Repositories: `../promptkit-backend-openrouter` and
`../promptkit-backend-rakestrawhome`. Their small data-only packages make this
one bounded prompt; keep changes in their respective repositories.

View File

@@ -2,11 +2,11 @@
## Status
Provisional and under active discussion. Nothing in this roadmap is an
accepted policy, an implementation commitment, a release decision, or a
description of current Promptkit behavior. Current code, GoDoc, durable
documentation, published module contracts, and release tags remain
authoritative until this proposal is finalized and implemented.
Accepted for implementation on 2026-09-22. The implementation sequence and
completion status are maintained in the
[profile-policy implementation plan](implementation.md). Current code, GoDoc,
durable documentation, published module contracts, and release tags remain
authoritative until each corresponding implementation change lands.
## Prerequisite And Sequencing
@@ -18,7 +18,8 @@ this subsequent work introduces the deliberate profile-policy changes.
Profile-source composition, maintained-profile construction, and catalog
dependency assembly must use the internal owners established by that refactor.
Both scopes may ship in `v0.10.0`, but they remain separately reviewable changes.
This prerequisite does not prevent continued discussion or planning here.
This prerequisite has been satisfied. The remaining work proceeds through the
[profile-policy implementation plan](implementation.md).
## Purpose
@@ -339,9 +340,8 @@ Promptkit and each maintained catalog repository:
- publish the policy transition and its consumer impact in the eventual
Promptkit minor release note and annotated tag.
No implementation should begin from this document until its provisional
status has been updated through the repository's normal planning process and
the public facade refactor prerequisite has been completed.
Implementation is sequenced and tracked in the
[profile-policy implementation plan](implementation.md).
## Non-Goals