src/split intosrc/standard/+src/methodologies/— visual separation of v1.5 production code vs v1.0 reference implementationssrc/standard/:pipeline.py,llm_rewriter.py,translators.py(production)src/methodologies/:humanizer.py,translation_chain.py,llm_rewriter.py(restoredLLMRewriteProcessor),detection_pipeline.py,mixed_engine.py,postprocess.py,detectors/,utils/(reference)- All import paths updated:
python -m src.standard.pipeline,from src.standard import run_standard_pipeline setup.py,scripts/start.*,Dockerfile, all docs, all examples updated to match
tests/test_smoke.py— 12 smoke tests: import verification, public API surface, pure-function unit tests, showcase file integrity (all pass, no API keys required)docs/README.md— documentation navigation index with audience-based routing
- Restored missing
LLMRewriteProcessorclass insrc/methodologies/llm_rewriter.py(was lost during v1.5 merge —humanizer.pydispatcher referenced it but the file only haddeepseek_rewrite) docs/faq.md: chain description updated from DE→ES to FI (was stale from v1.5.0)docs/installation.md: repo URL pointed tomolly554/ai-humanizeinstead oflynote-ai/humanize-textdocs/api-reference.md: rewritten to document both Standard Pipeline and v1.0 dispatcher
examples/showcase/— 5 end-to-end input/output traces with all intermediate step outputs (中文改写 / 日语改写 / 一轮翻译 / 二轮翻译) plus AI-detection verdictsexamples/showcase/README.md— index with detection-confidence table- Pipeline result dict now includes
outputfor each step (was onlylength) - New config option
[pipeline].intermediate_langto swap the intermediate translation language
- Pipeline aligned with production reality: chain is now 4 steps (was documented as 5) —
EN → ZH (DeepSeek) → JA (DeepSeek) → FI (Google) → EN (Niutrans). Finnish replaces the German→Spanish double-hop based on empirical validation. - README.md / README-zh.md / docs/pipeline.md updated to match the actual chain
- Step labels now use Chinese conventions (中文改写 / 日语改写 / 一轮翻译 / 二轮翻译) for consistency with internal terminology
The v1.5 documented chain (5 steps with German→Spanish→target) didn't match the actual production pipeline used to generate validation samples. v1.5.1 fixes this so code, docs, and showcase examples are all consistent.
src/pipeline.py— Production Standard Pipeline integrating Method 1 (Translation Chain) + Method 2 (LLM Rewriting) into a fixed 5-step chainsrc/llm_rewriter.py— DeepSeek-based humanization rewriter with history-context carrying (temperature 1.3)src/translators.py— Google Translate (deep-translator) + Niutrans API clients with chunking for long textn8n/humanize_standard.json— Importable n8n workflow for no-code automation- CLI entry:
python -m src.pipeline --input ... --target ... - Bilingual README (English + Chinese)
- Quality metrics from expert evaluation on 50 text pairs (9.1/10 overall)
- v1.5 Standard Pipeline is now the recommended production path
- v1.0 four methodologies remain in
src/as reference implementations for research and customization
- Method 1: Translation Chain (
src/translation_chain.py) — Multi-language translation hops - Method 2: Multi-Turn LLM Rewriting (
src/humanizer.py, partial) — Iterative LLM rewrites - Method 3: Detection-Guided Feedback Loop (
src/detection_pipeline.py,src/detectors/) — Binoculars-inspired + RoBERTa scoring loop - Method 4: Mixed-Engine Translation (
src/mixed_engine.py) — Multiple NMT engines combined - Documentation of all four methodologies in
docs/techniques.md - Comparison examples in
examples/comparison/