1.8 KiB
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. Implemented schema support is documented in the format reference.
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 accounting for the implemented schema-source changes.
Further Candidates
Append additional pre-release considerations here as they arise.