From be5a508554a271c8d22c43595615251991087952 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Fri, 20 Nov 2026 15:28:08 +0000 Subject: [PATCH] List feature considerations for the next release --- docs/roadmap/next-release-considerations.md | 39 +++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 docs/roadmap/next-release-considerations.md diff --git a/docs/roadmap/next-release-considerations.md b/docs/roadmap/next-release-considerations.md new file mode 100644 index 0000000..1bf80e2 --- /dev/null +++ b/docs/roadmap/next-release-considerations.md @@ -0,0 +1,39 @@ +# Feature Considerations Before The Next Release + +Status: candidates for discussion, not accepted implementation requirements. +Review these items before the next release; inclusion in this list does not +commit them to that release. Schema support implementation continues under the +[prompt-owned schemas roadmap](prompt-owned-schemas.md). + +## 1. Enable One Structured-Output Repair Attempt By Default + +Consider changing the default number of structured-output repair attempts from +zero to one. The intended benefit is automatic recovery from an invalid structured +response without requiring each consumer to opt in. + +Before accepting, settle: + +- Which validation modes and execution paths receive the default. +- How callers explicitly select zero attempts, including Go values where zero + may currently also represent omission. +- How to communicate the possibility of an additional inference request, with + corresponding latency and usage, when repair is needed. + +## 2. Place Configuration Under A Root-Level `promptkit` Key + +Consider moving PromptKit-owned configuration beneath `promptkit`, for example +from `prompts` to `promptkit.prompts`. This would give applications a distinct +configuration section for PromptKit alongside their other settings. + +Before accepting, settle: + +- The complete field scope, including backends, profiles, collections, and schema + roots; ConfigKit-owned source headers and directives retain ConfigKit semantics. +- Whether to make a clean breaking migration or support a transition period. +- How collection imports, bundled defaults, typed configuration helpers, and + inspection use the new location through normal ConfigKit composition. +- Migration guidance and coordination with the schema work currently underway. + +## Further Candidates + +Append additional pre-release considerations here as they arise.