Improve prompt roles and correction repair context

This commit is contained in:
2026-11-11 17:42:30 +00:00
parent cf1fbe5748
commit f42573f8b0
23 changed files with 256 additions and 40 deletions

View File

@@ -2,11 +2,11 @@
**Updated:** 2026-11-11
**Status:** Accepted; implementation has not begun. This roadmap replaces the
completed prompt-quality plan with the recommendations from the fresh review of
revision `d155bf4`. The review covered all eleven prompt definitions, shared
instructions, response schemas, and request assembly. It identified design
concerns, not measured live-model regressions.
**Status:** All six stages implemented and verified. Broader context changes and
live-model editorial evaluation remain deferred as described below. The plan
followed the review of revision `d155bf4`, which covered all eleven prompt
definitions, shared instructions, response schemas, and request assembly.
That review identified design concerns, not measured live-model regressions.
## Target State and Boundaries
@@ -173,6 +173,20 @@ establish live-model editorial quality.
## Deferred Evidence and Follow-Up
The evidence review examined the maintained local, campaign, and prompt-edit
transcript examples, adjacent-context validation fixtures, and proposal
application fixtures. The glossary example is a single-segment correction;
the validation fixture supplies the troupe definition and adjacent evidence
needed to assess its proposed name change. These sources contain no recorded
live-model rejection demonstrating a need for more distant context. The target
speaker is now included; broader selection and context fitting remain unchanged.
Revisit the window when a captured case shows material evidence in the proposal
request that was absent from validation.
The existing stale-span application fixture demonstrates the mechanical overlap
addressed by the new guidance. It does not establish a need for new combined
semantic validation, so application ordering and rejection rules remain unchanged.
Formal evaluation corpus preparation and live-model comparisons remain deferred
and are not prerequisites for the agreed changes. Broader validation context and
additional handling of combined semantic effects should follow concrete evidence
@@ -182,3 +196,34 @@ repair outcomes using independent editorial judgment. Keep live calls opt-in
and separate from the default offline suite.
No blocking product decisions remain for the implementation scope above.
## Completion and Verification
- The four proposal definitions now separate durable system principles from
their initial user assignments. The shared proposal guidance covers overlapping
and dependent edits; the grammar prompt illustrates a combined edit.
- Every repair attempt receives the current target's original text when
available and its previewed result when applicable, using the same domain
replacement function as validation. Revision and withdrawal examples accompany
the shared repair guidance.
- Validation includes the target speaker in rendered input and token accounting.
Spoken-word proposal and editorial review examples distinguish meaningful
apparent filler from removable hesitation. The meaning-reversal definition and
all response schemas retain their existing contracts.
- Behavioral tests cover repair deletion and replace-all previews, ambiguous or
missing spans, blank results, missing targets, and refresh after retargeting.
Existing validation tests now cover target-speaker propagation, absence, and
budget fitting, including parity with serialized payload estimates.
- The affected prompt, module, request-assembly, and conversation tests were
reviewed for wording checks. No further bundled-prose change detectors were
found to remove; the earlier cleanup remains effective. Retained assertions
protect supplied-data rendering, schema selection, operator replacement,
conversation history, revalidation, withdrawal, and outcomes. New assertions
check request data and behavior rather than prompt phrases.
- All eleven definitions prepared through the CLI. Four illustrative complete
conversations, including subsequent repair requests, were reviewed, and the
sixteen embedded JSON response examples passed schema checks. The application
build and full offline Go suite passed. Canonical documentation and maintained
preview examples were updated; links and whitespace were checked.
These checks verify implementation and editorial intent, not live-model quality.