Skip to content

Enforce mandatory precision translation - #1

Draft
puritysb wants to merge 2 commits into
mainfrom
codex/mandatory-precision-translation
Draft

Enforce mandatory precision translation#1
puritysb wants to merge 2 commits into
mainfrom
codex/mandatory-precision-translation

Conversation

@puritysb

@puritysb puritysb commented Aug 3, 2026

Copy link
Copy Markdown
Owner

What changed

  • makes precision translation mandatory for every request
  • researches source provenance and prefers verified original-language public-domain editions
  • builds a web-grounded, adversarially cross-checked concept sheet
  • adds fail-closed terminology auditing and contextual repair
  • binds checkpoints to the source and precision profile
  • updates the MCP surface, documentation, and tests

Why

Fluent Korean could hide conceptual errors or collapse neighboring philosophical terms. This change prioritizes semantic and philological accuracy without requiring manual terminology approval.

Validation

  • ./venv/bin/python3 -m unittest discover -s tests -v (14 passed)
  • ./venv/bin/python3 -m py_compile ...
  • git diff --check

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.

1 participant