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

Plan the public output repair implementation

Browse Source
This commit is contained in:
Eric Rakestraw
2026-08-25 09:38:06 +00:00
parent 115fe8ba58
commit e827631d8c
2 changed files with 596 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/roadmap/output-repair.md
View File

@@ -264,9 +264,9 @@ public fields and updates their contracts:
- `Run`, `RunPrepared`, and related result GoDoc describe exhaustion, failure,
usage, cancellation, and prepared-execution behavior.
Once implemented, the framework format reference owns the exact
The framework format reference owns the exact
`repair_attempts` YAML semantics and the meaning of `none`, `basic`, `json`,
and `json_schema`. Consumer guidance should contain one concise JSON Schema
and `json_schema`. Consumer guidance contains one concise JSON Schema
example, note that `basic` can repair empty output, and emphasize that content
presence or structural validity does not establish domain correctness. The
internal runner document owns orchestration and test ownership. The
@@ -274,9 +274,9 @@ OpenAI-compatible integration contract owns the explicit-empty versus missing
content distinction. Architecture policy needs to change only if implementation
changes its existing package boundaries.
Current-state documentation must not describe public repair as available until
the public engine actually installs it. Completed roadmap material should be
retired after the implementation and canonical documentation land.
Canonical current-state documentation describes implemented behavior in
accordance with the documentation policy. Roadmap material remains temporary
and is retired when it no longer describes future work.
## Verification Expectations