Complete Phase 14 homophones module
This commit is contained in:
@@ -65,6 +65,9 @@ Implemented:
|
||||
- Glossary-derived deterministic protected-term extraction and validator integration.
|
||||
- Explicit `--modules glossary` runtime path through runner, shared proposal generation, validators, application, reporting, and diagnostics.
|
||||
- Repeated glossary stage support with deterministic instance names (`glossary_1`, `glossary_2`), including mutable working-transcript handoff.
|
||||
- Production homophones module package with Python-aligned prompt intent and guardrails.
|
||||
- Explicit `--modules homophones` runtime path through runner, shared proposal generation, validators, application, reporting, and diagnostics.
|
||||
- Focused multi-module runtime tests for already-implemented interoperability (for example `glossary,homophones`) without claiming full default-pipeline completion.
|
||||
- Broad deterministic and CLI/subprocess test coverage for implemented phases through `go test ./...`.
|
||||
- Internal typed structured LLM contract (`StructuredLLMClient.CompleteStructured(ctx, req, out)`).
|
||||
- `internal/framework/llm` instructor-go-backed adapter with:
|
||||
@@ -80,8 +83,8 @@ Implemented:
|
||||
- Generic JSON diagnostics primitives for LLM interactions (request metadata, request payload, response payload, optional error payload) with secret redaction.
|
||||
|
||||
Not yet implemented in runtime pipeline:
|
||||
- Real correction modules for `homophones` and `spoken_word`.
|
||||
- Domain proposal prompts for remaining real modules.
|
||||
- Real correction module for `spoken_word`.
|
||||
- Domain proposal prompts for remaining real module.
|
||||
- End-to-end transcript polishing behavior with the full default module sequence.
|
||||
|
||||
## Completed phases
|
||||
@@ -220,7 +223,7 @@ Not implemented in Phase 8 (by design):
|
||||
|
||||
## Remaining work plan
|
||||
|
||||
Next recommended phase: **Phase 14 (homophones module)**.
|
||||
Next recommended phase: **Phase 15 (spoken-word module)**.
|
||||
|
||||
## Phase 9: Structured LLM client and scheduler infrastructure
|
||||
|
||||
@@ -391,41 +394,27 @@ Not implemented in Phase 13 (by design):
|
||||
|
||||
## Phase 14: Homophones module
|
||||
|
||||
### Purpose
|
||||
Completed.
|
||||
|
||||
Implement conservative homophone and mistranscription correction behavior.
|
||||
Implemented:
|
||||
- Production homophones module package in `internal/modules/homophones`.
|
||||
- Homophones prompt builder aligned to Python intent and constrained to conservative homophone/near-homophone/mistranscription corrections.
|
||||
- Prompt context using glossary/protected-term information (names, aliases, plurals where present) to avoid damaging known domain terms.
|
||||
- Homophones proposal generation through shared `internal/framework/proposal_generation` using `contracts.StructuredLLMClient`.
|
||||
- Scheduler-aware homophones proposal generation through existing scheduler hooks.
|
||||
- Homophones replacement policy `require_unique` (matching Python behavior).
|
||||
- Homophones validator chain using existing deterministic and LLM-backed validators.
|
||||
- Homophones confidence threshold enforcement through existing config + confidence-threshold validator behavior.
|
||||
- Protected-term guardrails remaining active for homophones via existing deterministic validators.
|
||||
- Explicit runtime support for `--modules homophones` through normalization, chunking, runner, proposal generation, validation, application, and reporting.
|
||||
- Prompt/response diagnostics artifacts for homophones proposal + validator interactions with secret redaction.
|
||||
- Module-level reports for homophones including generated proposals, validator decisions/rejections, applied changes, and application skips.
|
||||
- CLI/runtime fake-client tests for approved proposals, validator rejection, application skips, diagnostics, protected-term rejection behavior, failure/error.log behavior, and report outputs (`--report-json` and run-dir `report.json`).
|
||||
- Focused interoperability tests for already-implemented module combinations (for example `glossary,homophones`) to verify working-transcript handoff and guardrails without claiming full default-sequence parity.
|
||||
|
||||
### Scope
|
||||
|
||||
Implement:
|
||||
- `homophones` module package.
|
||||
- Homophones prompt builder ported from Python.
|
||||
- Homophones structured response model.
|
||||
- Homophones replacement policy.
|
||||
- Homophones confidence threshold handling.
|
||||
- Homophones validator chain.
|
||||
- Prompt/response diagnostics.
|
||||
- CLI support for `--modules homophones`.
|
||||
- Fake LLM tests.
|
||||
- Tests for interaction with glossary/protected terms where relevant.
|
||||
|
||||
Do not implement:
|
||||
- Spoken-word module.
|
||||
- Default full pipeline parity claim unless spoken-word is already complete.
|
||||
|
||||
### Expected behavior at end of phase
|
||||
|
||||
Running `audita process ... --modules homophones` should perform real conservative homophone/mistranscription corrections using the configured LLM endpoint.
|
||||
|
||||
### Definition of done
|
||||
|
||||
- Homophones module runs in the production runner.
|
||||
- Homophones proposals are generated through structured LLM calls.
|
||||
- Validator chain is enforced.
|
||||
- Protected-term behavior is respected where applicable.
|
||||
- Applied/skipped homophone changes appear in reports.
|
||||
- Prompt/response diagnostics are written.
|
||||
- `go test ./...` passes without requiring external LLM credentials.
|
||||
Not implemented in Phase 14 (by design):
|
||||
- Production `spoken_word` module.
|
||||
- Full default module sequence execution as a feature-complete claim.
|
||||
|
||||
## Phase 15: Spoken-word module
|
||||
|
||||
|
||||
Reference in New Issue
Block a user