Optimize recruiter-facing Voice2Task project page#4
Draft
Raidriar7170 wants to merge 5 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Scope
This is a docs-only stacked PR. It targets
codex/materialize-manifest-bound-train-only-sft-v1and changes onlyREADME.md,README_en.md, and the committed recruiter-facing design/implementation planning documents.There are no runtime, source, test, config, training, inference, evaluation, DPO, GRPO, data, metric, or evidence mutations. This PR does not merge, release, deploy, or publish a checkpoint or adapter.
Verification
PYTHONPATH=src pytest -q: 1485 passedPYTHONPATH=src ruff check .: passedOPENSPEC_TELEMETRY=0 openspec validate --all --strict: 15/15 passedgit diff --check origin/codex/materialize-manifest-bound-train-only-sft-v1...HEAD: passedResult boundary
The Final SFT arm scored higher on semantic/channel aggregate metrics, but strict exact fell from 1.67% to 0.83%; therefore, this PR makes no overall model improvement claim.
No training, inference, evaluation, DPO, GRPO, data, metric, or evidence mutation was performed. No merge, release, deploy, checkpoint publication, or adapter publication was performed.