content-loop

Content Loop: generate -> validate -> fix -> deploy (self-correcting)

Invocation: /content-loop $1 where $1 is a page slug (e.g. technical-diving) or a topic. Operate on the gotodive workspace.

Languages (authoritative set)

en (source) + ru, de. EN is hand-authored source of truth in output/en/<slug>.html; ru and de are generated and post-edited.

Definition of Done (ALL must be green before deploy)

1. EN copy exists, professional, on-topic (tech/CCR diving), no fabricated facts.
2. ru and de generated AND structurally in sync with EN.
3. No encoding corruption (no literal ??, no mojibake/U+FFFD) in any file.
4. No duplicated/echoing words, no sentence fragmentation in ru/de.
5. No broken internal links; sitemap URLs resolve same-language 200.
6. Layout/visual check passes (no overflow, no broken sections) on desktop+mobile.

NEVER deploy to LIVE prod until every gate above is green AND the user confirms.

PHASE 1 — GENERATE

• Author/refine EN in output/en/<slug>.html (single physical line per text node; NEVER split a meaningful phrase across a newline — it causes double-translation).
• Generate ru + de (free gtx + masking glossary, preserves brand/dive terms): python scripts/generate_full_page_translations.py --langs ru,de --slugs <en-slug>
  • --slugs is an EXACT en-slug filter (not substring). Use it, not --match.

PHASE 2 — VALIDATE

Delegate to the precheck skill: /precheck <slug> --langs ru,de. It runs encoding guard, translation-sync, dupe-words, fragmentation, links, sitemap — and returns PRECHECK: PASS or PRECHECK: FAIL (<n>) with details.

PHASE 3 — FIX (self-correct, then GO BACK to PHASE 2)

Apply the known remedy per failure, then re-run PHASE 2. Repeat up to 5 iterations; if still failing, STOP and report what is stuck.

• Structure drift (tag mismatch / node delta >1): fix EN source then regenerate that slug; do NOT hand-hack locale tags.
• Double trailing word / fragmentation: usually a mid-phrase newline in EN -> merge onto one line, regenerate the slug (generator collapses whitespace).
• Spec-key Latin/garbled: python scripts/_apply-spec-keys.py --langs ru,de.
• ?? / mojibake: re-author the real UTF-8 glyph; deploy ONLY via binary scp (never echo non-ASCII through PowerShell). Prefer HTML entities (·) for separators in theme PHP/HTML to be encoding-proof.

PHASE 4 — DEPLOY

Hand off to the safe-deploy skill (backup -> diff -> confirm -> deploy -> live-verify -> rollback-on-fail). Do not deploy directly from here.

PHASE 5 — DONE

Report: languages produced (en/ru/de), gates passed, files deployed, live result.

Hard rules

• Honesty: no invented people, agencies, certifications, or stats.
• gotodive.com = authority/E-E-A-T site; never add prices/booking (that's .eu).
• Keep EN phrases on one physical line; avoid mid-phrase newlines.
• Apply by WP ID, never by slug, for locale meta/body deploys.
• Stop after 5 fix iterations and ask for help rather than looping forever.