Skip to content

docs/usermanuals/en/training/dpo.md: broken example — Workaround: enable reference_free: true (less stable but skips the second model) (DOC-D3B05-011) #237

Open

Description

@cemililik

Wave 1 · theme D1-10: Documentation-only fixes · highest severity High · 1 finding(s) · effort docs fix

Summary

The suggested workaround breaks the config.

Primary finding

DOC-D3B05-011 — docs/usermanuals/en/training/dpo.md: broken example — Workaround: enable reference_free: true (less stable but skips the second model)

severity High · already tracked: KNOWN-OPEN C31-DOC-SCHEMA-PROSE docs/roadmap/phase-16-trust-surface-hardening.md:785-786

Where. docs/usermanuals/en/training/dpo.md:128 (Turkish mirror: docs/usermanuals/tr/training/dpo.md:116) · type: broken example

The document says. Workaround: enable reference_free: true (less stable but skips the second model)

What the code does. TrainingConfig is extra='forbid' (config.py:449). training.reference_free: true is rejected with 'Extra inputs are not permitted', dry-run exit 1. TRL 1.7.1 DPOConfig has no reference_free field. Line 114 of the same page says it is not exposed.

Code references. forgelm/config.py:449

User impact. The suggested workaround breaks the config.

Proposed correction. Delete the reference_free bullet.

Turkish mirror. the Turkish page has the same error; fix both in the same PR

Acceptance criteria

  • Each statement is re-checked against the code at fix time.
  • Documentation listed above is corrected in English and in its Turkish mirror in the same PR.
  • Every finding in this issue is resolved or explicitly closed with a reason.

Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlog: knownAlready tracked in docs/roadmapblockedWaits for another issue (see Blocked by); set and removed automatically, never by handdocumentationImprovements or additions to documentationseverity: highWrong behaviour or a false claim users rely onsource: review-2026-10Found by the October 2026 code and documentation reviewwave: 1Roadmap wave 1: high severity, small effort

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions