Skip to content

Select current-year writing; point demo and README at the write path - #47

Merged
telivity-otaip merged 1 commit into
mainfrom
fix/select-year-and-write-path-docs
Jul 30, 2026
Merged

Select current-year writing; point demo and README at the write path#47
telivity-otaip merged 1 commit into
mainfrom
fix/select-year-and-write-path-docs

Conversation

@telivity-otaip

Copy link
Copy Markdown
Contributor

select capped the corpus at a hardcoded DEFAULT_THROUGH_YEAR = 2024, so any corpus written in 2025 or later selected zero pieces. build-style-profile reads that selection, which means the style card driving every write draft was measured from a pre-2025 slice — or from nothing. run_build_writer_sft already bypassed the year gate for exactly this reason; select had not caught up. The cap now defaults to the current year, and --through-year stays for deliberate narrowing. Holdouts remain separate and explicit (--holdout-id).

Also:

  • run_demo now runs select → index-voice → build-style-profile → write, stubbing only the model call through the existing generate_fn seam. No weights download. Retrieval, style card, trim and guards are the real code. The mock train/filter tail stays because test_api_health depends on it.
  • Demo output names the write path and marks the stub: adapter=none model=stub.
  • select now points at index-voice; train points at eval-write-holdout with the keep-only-if-it-beats-RAG rule.
  • README: select added to the quick start — build-style-profile requires it, so the documented path previously dead-ended.
  • Regenerated cli-status.png and cli-demo.png from real output, added cli-setup.png and scripts/shot.py so docs images stay reproducible.

ruff clean, 272 tests pass (3 new), sanitize OK.

Open in Web Open in Cursor 

Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
@telivity-otaip
telivity-otaip marked this pull request as ready for review July 30, 2026 18:51
@telivity-otaip
telivity-otaip merged commit 9a7fd32 into main Jul 30, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants