diff --git a/.agents/skills/cut-release/SKILL.md b/.agents/skills/cut-release/SKILL.md
index 42fb079d..7b74cc99 100644
--- a/.agents/skills/cut-release/SKILL.md
+++ b/.agents/skills/cut-release/SKILL.md
@@ -186,7 +186,7 @@ Highlights:
 - GGUF export
 - VRAM fit advisor
 
-Full changelog: https://github.com/cemililik/ForgeLM/blob/main/CHANGELOG.md
+Full changelog: https://github.com/HodeTech/ForgeLM/blob/main/CHANGELOG.md
 Upgrade: pip install --upgrade forgelm
 ```
 
diff --git a/.agents/skills/sync-bilingual-docs/SKILL.md b/.agents/skills/sync-bilingual-docs/SKILL.md
index d6990299..ee8d11cd 100644
--- a/.agents/skills/sync-bilingual-docs/SKILL.md
+++ b/.agents/skills/sync-bilingual-docs/SKILL.md
@@ -36,7 +36,7 @@ usermanual page, every link MUST be one of:
 
 1. A SPA route `#/<section>/<page>` where the target file exists under
    `docs/usermanuals/<lang>/<section>/<page>.md`.
-2. An absolute HTTPS URL (use `https://github.com/cemililik/ForgeLM/blob/main/<path>`
+2. An absolute HTTPS URL (use `https://github.com/HodeTech/ForgeLM/blob/main/<path>`
    for project files that live outside the manual — guides, references,
    QMS templates, source files, the roadmap).
 3. A pure same-file anchor (`#heading-slug`).
diff --git a/.claude/skills/cut-release/SKILL.md b/.claude/skills/cut-release/SKILL.md
index 42fb079d..7b74cc99 100644
--- a/.claude/skills/cut-release/SKILL.md
+++ b/.claude/skills/cut-release/SKILL.md
@@ -186,7 +186,7 @@ Highlights:
 - GGUF export
 - VRAM fit advisor
 
-Full changelog: https://github.com/cemililik/ForgeLM/blob/main/CHANGELOG.md
+Full changelog: https://github.com/HodeTech/ForgeLM/blob/main/CHANGELOG.md
 Upgrade: pip install --upgrade forgelm
 ```
 
diff --git a/.claude/skills/sync-bilingual-docs/SKILL.md b/.claude/skills/sync-bilingual-docs/SKILL.md
index d6990299..ee8d11cd 100644
--- a/.claude/skills/sync-bilingual-docs/SKILL.md
+++ b/.claude/skills/sync-bilingual-docs/SKILL.md
@@ -36,7 +36,7 @@ usermanual page, every link MUST be one of:
 
 1. A SPA route `#/<section>/<page>` where the target file exists under
    `docs/usermanuals/<lang>/<section>/<page>.md`.
-2. An absolute HTTPS URL (use `https://github.com/cemililik/ForgeLM/blob/main/<path>`
+2. An absolute HTTPS URL (use `https://github.com/HodeTech/ForgeLM/blob/main/<path>`
    for project files that live outside the manual — guides, references,
    QMS templates, source files, the roadmap).
 3. A pure same-file anchor (`#heading-slug`).
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 84303983..82159ed6 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,8 +1,8 @@
 blank_issues_enabled: false
 contact_links:
   - name: Documentation
-    url: https://github.com/cemililik/ForgeLM/tree/main/docs
+    url: https://github.com/HodeTech/ForgeLM/tree/main/docs
     about: Check the docs and guides before opening an issue
   - name: Discussions (Q&A)
-    url: https://github.com/cemililik/ForgeLM/discussions
+    url: https://github.com/HodeTech/ForgeLM/discussions
     about: Ask questions and get help from the community
diff --git a/.github/workflows/nightly.yml b/.github/workflows/nightly.yml
index acfd2747..53b63bc9 100644
--- a/.github/workflows/nightly.yml
+++ b/.github/workflows/nightly.yml
@@ -101,7 +101,7 @@ jobs:
           # Colab installs depend on a specific branch HEAD, breaking
           # reproducibility and confusing users when main moves ahead of
           # the latest released wheel.
-          if grep -rn 'git+https://github.com/cemililik/ForgeLM' notebooks/; then
+          if grep -rn 'git+https://github.com/HodeTech/ForgeLM' notebooks/; then
             echo "::error::Notebooks must install from PyPI, not git+https"
             exit 1
           fi
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 161950cd..b060a8f6 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -15,7 +15,7 @@ the whole chain — including auto-chained inputs, per-stage gates,
 crash-safe resume, and 7 new pipeline-scoped audit events that join on a
 single top-level `run_id`.  The release also lands a critical SSRF
 hardening for outbound webhook / judge / synthetic destinations
-(issue [#14](https://github.com/cemililik/ForgeLM/issues/14)).
+(issue [#14](https://github.com/HodeTech/ForgeLM/issues/14)).
 Single-stage configs reach `forgelm/trainer.py` byte-identical to
 v0.6.0; the orchestrator module is never imported when no `pipeline:`
 block is present.
@@ -486,7 +486,7 @@ pytest-randomly adoption) is under **Internal**.
 workflow ([`.github/workflows/publish.yml`](.github/workflows/publish.yml))
 which gates PyPI publish on 12 wheel-install matrix combos
 (3 OS × 4 Python). GitHub Release:
-[v0.5.6](https://github.com/cemililik/ForgeLM/releases/tag/v0.5.6).
+[v0.5.6](https://github.com/HodeTech/ForgeLM/releases/tag/v0.5.6).
 
 Patch release. Reverts the v0.5.5 `torch>=2.3.0` minimum back to
 `torch>=2.2.0` to restore Intel Mac (x86_64) installability. The
@@ -1091,7 +1091,7 @@ collectors / BYOD / IO concerns.
 ### Fixed
 
 - **Nightly pip-audit gate — `transformers` CVE-2026-1839**
-  (issue [#37](https://github.com/cemililik/ForgeLM/issues/37)). The
+  (issue [#37](https://github.com/HodeTech/ForgeLM/issues/37)). The
   Supply-chain security workflow flagged the CVE whose published fix
   lives in `transformers 5.0.0rc3` (release candidate). ForgeLM's
   `pyproject.toml` pins `transformers>=4.38.0,<5.0.0`; the 5.x branch
@@ -1405,7 +1405,7 @@ Same review surface as rounds 4-7; further hardening on top of the
   URL cannot be redirected to a private destination) and the
   `mask_secrets` `ImportError` fallback emits `[REDACTED — secrets
   masker unavailable]` instead of the raw 512-char reason prefix.
-  See [#14](https://github.com/cemililik/ForgeLM/issues/14) for the
+  See [#14](https://github.com/HodeTech/ForgeLM/issues/14) for the
   remaining DNS-rebinding TOCTOU follow-up tracked for `v0.5.3`.
 - **Trainer governance failure visibility** (`forgelm/trainer.py`) — the
   `data_governance_report.json` export try/except now catches the full
@@ -2073,9 +2073,9 @@ Major release: ForgeLM goes from a basic SFT fine-tuning tool to a full-stack LL
 - Basic evaluation checks (max loss, baseline comparison)
 - Auto-revert on quality degradation
 
-[Unreleased]: https://github.com/cemililik/ForgeLM/compare/v0.7.0...HEAD
-[0.7.0]: https://github.com/cemililik/ForgeLM/compare/v0.6.0...v0.7.0
-[0.6.0]: https://github.com/cemililik/ForgeLM/compare/v0.5.7...v0.6.0
-[0.5.7]: https://github.com/cemililik/ForgeLM/compare/v0.5.6...v0.5.7
-[0.5.6]: https://github.com/cemililik/ForgeLM/compare/v0.5.5...v0.5.6
-[0.5.5]: https://github.com/cemililik/ForgeLM/compare/v0.5.0...v0.5.5
+[Unreleased]: https://github.com/HodeTech/ForgeLM/compare/v0.7.0...HEAD
+[0.7.0]: https://github.com/HodeTech/ForgeLM/compare/v0.6.0...v0.7.0
+[0.6.0]: https://github.com/HodeTech/ForgeLM/compare/v0.5.7...v0.6.0
+[0.5.7]: https://github.com/HodeTech/ForgeLM/compare/v0.5.6...v0.5.7
+[0.5.6]: https://github.com/HodeTech/ForgeLM/compare/v0.5.5...v0.5.6
+[0.5.5]: https://github.com/HodeTech/ForgeLM/compare/v0.5.0...v0.5.5
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index 8c76d6c5..06b926e4 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -36,7 +36,7 @@ This Code of Conduct applies within all community spaces — GitHub issues, pull
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers at:
 
-**Email:** [ai-team@cemililik.com](mailto:ai-team@cemililik.com)
+**Email:** [forgelm@hodetech.io](mailto:forgelm@hodetech.io)
 
 All complaints will be reviewed and investigated promptly and fairly. All maintainers are obligated to respect the privacy and security of the reporter.
 
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 25b87af2..66cd6553 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -4,8 +4,8 @@ Thanks for your interest in contributing! ForgeLM is an open-source project and
 
 ## Ways to Contribute
 
-- **Bug reports** — found something broken? [Open a bug report](https://github.com/cemililik/ForgeLM/issues/new?template=bug_report.yml)
-- **Feature requests** — have an idea? [Open a feature request](https://github.com/cemililik/ForgeLM/issues/new?template=feature_request.yml)
+- **Bug reports** — found something broken? [Open a bug report](https://github.com/HodeTech/ForgeLM/issues/new?template=bug_report.yml)
+- **Feature requests** — have an idea? [Open a feature request](https://github.com/HodeTech/ForgeLM/issues/new?template=feature_request.yml)
 - **Code** — fix a bug, add a feature, improve tests
 - **Documentation** — fix typos, improve guides, add examples
 - **Notebooks** — add Colab notebooks for new use cases
@@ -18,7 +18,7 @@ Thanks for your interest in contributing! ForgeLM is an open-source project and
 ```bash
 git clone https://github.com/YOUR_USERNAME/ForgeLM.git
 cd ForgeLM
-git remote add upstream https://github.com/cemililik/ForgeLM.git
+git remote add upstream https://github.com/HodeTech/ForgeLM.git
 ```
 
 ### 2. Install (dev mode)
@@ -196,12 +196,12 @@ style: apply ruff format
 
 ## First-Time Contributors
 
-Look for issues labeled [`good first issue`](https://github.com/cemililik/ForgeLM/labels/good%20first%20issue). These are designed to be approachable for newcomers.
+Look for issues labeled [`good first issue`](https://github.com/HodeTech/ForgeLM/labels/good%20first%20issue). These are designed to be approachable for newcomers.
 
 ## Questions?
 
-- **GitHub Discussions** — [Ask a question](https://github.com/cemililik/ForgeLM/discussions)
-- **Issues** — [Report a bug or request a feature](https://github.com/cemililik/ForgeLM/issues)
+- **GitHub Discussions** — [Ask a question](https://github.com/HodeTech/ForgeLM/discussions)
+- **Issues** — [Report a bug or request a feature](https://github.com/HodeTech/ForgeLM/issues)
 
 ## License
 
diff --git a/README.md b/README.md
index b3e98d2b..9bcf4a04 100644
--- a/README.md
+++ b/README.md
@@ -3,7 +3,7 @@
 [![PyPI](https://img.shields.io/pypi/v/forgelm.svg)](https://pypi.org/project/forgelm/)
 [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
-[![CI](https://github.com/cemililik/ForgeLM/actions/workflows/ci.yml/badge.svg)](https://github.com/cemililik/ForgeLM/actions/workflows/ci.yml)
+[![CI](https://github.com/HodeTech/ForgeLM/actions/workflows/ci.yml/badge.svg)](https://github.com/HodeTech/ForgeLM/actions/workflows/ci.yml)
 
 **A config-driven LLM fine-tuning toolkit for everyone — from solo researchers to enterprise platform teams.** SFT → DPO → SimPO → KTO → ORPO → GRPO, with safety evaluation, EU AI Act compliance, and CI/CD-native design baked in. YAML in — fine-tuned model + audit artefacts out.
 
@@ -118,9 +118,9 @@ Full details: [Safety & Compliance Guide](docs/guides/safety_compliance.md) · [
 
 Featured walkthroughs, runnable in Colab on a free T4 GPU:
 
-- [Quick Start — SFT Fine-Tuning](notebooks/quickstart_sft.ipynb) [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/quickstart_sft.ipynb)
-- [GRPO Reasoning RL](notebooks/grpo_reasoning.ipynb) [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/grpo_reasoning.ipynb)
-- [Safety Evaluation & Red-Teaming](notebooks/safety_evaluation.ipynb) [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/safety_evaluation.ipynb)
+- [Quick Start — SFT Fine-Tuning](notebooks/quickstart_sft.ipynb) [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/quickstart_sft.ipynb)
+- [GRPO Reasoning RL](notebooks/grpo_reasoning.ipynb) [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/grpo_reasoning.ipynb)
+- [Safety Evaluation & Red-Teaming](notebooks/safety_evaluation.ipynb) [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/safety_evaluation.ipynb)
 
 See [notebooks/](notebooks/) for the full set (DPO, KTO, multi-dataset, GaLore, synthetic data, post-training workflow, data curation).
 
@@ -133,7 +133,7 @@ See [notebooks/](notebooks/) for the full set (DPO, KTO, multi-dataset, GaLore,
 pip install forgelm
 
 # From source
-git clone https://github.com/cemililik/ForgeLM.git
+git clone https://github.com/HodeTech/ForgeLM.git
 cd ForgeLM
 pip install -e .
 ```
diff --git a/docs/guides/quickstart-tr.md b/docs/guides/quickstart-tr.md
index 159e786a..63243c40 100644
--- a/docs/guides/quickstart-tr.md
+++ b/docs/guides/quickstart-tr.md
@@ -12,7 +12,7 @@
 ## 1. Kurulum
 
 ```bash
-git clone https://github.com/cemililik/ForgeLM.git
+git clone https://github.com/HodeTech/ForgeLM.git
 cd ForgeLM
 pip install -e .
 
@@ -63,7 +63,7 @@ seçilmiş kendi fallback'i vardır:
 `--model your-org/your-model` ya da `--dataset path/to/your.jsonl` ile
 override edin.
 
-Bundled seed dataset'lerin lisansları için bkz. [LICENSES.md](https://github.com/cemililik/ForgeLM/blob/main/forgelm/templates/LICENSES.md)
+Bundled seed dataset'lerin lisansları için bkz. [LICENSES.md](https://github.com/HodeTech/ForgeLM/blob/main/forgelm/templates/LICENSES.md)
 (CC-BY-SA 4.0, yazar-orijinal).
 
 ### Seçenek A: Etkileşimli Sihirbaz
@@ -309,7 +309,7 @@ synthetic:
 Sentetik satır sayısı seed-file boyutu ile kontrol edilir (seed başına
 bir teacher çağrısı); tam alan seti için `forgelm/config.py` içindeki
 `SyntheticConfig` Pydantic modeline bakın
-([repo-arama](https://github.com/cemililik/ForgeLM/search?q=class+SyntheticConfig)).
+([repo-arama](https://github.com/HodeTech/ForgeLM/search?q=class+SyntheticConfig)).
 
 ---
 
diff --git a/docs/guides/quickstart.md b/docs/guides/quickstart.md
index 4b7e63de..c1286d19 100644
--- a/docs/guides/quickstart.md
+++ b/docs/guides/quickstart.md
@@ -12,7 +12,7 @@ Get your first fine-tuned model in 5 minutes.
 ## 1. Install
 
 ```bash
-git clone https://github.com/cemililik/ForgeLM.git
+git clone https://github.com/HodeTech/ForgeLM.git
 cd ForgeLM
 pip install -e .
 
@@ -59,7 +59,7 @@ ForgeLM auto-downsizes the model on small GPUs. Each template has its own fallba
 
 Override with `--model your-org/your-model` or `--dataset path/to/your.jsonl`.
 
-See [LICENSES.md](https://github.com/cemililik/ForgeLM/blob/main/forgelm/templates/LICENSES.md) for the licenses of bundled seed datasets (CC-BY-SA 4.0, author-original).
+See [LICENSES.md](https://github.com/HodeTech/ForgeLM/blob/main/forgelm/templates/LICENSES.md) for the licenses of bundled seed datasets (CC-BY-SA 4.0, author-original).
 
 ### Option A: Interactive Wizard
 
@@ -290,7 +290,7 @@ synthetic:
   output_format: "messages"
 ```
 
-The number of synthetic rows is controlled by the seed-file size (one teacher call per seed); see the `SyntheticConfig` Pydantic model in `forgelm/config.py` for the full field set ([repo search](https://github.com/cemililik/ForgeLM/search?q=class+SyntheticConfig)).
+The number of synthetic rows is controlled by the seed-file size (one teacher call per seed); see the `SyntheticConfig` Pydantic model in `forgelm/config.py` for the full field set ([repo search](https://github.com/HodeTech/ForgeLM/search?q=class+SyntheticConfig)).
 
 ---
 
diff --git a/docs/guides/troubleshooting-tr.md b/docs/guides/troubleshooting-tr.md
index 943b4ee3..f664b60a 100644
--- a/docs/guides/troubleshooting-tr.md
+++ b/docs/guides/troubleshooting-tr.md
@@ -413,6 +413,6 @@ docker run --gpus all --shm-size=16g ...
 
 ## Yardım alma
 
-- **GitHub Issues**: [github.com/cemililik/ForgeLM/issues](https://github.com/cemililik/ForgeLM/issues)
+- **GitHub Issues**: [github.com/HodeTech/ForgeLM/issues](https://github.com/HodeTech/ForgeLM/issues)
 - **Dry-run debug**: `forgelm --config job.yaml --dry-run --log-level DEBUG`
 - **JSON tanılama**: `forgelm --config job.yaml --output-format json 2>error.log`
diff --git a/docs/guides/troubleshooting.md b/docs/guides/troubleshooting.md
index 1e411891..c75cd1f2 100644
--- a/docs/guides/troubleshooting.md
+++ b/docs/guides/troubleshooting.md
@@ -391,6 +391,6 @@ docker run --gpus all --shm-size=16g ...
 
 ## Getting Help
 
-- **GitHub Issues**: [github.com/cemililik/ForgeLM/issues](https://github.com/cemililik/ForgeLM/issues)
+- **GitHub Issues**: [github.com/HodeTech/ForgeLM/issues](https://github.com/HodeTech/ForgeLM/issues)
 - **Dry-run debug**: `forgelm --config job.yaml --dry-run --log-level DEBUG`
 - **JSON diagnostics**: `forgelm --config job.yaml --output-format json 2>error.log`
diff --git a/docs/reference/usage-tr.md b/docs/reference/usage-tr.md
index 0333b1b1..aba8d823 100644
--- a/docs/reference/usage-tr.md
+++ b/docs/reference/usage-tr.md
@@ -8,7 +8,7 @@ ForgeLM, komut satırı arayüzü üzerinden çalıştırılmak üzere tasarlanm
 - CUDA destekli NVIDIA GPU (önerilir; CPU modu çok yavaş)
 
 ```bash
-git clone https://github.com/cemililik/ForgeLM.git
+git clone https://github.com/HodeTech/ForgeLM.git
 cd ForgeLM
 pip install -e .
 ```
diff --git a/docs/reference/usage.md b/docs/reference/usage.md
index 18e17c2d..1e25940d 100644
--- a/docs/reference/usage.md
+++ b/docs/reference/usage.md
@@ -8,7 +8,7 @@ ForgeLM is designed to be executed via the command line, making it perfect for b
 - NVIDIA GPU with CUDA (recommended; CPU mode is very slow)
 
 ```bash
-git clone https://github.com/cemililik/ForgeLM.git
+git clone https://github.com/HodeTech/ForgeLM.git
 cd ForgeLM
 pip install -e .
 ```
diff --git a/docs/roadmap/releases.md b/docs/roadmap/releases.md
index 1ea226ba..acca7eb6 100644
--- a/docs/roadmap/releases.md
+++ b/docs/roadmap/releases.md
@@ -40,7 +40,7 @@
 
 ## v0.4.0 — "Post-Training Completion" (2026-04-26)
 
-**Status:** Released — published to PyPI on 2026-04-26 ([release notes](https://github.com/cemililik/ForgeLM/releases/tag/v0.4.0)).
+**Status:** Released — published to PyPI on 2026-04-26 ([release notes](https://github.com/HodeTech/ForgeLM/releases/tag/v0.4.0)).
 
 Odak: [Phase 10](completed-phases.md). Full post-training handoff: inference, chat, GGUF export, VRAM fit-check, deployment config generation.
 
@@ -60,7 +60,7 @@ Odak: [Phase 10](completed-phases.md). Full post-training handoff: inference, ch
 
 ## v0.4.5 — "Quickstart Layer" (2026-04-26)
 
-**Status:** Released — published to PyPI on 2026-04-26 ([release notes](https://github.com/cemililik/ForgeLM/releases/tag/v0.4.5)). Focus: [Phase 10.5](completed-phases.md) (Quickstart). One-command bundled templates, sample datasets, opinionated defaults — primary community growth driver.
+**Status:** Released — published to PyPI on 2026-04-26 ([release notes](https://github.com/HodeTech/ForgeLM/releases/tag/v0.4.5)). Focus: [Phase 10.5](completed-phases.md) (Quickstart). One-command bundled templates, sample datasets, opinionated defaults — primary community growth driver.
 
 ### Features:
 1. [x] **`forgelm/quickstart.py`** — Template registry (`@dataclass(frozen=True) Template`), `auto_select_model()` GPU-aware downsizing (≥10 GB VRAM → primary model; otherwise fallback ≤2B), `run_quickstart()` end-to-end orchestrator that copies the bundled seed dataset, substitutes `model.name_or_path` and `data.dataset_name_or_path`, and writes a `configs/<template>-YYYYMMDDHHMMSS.yaml` the existing trainer accepts unchanged.
@@ -82,7 +82,7 @@ Odak: [Phase 10](completed-phases.md). Full post-training handoff: inference, ch
 
 ## v0.5.0 — "Document Ingestion + Data Curation Pipeline"
 
-**Status:** ✅ Done — released to [PyPI 2026-04-30](https://pypi.org/project/forgelm/0.5.0/) (Phases 11 + 11.5 + 12 + 12.5 consolidated; merged on `main` 2026-04-29). One hardening follow-up tracked outside the release: [#14 — webhook SSRF DNS-rebinding TOCTOU](https://github.com/cemililik/ForgeLM/issues/14) (defence-in-depth on top of the existing `allow_private_destinations: false` default).
+**Status:** ✅ Done — released to [PyPI 2026-04-30](https://pypi.org/project/forgelm/0.5.0/) (Phases 11 + 11.5 + 12 + 12.5 consolidated; merged on `main` 2026-04-29). One hardening follow-up tracked outside the release: [#14 — webhook SSRF DNS-rebinding TOCTOU](https://github.com/HodeTech/ForgeLM/issues/14) (defence-in-depth on top of the existing `allow_private_destinations: false` default).
 
 > **Note on consolidation.** Originally planned as four sequential PyPI tags (`v0.5.0` / `v0.5.1` / `v0.5.2` / `v0.5.3`), the four phases were consolidated into a single `v0.5.0` because they form one coherent surface (ingest → polish → mature → polish) hard to use in parts. Git history retains the four phases as separate commit batches; this entry collapses them into one user-facing release. CHANGELOG.md preserves the phase boundaries inside the `[0.5.0]` section so reviewers can map back to PR history (#11, #12, #13, #18).
 
@@ -124,13 +124,13 @@ Odak: [Phase 10](completed-phases.md). Full post-training handoff: inference, ch
 
 ### Hardening follow-up (tracked outside this release)
 
-- [#14 — webhook SSRF DNS-rebinding TOCTOU](https://github.com/cemililik/ForgeLM/issues/14): defence-in-depth on top of the existing `allow_private_destinations: false` default. Slated for `v0.5.1`.
+- [#14 — webhook SSRF DNS-rebinding TOCTOU](https://github.com/HodeTech/ForgeLM/issues/14): defence-in-depth on top of the existing `allow_private_destinations: false` default. Slated for `v0.5.1`.
 
 ---
 
 ## v0.6.0 — "Phase 15 Ingestion Pipeline Reliability" (2026-05-11)
 
-**Status:** Released to PyPI 2026-05-11. Minor release on top of v0.5.7. Five review-absorption rounds (Gemini + CodeRabbit + Sonar + Codacy + independent self-review) ship in the same release. GitHub Release: [v0.6.0](https://github.com/cemililik/ForgeLM/releases/tag/v0.6.0).
+**Status:** Released to PyPI 2026-05-11. Minor release on top of v0.5.7. Five review-absorption rounds (Gemini + CodeRabbit + Sonar + Codacy + independent self-review) ship in the same release. GitHub Release: [v0.6.0](https://github.com/HodeTech/ForgeLM/releases/tag/v0.6.0).
 
 ### Summary
 
@@ -167,7 +167,7 @@ See [CHANGELOG.md `[0.6.0]`](../../CHANGELOG.md#060--2026-05-11) for the complet
 
 ## v0.5.7 — "SFT trainer trl-modernisation fix" (2026-05-10)
 
-**Status:** Released to PyPI 2026-05-10. Patch on top of v0.5.6. GitHub Release: [v0.5.7](https://github.com/cemililik/ForgeLM/releases/tag/v0.5.7).
+**Status:** Released to PyPI 2026-05-10. Patch on top of v0.5.6. GitHub Release: [v0.5.7](https://github.com/HodeTech/ForgeLM/releases/tag/v0.5.7).
 
 ### Summary
 
@@ -187,7 +187,7 @@ See [CHANGELOG.md `[0.5.7]`](../../CHANGELOG.md#057--2026-05-10).
 
 ## v0.5.6 — "Intel Mac install fix" (2026-05-10)
 
-**Status:** Released to PyPI 2026-05-10. Patch on top of v0.5.5. GitHub Release: [v0.5.6](https://github.com/cemililik/ForgeLM/releases/tag/v0.5.6).
+**Status:** Released to PyPI 2026-05-10. Patch on top of v0.5.5. GitHub Release: [v0.5.6](https://github.com/HodeTech/ForgeLM/releases/tag/v0.5.6).
 
 ### Summary
 
@@ -207,7 +207,7 @@ See [CHANGELOG.md `[0.5.6]`](../../CHANGELOG.md#056--2026-05-10).
 
 ## v0.5.5 — "Closure Cycle Bundle + Phase 22 Wizard + Site Documentation Sweep" (2026-05-10)
 
-**Status:** Released to PyPI 2026-05-10 via the cross-OS publish workflow ([`.github/workflows/publish.yml`](../../.github/workflows/publish.yml)) which gates PyPI publish on 12 wheel-install matrix combos (3 OS × 4 Python). GitHub Release: [v0.5.5](https://github.com/cemililik/ForgeLM/releases/tag/v0.5.5).
+**Status:** Released to PyPI 2026-05-10 via the cross-OS publish workflow ([`.github/workflows/publish.yml`](../../.github/workflows/publish.yml)) which gates PyPI publish on 12 wheel-install matrix combos (3 OS × 4 Python). GitHub Release: [v0.5.5](https://github.com/HodeTech/ForgeLM/releases/tag/v0.5.5).
 
 ### Summary
 
@@ -241,7 +241,7 @@ See [CHANGELOG.md `[0.5.5]`](../../CHANGELOG.md#055--2026-05-10) for the complet
 
 ## v0.7.0 — "Pipeline Chains" (2026-05-15)
 
-**Status:** Released to PyPI 2026-05-15 via the cross-OS publish workflow ([`.github/workflows/publish.yml`](../../.github/workflows/publish.yml)) — all 12 wheel-install matrix combos (3 OS × 4 Python) green before OIDC trusted publish. GitHub Release: [v0.7.0](https://github.com/cemililik/ForgeLM/releases/tag/v0.7.0).
+**Status:** Released to PyPI 2026-05-15 via the cross-OS publish workflow ([`.github/workflows/publish.yml`](../../.github/workflows/publish.yml)) — all 12 wheel-install matrix combos (3 OS × 4 Python) green before OIDC trusted publish. GitHub Release: [v0.7.0](https://github.com/HodeTech/ForgeLM/releases/tag/v0.7.0).
 
 ### Summary
 
diff --git a/docs/roadmap/risks-and-decisions.md b/docs/roadmap/risks-and-decisions.md
index 0691a0ea..40f88837 100644
--- a/docs/roadmap/risks-and-decisions.md
+++ b/docs/roadmap/risks-and-decisions.md
@@ -95,7 +95,7 @@
 | **F-PR29-A6-15-followup** — Bare `# NOSONAR` rule-code sweep | Low | Lint / Style | ~30 BLE001 sites in `forgelm/` use bare `# NOSONAR` without the rule code. Wave 2-4 added the NOSONAR-discipline section to `coding.md` (rule code + rationale required). Sweep all bare-NOSONAR sites and append `python:S<id>` per the new policy. Mechanical refactor; no behaviour change. | ~2 h | TBD |
 | **F-PR29-A5-anchor-slugifier** — anchor-resolution checker GFM divergence | Low | Tooling | Wave 2-7 surfaced two anchor-slugger divergences vs GitHub-flavored Markdown in `tools/check_anchor_resolution.py`: (i) multi-dash collapse (local checker collapses `-+` → `-`; GFM preserves), (ii) duplicate-heading disambiguation (GFM appends `-1`/`-2`; local stores in `set`). Two fixed locally as workarounds in `safety_compliance-tr.md`; align checker's slugifier with GFM in v0.6.x. | ~2 h | TBD |
 | **F-PR29-A2-13-design-doc-paths** — `library-api-design.md` `forgelm/api.py` references | Low | Docs | Wave 2-13 added a Status callout in §5.1 noting impl diverged from design (3-segment vs 2-segment `__api_version__`), but ~7 downstream sentences still reference `forgelm/api.py` as the version-home module (the file does not exist; `forgelm/_version.py` is canonical). Sweep `__api_version__` location refs in design doc to point at `_version.py` for full historical-vs-current clarity. Doc-only. | ~30 min | TBD |
-| **F-PR29-A6-05-issue-link** — open GitHub issue tracking semantic-chunking deferral | Low | Docs / Tracking | `forgelm/ingestion.py:_chunk_semantic` raises `NotImplementedError` referencing this row. Open a GitHub issue at https://github.com/cemililik/ForgeLM/issues describing the embedding-based semantic-chunking deferral (per [completed-phases.md "Phase 12 — Data Curation Maturity"](completed-phases.md#phase-12-data-curation-maturity), "deferred to Phase 13+ for Annex IV reproducibility"); update the message in `ingestion.py:_chunk_semantic` to reference the real issue number. | ~5 min | TBD |
+| **F-PR29-A6-05-issue-link** — open GitHub issue tracking semantic-chunking deferral | Low | Docs / Tracking | `forgelm/ingestion.py:_chunk_semantic` raises `NotImplementedError` referencing this row. Open a GitHub issue at https://github.com/HodeTech/ForgeLM/issues describing the embedding-based semantic-chunking deferral (per [completed-phases.md "Phase 12 — Data Curation Maturity"](completed-phases.md#phase-12-data-curation-maturity), "deferred to Phase 13+ for Annex IV reproducibility"); update the message in `ingestion.py:_chunk_semantic` to reference the real issue number. | ~5 min | TBD |
 | **F-PR29-A6-lock-file** — `requirements.lock` for development environments | Low | Supply-chain | SonarCloud `text:S8565` flags `pyproject.toml` for missing `uv.lock` / `poetry.lock`. ForgeLM uses pip + setuptools (not uv / poetry), and bounded-range `[project.dependencies]` + nightly `pip-audit` + per-OS CycloneDX SBOMs cover the supply-chain determinism story. A pip-tools workflow producing `requirements.lock` (input: `pyproject.toml` extras; output: pinned hash-locked txt) would be a strict improvement for development environment reproducibility — track here for v0.6.x; SonarCloud finding suppressed via `# NOSONAR text:S8565` at `pyproject.toml:1`. | ~2 h | TBD |
 
 **Removal contract.** A row is removed from this table only when:
diff --git a/docs/standards/code-review.md b/docs/standards/code-review.md
index 3245a33a..e3ea9b43 100644
--- a/docs/standards/code-review.md
+++ b/docs/standards/code-review.md
@@ -1,6 +1,6 @@
 # Code Review Standard
 
-> **Scope:** Every pull request to `cemililik/ForgeLM`. Applies equally to external contributors and the maintainer.
+> **Scope:** Every pull request to `HodeTech/ForgeLM`. Applies equally to external contributors and the maintainer.
 > **Enforced by:** `.github/pull_request_template.md` checklist + CI gates + reviewer attention.
 
 ## The default state of a PR is "blocked"
diff --git a/docs/standards/documentation.md b/docs/standards/documentation.md
index 6d2ea1f8..a680bf29 100644
--- a/docs/standards/documentation.md
+++ b/docs/standards/documentation.md
@@ -102,7 +102,7 @@ Rules:
 ✅ Relative sibling: error-handling.md
 ✅ Relative parent-tree: ../reference/configuration.md
 ❌ Absolute repo path: /docs/reference/configuration.md
-❌ Full GitHub URL: https://github.com/cemililik/ForgeLM/blob/main/docs/reference/configuration.md
+❌ Full GitHub URL: https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/configuration.md
 ```
 
 **External links:** full HTTPS URL. Prefer stable archives (arxiv.org, github.com) over transient news sites.
@@ -121,7 +121,7 @@ The viewer **only** knows how to render two kinds of in-content link:
 | Form | Example | Resolved by |
 |---|---|---|
 | SPA hash-router route | `[Audit Log](#/compliance/audit-log)` | `site/js/guide.js` → loads `docs/usermanuals/<lang>/compliance/audit-log.md` |
-| External HTTPS URL | `[Phase 13 roadmap](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)` | The browser, in a new tab |
+| External HTTPS URL | `[Phase 13 roadmap](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)` | The browser, in a new tab |
 
 Any other form — a repo-relative path like `../../../guides/foo.md`, an
 intra-manual path like `../concepts/choosing-trainer.md`, or a SPA route
diff --git a/docs/usermanuals/en/compliance/annex-iv.md b/docs/usermanuals/en/compliance/annex-iv.md
index 94f549c6..5920afa6 100644
--- a/docs/usermanuals/en/compliance/annex-iv.md
+++ b/docs/usermanuals/en/compliance/annex-iv.md
@@ -127,4 +127,4 @@ OK: …/annex_iv_metadata.json
 - [Audit Log](#/compliance/audit-log) — append-only event log; `compliance.artifacts_exported` (Article 11 + Annex IV) is the production-side counterpart to this verifier.
 - [Verify Audit](#/compliance/verify-audit) — companion verifier for the audit log.
 - [Verify GGUF](#/deployment/verify-gguf) — companion verifier on the deployment-integrity surface.
-- [`verify_annex_iv_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/verify_annex_iv_subcommand.md) — the reference doc with full flag table and library-symbol citations (GitHub source).
+- [`verify_annex_iv_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/verify_annex_iv_subcommand.md) — the reference doc with full flag table and library-symbol citations (GitHub source).
diff --git a/docs/usermanuals/en/compliance/audit-log.md b/docs/usermanuals/en/compliance/audit-log.md
index ca0b7a34..0e3295b1 100644
--- a/docs/usermanuals/en/compliance/audit-log.md
+++ b/docs/usermanuals/en/compliance/audit-log.md
@@ -18,7 +18,7 @@ One JSON object per line:
 {"ts":"2026-04-29T14:33:11Z","seq":4,"event":"pipeline.completed","exit_code":0,"prev_hash":"sha256:beef...","_hmac":"..."}
 ```
 
-(See the "Event types" table below and the [Audit Event Catalog on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md) for the full canonical list. Earlier drafts referenced `run_start` / `run_complete` / `data_audit_complete` / `training_epoch_complete` / `benchmark_complete` / `safety_eval_complete` / `auto_revert` — none of those names ship; no call site in `forgelm/` emits them.)
+(See the "Event types" table below and the [Audit Event Catalog on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md) for the full canonical list. Earlier drafts referenced `run_start` / `run_complete` / `data_audit_complete` / `training_epoch_complete` / `benchmark_complete` / `safety_eval_complete` / `auto_revert` — none of those names ship; no call site in `forgelm/` emits them.)
 
 Every entry has:
 - **`ts`** — ISO-8601 UTC timestamp.
@@ -46,7 +46,7 @@ Every entry has:
 | `cli.legacy_flag_invoked` | A deprecated CLI flag was used. |
 
 The full event catalog (with payload schema and emitting site) lives in the
-[Audit Event Catalog on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md).
+[Audit Event Catalog on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md).
 
 ## Append-only by design
 
diff --git a/docs/usermanuals/en/compliance/gdpr-erasure.md b/docs/usermanuals/en/compliance/gdpr-erasure.md
index 8b57b4cc..6cf43cb9 100644
--- a/docs/usermanuals/en/compliance/gdpr-erasure.md
+++ b/docs/usermanuals/en/compliance/gdpr-erasure.md
@@ -7,7 +7,7 @@ description: Honour Article 15 (right of access) and Article 17 (right to erasur
 
 ForgeLM ships sister subcommands for the two most-common GDPR data-subject rights: `forgelm purge` (Article 17 — right to erasure) and `forgelm reverse-pii` (Article 15 — right of access). They share a per-output-dir salt so a compliance reviewer can correlate erasures and access requests for the same data subject in a single tamper-evident audit chain — without the cleartext identifier ever leaving the operator's terminal.
 
-This page is the operator quick-reference. The deeper deployer-flow walkthrough lives in the [GDPR erasure deployer guide on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/gdpr_erasure.md); per-flag references are in the in-manual [CLI Reference](#/reference/cli) and the dedicated subcommand pages [`purge_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/purge_subcommand.md) + [`reverse_pii_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/reverse_pii_subcommand.md) on GitHub.
+This page is the operator quick-reference. The deeper deployer-flow walkthrough lives in the [GDPR erasure deployer guide on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/gdpr_erasure.md); per-flag references are in the in-manual [CLI Reference](#/reference/cli) and the dedicated subcommand pages [`purge_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/purge_subcommand.md) + [`reverse_pii_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/reverse_pii_subcommand.md) on GitHub.
 
 ## Two rights, one chain
 
@@ -37,7 +37,7 @@ forgelm purge --check-policy --config configs/run.yaml --output-dir ./outputs
 
 ### What gets recorded
 
-Six events ride the audit chain (see the [Audit Event Catalog on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)):
+Six events ride the audit chain (see the [Audit Event Catalog on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)):
 
 - `data.erasure_requested` — emitted FIRST, before any deletion.
 - `data.erasure_completed` — emitted LAST after the disk operation succeeded.
@@ -125,6 +125,6 @@ Codes 3 (`EXIT_EVAL_FAILURE`) and 4 (`EXIT_AWAITING_APPROVAL`) are not part of e
 
 - [Audit Log](#/compliance/audit-log) — where the `data.*` events are recorded.
 - [Human Oversight](#/compliance/human-oversight) — Article 14 sister gate that pairs with the GDPR rights for high-risk deployments.
-- [GDPR erasure deployer guide](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/gdpr_erasure.md) — full deployer-flow walkthrough (GitHub source).
-- [`purge_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/purge_subcommand.md) — `forgelm purge` per-flag reference (GitHub source).
-- [`reverse_pii_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/reverse_pii_subcommand.md) — `forgelm reverse-pii` per-flag reference (GitHub source).
+- [GDPR erasure deployer guide](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/gdpr_erasure.md) — full deployer-flow walkthrough (GitHub source).
+- [`purge_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/purge_subcommand.md) — `forgelm purge` per-flag reference (GitHub source).
+- [`reverse_pii_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/reverse_pii_subcommand.md) — `forgelm reverse-pii` per-flag reference (GitHub source).
diff --git a/docs/usermanuals/en/compliance/gdpr.md b/docs/usermanuals/en/compliance/gdpr.md
index 3ae9d698..983322cd 100644
--- a/docs/usermanuals/en/compliance/gdpr.md
+++ b/docs/usermanuals/en/compliance/gdpr.md
@@ -108,7 +108,7 @@ For high-risk processing, GDPR Art. 35 requires a DPIA. ForgeLM doesn't write yo
 - Mitigations applied → from `compliance.risk_assessment.mitigations`.
 - Residual risks → from `compliance.risk_assessment.residual_risks`.
 
-For DPIA work, pair the inputs above with the QMS [risk-treatment plan](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/risk_treatment_plan.md) and the [Statement of Applicability](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/statement_of_applicability.md) (GitHub QMS templates shipped with the toolkit). A dedicated DPIA template is on the roadmap; the risk-treatment plan covers the same ground for now.
+For DPIA work, pair the inputs above with the QMS [risk-treatment plan](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/risk_treatment_plan.md) and the [Statement of Applicability](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/statement_of_applicability.md) (GitHub QMS templates shipped with the toolkit). A dedicated DPIA template is on the roadmap; the risk-treatment plan covers the same ground for now.
 
 ## Configuration reference
 
diff --git a/docs/usermanuals/en/compliance/human-approval-gate.md b/docs/usermanuals/en/compliance/human-approval-gate.md
index 41746bdc..c9e36c40 100644
--- a/docs/usermanuals/en/compliance/human-approval-gate.md
+++ b/docs/usermanuals/en/compliance/human-approval-gate.md
@@ -7,7 +7,7 @@ description: Deployer-facing companion to Human Oversight — the `forgelm appro
 
 This page is the deployer-facing companion to [Human Oversight](#/compliance/human-oversight). The shorter Human Oversight page is the operator quick-reference; this page collects the wiring details — CI integration, segregation of duties, audit-evidence verification — that a deployer needs when standing up the gate end-to-end.
 
-For the full walkthrough, see the [human approval gate deployer guide on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/human_approval_gate.md). For per-flag references, see [`approve_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/approve_subcommand.md) and [`approvals_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/approvals_subcommand.md) on GitHub.
+For the full walkthrough, see the [human approval gate deployer guide on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/human_approval_gate.md). For per-flag references, see [`approve_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/approve_subcommand.md) and [`approvals_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/approvals_subcommand.md) on GitHub.
 
 ## When the gate fires
 
@@ -68,7 +68,7 @@ forgelm reject   <run_id> --output-dir <dir> --comment "..."  # discard the stag
 
 ## Segregation of duties (Article 14 + ISO A.5.3 + SOC 2 CC1.5)
 
-The approver's `FORGELM_OPERATOR` MUST differ from the trainer's. ForgeLM does not enforce this — it is a deployer-side IdP control — but the audit chain records both, so a violation is detectable post-hoc with the canonical `jq -rs` cookbook in the [`access_control.md` QMS template on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/access_control.md) §6:
+The approver's `FORGELM_OPERATOR` MUST differ from the trainer's. ForgeLM does not enforce this — it is a deployer-side IdP control — but the audit chain records both, so a violation is detectable post-hoc with the canonical `jq -rs` cookbook in the [`access_control.md` QMS template on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/access_control.md) §6:
 
 ```bash
 jq -rs '
@@ -87,7 +87,7 @@ Pattern: CI runners use a machine-readable identity (`gha:Acme/pipelines:trainin
 
 ## Audit events emitted
 
-Three events describe the gate's full lifecycle (see the [Audit Event Catalog on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)):
+Three events describe the gate's full lifecycle (see the [Audit Event Catalog on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)):
 
 | Event | Emitted by | When |
 |---|---|---|
@@ -149,7 +149,7 @@ jq -rs '
 
 - [Human Oversight](#/compliance/human-oversight) — operator quick-reference companion.
 - [Audit Log](#/compliance/audit-log) — where the `human_approval.*` events are recorded.
-- [Human approval gate deployer guide](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/human_approval_gate.md) — full deployer-flow walkthrough (GitHub source).
-- [`approve_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/approve_subcommand.md) — `approve` / `reject` per-flag reference (GitHub source).
-- [`approvals_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/approvals_subcommand.md) — `approvals` per-flag reference (GitHub source).
-- [`access_control.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/access_control.md) §6 — canonical segregation-of-duties cookbook (GitHub QMS template).
+- [Human approval gate deployer guide](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/human_approval_gate.md) — full deployer-flow walkthrough (GitHub source).
+- [`approve_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/approve_subcommand.md) — `approve` / `reject` per-flag reference (GitHub source).
+- [`approvals_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/approvals_subcommand.md) — `approvals` per-flag reference (GitHub source).
+- [`access_control.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/access_control.md) §6 — canonical segregation-of-duties cookbook (GitHub QMS template).
diff --git a/docs/usermanuals/en/compliance/overview.md b/docs/usermanuals/en/compliance/overview.md
index 32d48951..4d3cdc9e 100644
--- a/docs/usermanuals/en/compliance/overview.md
+++ b/docs/usermanuals/en/compliance/overview.md
@@ -62,7 +62,7 @@ There is **no** `compliance.annex_iv: true` knob — Annex IV emission is driven
 | **15** | Accuracy & robustness | Benchmark gates + safety eval + cybersecurity (PII / secrets at ingest). |
 | **16-17** | Conformity & QMS | Declaration scaffold + QMS SOPs shipped alongside the toolkit. |
 
-For the full mapping with code references, see the [Compliance summary on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/compliance_summary.md).
+For the full mapping with code references, see the [Compliance summary on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/compliance_summary.md).
 
 ## What ForgeLM doesn't claim
 
diff --git a/docs/usermanuals/en/compliance/verify-audit.md b/docs/usermanuals/en/compliance/verify-audit.md
index 31322d46..45d06675 100644
--- a/docs/usermanuals/en/compliance/verify-audit.md
+++ b/docs/usermanuals/en/compliance/verify-audit.md
@@ -128,4 +128,4 @@ Either way, exit code is `1`. Investigate before treating the log as evidence.
 - [Audit Log](#/compliance/audit-log) — operator-facing primer on the log this command verifies.
 - [Annex IV](#/compliance/annex-iv) — the technical-documentation artifact whose verifier (`forgelm verify-annex-iv`) shares this verifier's design pattern.
 - [Verify GGUF](#/deployment/verify-gguf) — companion verifier on the deployment-integrity surface.
-- [`audit_event_catalog.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md) — events that appear *inside* the verified log (GitHub source).
+- [`audit_event_catalog.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md) — events that appear *inside* the verified log (GitHub source).
diff --git a/docs/usermanuals/en/data/deduplication.md b/docs/usermanuals/en/data/deduplication.md
index 33419502..1010b173 100644
--- a/docs/usermanuals/en/data/deduplication.md
+++ b/docs/usermanuals/en/data/deduplication.md
@@ -78,7 +78,7 @@ MinHash trades small accuracy for big speed — typical recall is >95% of true d
 | `--dedup-method minhash` | Switch from the default simhash detector to MinHash LSH. Requires the `forgelm[ingestion-scale]` extra (datasketch). |
 | `--jaccard-threshold` | Jaccard similarity threshold (default 0.85). Ignored under simhash. |
 
-Permutation count and LSH banding are not user-tunable today — they are fixed at the library defaults that benchmark cleanly across the 50K-to-1M-row range. Track [Phase 13 roadmap on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md) for the planned `forgelm[ingestion-scale]` knobs to expose them.
+Permutation count and LSH banding are not user-tunable today — they are fixed at the library defaults that benchmark cleanly across the 50K-to-1M-row range. Track [Phase 13 roadmap on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md) for the planned `forgelm[ingestion-scale]` knobs to expose them.
 
 ## Streaming behaviour
 
@@ -109,7 +109,7 @@ When duplicates are within a single split, ForgeLM keeps the first occurrence. A
 :::
 
 :::warn
-**MinHash recall depends on the permutation count.** ForgeLM ships datasketch defaults (≥128 permutations) that keep recall above 95%. Manual override is on the [Phase 13 roadmap on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md) — until then, do not rely on a `--num-perm` flag (it does not exist).
+**MinHash recall depends on the permutation count.** ForgeLM ships datasketch defaults (≥128 permutations) that keep recall above 95%. Manual override is on the [Phase 13 roadmap on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md) — until then, do not rely on a `--num-perm` flag (it does not exist).
 :::
 
 :::tip
diff --git a/docs/usermanuals/en/data/pii-masking.md b/docs/usermanuals/en/data/pii-masking.md
index 6d1727b0..e7b9c5ac 100644
--- a/docs/usermanuals/en/data/pii-masking.md
+++ b/docs/usermanuals/en/data/pii-masking.md
@@ -62,7 +62,7 @@ The PII regexes are deliberately tuned for **low false-positive rate**. They pre
 
 1. False positives silently corrupt your data — replacing legitimate words with `[EMAIL_REDACTED]` ruins examples.
 2. The audit step catches what masking missed; you can decide per-row whether to fix or drop.
-3. Aggressive regexes have caused real-world ML pipeline outages (the Phase 11.5 incident is documented in the contributor [regex standard on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/regex.md)).
+3. Aggressive regexes have caused real-world ML pipeline outages (the Phase 11.5 incident is documented in the contributor [regex standard on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/regex.md)).
 
 If you need stricter detection — for instance, a high-stakes legal corpus — pair the masker with a manual review step. Don't push the regexes harder.
 
diff --git a/docs/usermanuals/en/deployment/chat.md b/docs/usermanuals/en/deployment/chat.md
index 6db6af2d..24e7906a 100644
--- a/docs/usermanuals/en/deployment/chat.md
+++ b/docs/usermanuals/en/deployment/chat.md
@@ -63,9 +63,9 @@ $ forgelm chat "Qwen/Qwen2.5-7B" --adapter ./checkpoints/run/
 
 ## Safety routing
 
-> Note: A built-in `--safety` flag on `forgelm chat` is planned for v0.6.0+ Pro CLI (see [Phase 13 roadmap on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)). Today the screen-every-turn behaviour ships via the YAML `safety:` block (set `safety: enabled: true` and bind it to the same chat session through your runner); the snippet below illustrates the planned `--safety` UX as preview output, NOT as a runnable v0.5.5 command.
+> Note: A built-in `--safety` flag on `forgelm chat` is planned for v0.6.0+ Pro CLI (see [Phase 13 roadmap on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)). The current release does **not** support per-turn safety screening in the chat REPL: `forgelm chat` has no `--safety` flag and loads no YAML config (verifiable in the chat subcommand parser, `forgelm/cli/_parser.py`). The `evaluation.safety.enabled: true` config block is read only by the training pipeline's auto-revert safety gate (`forgelm/trainer.py`) and the standalone `forgelm safety-eval` subcommand — never by the chat REPL. The snippet below previews the planned `--safety` UX; it is NOT a runnable command today.
 
-With `safety: enabled: true` in your YAML config (or under the planned v0.6.0+ `--safety on` flag, illustrated for preview only below), every prompt and response is screened by Llama Guard:
+Under the planned `--safety` flag (preview only — see the note above), every prompt and response would be screened by Llama Guard:
 
 ```text
 forgelm> [adversarial prompt]
@@ -107,7 +107,7 @@ Sessions are useful for:
 
 ## Comparing two models
 
-> Note: The `chat-compare` subcommand is planned for v0.6.0+ Pro CLI tier (see [Phase 13 roadmap on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)). Today the same comparison runs through `forgelm --benchmark-only` against each checkpoint and a downstream judge config; the snippet below previews the dedicated UX.
+> Note: The `chat-compare` subcommand — an interactive, side-by-side chat-prompt comparison with judge adjudication — is planned for v0.6.0+ Pro CLI tier (see [Phase 13 roadmap on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)). There is no equivalent today: `forgelm --benchmark-only` (see `forgelm/cli/_no_train_modes.py`) runs lm-evaluation-harness benchmarks on a **single** checkpoint at a time — it does not do side-by-side comparison or judge adjudication. To compare two checkpoints now, run `--benchmark-only` once per checkpoint, run the judge separately, and aggregate the results yourself. The snippet below previews the planned UX.
 
 ```shell
 $ forgelm chat-compare ./checkpoints/v1 ./checkpoints/v2 --prompts data/probes.jsonl
diff --git a/docs/usermanuals/en/deployment/model-merging.md b/docs/usermanuals/en/deployment/model-merging.md
index 1949e13a..71723df3 100644
--- a/docs/usermanuals/en/deployment/model-merging.md
+++ b/docs/usermanuals/en/deployment/model-merging.md
@@ -169,7 +169,7 @@ merge_adapters(
 :::
 
 :::tip
-For exploratory merging, generate a small grid of `(algorithm, parameters)` combinations and evaluate each. A `forgelm merge-sweep` helper that automates this remains **planned post-Phase 14** — Phase 14 itself shipped multi-stage SFT/DPO/GRPO pipeline chaining in `v0.7.0` (see the [Phase 14 completed-phases entry on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap/completed-phases.md#phase-14-multi-stage-pipeline-chains-v070)) but did not include a merge-sweep CLI; that helper waits for explicit operator demand. Until then, write a small shell loop that calls `forgelm` once per `(algorithm, parameters)` pair.
+For exploratory merging, generate a small grid of `(algorithm, parameters)` combinations and evaluate each. A `forgelm merge-sweep` helper that automates this remains **planned post-Phase 14** — Phase 14 itself shipped multi-stage SFT/DPO/GRPO pipeline chaining in `v0.7.0` (see the [Phase 14 completed-phases entry on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap/completed-phases.md#phase-14-multi-stage-pipeline-chains-v070)) but did not include a merge-sweep CLI; that helper waits for explicit operator demand. Until then, write a small shell loop that calls `forgelm` once per `(algorithm, parameters)` pair.
 :::
 
 ## See also
diff --git a/docs/usermanuals/en/deployment/verify-gguf.md b/docs/usermanuals/en/deployment/verify-gguf.md
index 798eef01..ec898cd5 100644
--- a/docs/usermanuals/en/deployment/verify-gguf.md
+++ b/docs/usermanuals/en/deployment/verify-gguf.md
@@ -156,4 +156,4 @@ Install with `pip install gguf` to add the metadata layer back. This matches the
 - [GGUF Export](#/deployment/gguf-export) — the production side that writes the sidecar this verifier consumes.
 - [Verify Audit](#/compliance/verify-audit) — companion verifier on the compliance surface.
 - [Verify Annex IV](#/compliance/annex-iv) — companion verifier for the technical-documentation artifact.
-- [`verify_gguf_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/verify_gguf_subcommand.md) — the reference doc with full flag table and library-symbol citations (GitHub source).
+- [`verify_gguf_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/verify_gguf_subcommand.md) — the reference doc with full flag table and library-symbol citations (GitHub source).
diff --git a/docs/usermanuals/en/evaluation/trend-tracking.md b/docs/usermanuals/en/evaluation/trend-tracking.md
index 69e614fa..5306e1dc 100644
--- a/docs/usermanuals/en/evaluation/trend-tracking.md
+++ b/docs/usermanuals/en/evaluation/trend-tracking.md
@@ -74,7 +74,7 @@ Commit this file. It's small (one row per run, JSON), and it's the only way to t
 
 ## Visualisation
 
-ForgeLM ships a CLI report. The dedicated `forgelm trend` subcommand is planned for v0.6.0+ Pro CLI tier (see the [Phase 13 roadmap on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)) — today the same data is queryable directly from the JSONL with `jq`. Today's working flow:
+ForgeLM ships a CLI report. The dedicated `forgelm trend` subcommand is planned for v0.6.0+ Pro CLI tier (see the [Phase 13 roadmap on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)) — today the same data is queryable directly from the JSONL with `jq`. Today's working flow:
 
 ```shell
 # Last 20 S5 (defamation) scores from the trend log:
diff --git a/docs/usermanuals/en/getting-started/installation.md b/docs/usermanuals/en/getting-started/installation.md
index 433aca4e..b94b1347 100644
--- a/docs/usermanuals/en/getting-started/installation.md
+++ b/docs/usermanuals/en/getting-started/installation.md
@@ -87,8 +87,8 @@ This is intentional — pulling DeepSpeed / bitsandbytes / Presidio / sentence-t
 If you'd rather not install Python dependencies on your host, the official Docker image bundles ForgeLM with all extras:
 
 ```shell
-$ docker pull ghcr.io/cemililik/forgelm:latest
-$ docker run --gpus all -v $PWD:/workspace ghcr.io/cemililik/forgelm:latest \
+$ docker pull ghcr.io/hodetech/forgelm:latest
+$ docker run --gpus all -v $PWD:/workspace ghcr.io/hodetech/forgelm:latest \
     forgelm --config /workspace/configs/run.yaml
 ```
 
diff --git a/docs/usermanuals/en/operations/docker.md b/docs/usermanuals/en/operations/docker.md
index f4dbe6de..9c546509 100644
--- a/docs/usermanuals/en/operations/docker.md
+++ b/docs/usermanuals/en/operations/docker.md
@@ -12,12 +12,12 @@ ForgeLM ships an official Dockerfile and `docker-compose.yml` for reproducible t
 Pull the official image:
 
 ```shell
-$ docker pull ghcr.io/cemililik/forgelm:latest
+$ docker pull ghcr.io/hodetech/forgelm:latest
 $ docker run --gpus all \
     -v $PWD:/workspace \
     -v $HOME/.cache/huggingface:/root/.cache/huggingface \
     -e HF_TOKEN \
-    ghcr.io/cemililik/forgelm:latest \
+    ghcr.io/hodetech/forgelm:latest \
     forgelm --config /workspace/configs/run.yaml
 ```
 
@@ -43,7 +43,7 @@ version: "3.9"
 
 services:
   trainer:
-    image: ghcr.io/cemililik/forgelm:latest
+    image: ghcr.io/hodetech/forgelm:latest
     deploy:
       resources:
         reservations:
@@ -81,7 +81,7 @@ $ docker compose up trainer
 If you need custom modifications:
 
 ```shell
-$ git clone https://github.com/cemililik/ForgeLM
+$ git clone https://github.com/HodeTech/ForgeLM
 $ cd ForgeLM
 $ docker build -t forgelm:custom -f Dockerfile .
 $ docker run --gpus all forgelm:custom forgelm --version
@@ -95,7 +95,7 @@ For air-gapped environments, build an image with everything pre-cached:
 
 ```dockerfile
 # airgap.Dockerfile
-FROM ghcr.io/cemililik/forgelm:latest
+FROM ghcr.io/hodetech/forgelm:latest
 
 # Pre-cache the base model
 RUN forgelm cache-models --model "Qwen/Qwen2.5-7B-Instruct"
diff --git a/docs/usermanuals/en/operations/experiment-tracking.md b/docs/usermanuals/en/operations/experiment-tracking.md
index 1700a86e..18149c9d 100644
--- a/docs/usermanuals/en/operations/experiment-tracking.md
+++ b/docs/usermanuals/en/operations/experiment-tracking.md
@@ -107,7 +107,7 @@ For very large checkpoints, prefer model registries (HuggingFace Hub) over W&B/M
 
 Each backend's UI handles comparison naturally — comparable runs share a `run_name` prefix, tags, and config hash. A built-in CLI summary is on the way:
 
-> Note: The `forgelm compare-runs` subcommand is planned for v0.6.0+ Pro CLI tier (see the [Phase 13 roadmap on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)). Today the same comparison runs through your tracking backend's UI (W&B / MLflow / Comet) or a small `jq` over each run's JSON envelope.
+> Note: The `forgelm compare-runs` subcommand is planned for v0.6.0+ Pro CLI tier (see the [Phase 13 roadmap on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)). Today the same comparison runs through your tracking backend's UI (W&B / MLflow / Comet) or a small `jq` over each run's JSON envelope.
 
 Today's working flow (W&B / MLflow / Comet UI is the canonical surface; below is the `jq` shortcut for ad-hoc CLI comparison):
 
diff --git a/docs/usermanuals/en/operations/gpu-cost.md b/docs/usermanuals/en/operations/gpu-cost.md
index adee3748..4c90574f 100644
--- a/docs/usermanuals/en/operations/gpu-cost.md
+++ b/docs/usermanuals/en/operations/gpu-cost.md
@@ -11,7 +11,7 @@ description: Auto-detect across 16 GPU profiles and track per-run cost against y
 > currently honoured by `forgelm/config.py`. Examples below that show
 > `cost_tracking:` fields are forward-looking placeholders — set hourly
 > rates manually until the YAML surface lands. The deferral is tracked in
-> the [risks-and-decisions roadmap on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap/risks-and-decisions.md).
+> the [risks-and-decisions roadmap on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap/risks-and-decisions.md).
 
 ForgeLM detects the GPU you're running on, looks up its profile (memory, compute, typical hourly rate), and tracks per-run cost. After every run, the audit log records exactly how much GPU time was used and what it cost.
 
diff --git a/docs/usermanuals/en/operations/iso-soc2-deployer.md b/docs/usermanuals/en/operations/iso-soc2-deployer.md
index e50fe623..ea5b62e3 100644
--- a/docs/usermanuals/en/operations/iso-soc2-deployer.md
+++ b/docs/usermanuals/en/operations/iso-soc2-deployer.md
@@ -34,23 +34,23 @@ The deep guide answers each with the exact `jq` / CLI command + the artefact it
 All of the following live alongside the toolkit on GitHub — they ship in the repository but are not part of this in-manual viewer.
 
 - The deep guide — full deployer cookbook, twelve-item setup checklist, common pitfalls:
-  [`iso_soc2_deployer_guide.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md)
+  [`iso_soc2_deployer_guide.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md)
 - Full ISO 27001:2022 Annex A control mapping × ForgeLM evidence:
-  [`iso27001_control_mapping.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/iso27001_control_mapping.md)
+  [`iso27001_control_mapping.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/iso27001_control_mapping.md)
 - Full SOC 2 Trust Services Criteria mapping:
-  [`soc2_trust_criteria_mapping.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/soc2_trust_criteria_mapping.md)
+  [`soc2_trust_criteria_mapping.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/soc2_trust_criteria_mapping.md)
 - Pre-populated 93-control Statement of Applicability matrix:
-  [`statement_of_applicability.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/statement_of_applicability.md)
+  [`statement_of_applicability.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/statement_of_applicability.md)
 - Pre-populated risk register:
-  [`risk_treatment_plan.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/risk_treatment_plan.md)
+  [`risk_treatment_plan.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/risk_treatment_plan.md)
 - Substrate-side encryption guidance:
-  [`encryption_at_rest.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/encryption_at_rest.md)
+  [`encryption_at_rest.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/encryption_at_rest.md)
 - Operator identity + secrets management:
-  [`access_control.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/access_control.md)
+  [`access_control.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/access_control.md)
 - Incident response runbook:
-  [`sop_incident_response.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/sop_incident_response.md)
+  [`sop_incident_response.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/sop_incident_response.md)
 - Change management runbook:
-  [`sop_change_management.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/sop_change_management.md)
+  [`sop_change_management.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/sop_change_management.md)
 
 ## See also
 
diff --git a/docs/usermanuals/en/operations/supply-chain.md b/docs/usermanuals/en/operations/supply-chain.md
index e56487b3..374929d4 100644
--- a/docs/usermanuals/en/operations/supply-chain.md
+++ b/docs/usermanuals/en/operations/supply-chain.md
@@ -85,11 +85,11 @@ ForgeLM does **not** ship a default project-level ignore list. The project's own
 ## Where to read more
 
 - The full reference (severity policy, suppression syntax, related ISO/SOC 2 controls):
-  [`supply_chain_security.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/supply_chain_security.md) (GitHub source).
+  [`supply_chain_security.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/supply_chain_security.md) (GitHub source).
 - The deployer audit cookbook (Q4 walks the SBOM, Q5 walks access controls, Q7 walks incident response):
-  [`iso_soc2_deployer_guide.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md) (GitHub source).
+  [`iso_soc2_deployer_guide.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md) (GitHub source).
 - The SBOM emitter source (pure stdlib, zero deps):
-  [`tools/generate_sbom.py`](https://github.com/cemililik/ForgeLM/blob/main/tools/generate_sbom.py) (GitHub source).
+  [`tools/generate_sbom.py`](https://github.com/HodeTech/ForgeLM/blob/main/tools/generate_sbom.py) (GitHub source).
 
 ## See also
 
diff --git a/docs/usermanuals/en/operations/troubleshooting.md b/docs/usermanuals/en/operations/troubleshooting.md
index 93280835..ab7fa342 100644
--- a/docs/usermanuals/en/operations/troubleshooting.md
+++ b/docs/usermanuals/en/operations/troubleshooting.md
@@ -172,7 +172,7 @@ If `forgelm doctor` says everything's fine but the problem persists, gather:
 3. Your `config.yaml` (with secrets redacted).
 4. Output of `forgelm doctor`.
 
-Open an issue: <https://github.com/cemililik/ForgeLM/issues>. The maintainer team triages within 48 hours.
+Open an issue: <https://github.com/HodeTech/ForgeLM/issues>. The maintainer team triages within 48 hours.
 
 ## See also
 
diff --git a/docs/usermanuals/en/operations/webhooks.md b/docs/usermanuals/en/operations/webhooks.md
index 819a4d98..68de491d 100644
--- a/docs/usermanuals/en/operations/webhooks.md
+++ b/docs/usermanuals/en/operations/webhooks.md
@@ -33,7 +33,7 @@ $ forgelm --config configs/run.yaml
 
 ForgeLM emits exactly **five** webhook events. The table below is the
 canonical surface mirrored in the
-[Audit Event Catalog on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md):
+[Audit Event Catalog on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md):
 
 | Event | When fired | Gated by |
 |---|---|---|
@@ -59,7 +59,7 @@ provider-specific templates:
 ```
 
 Payload keys vary by event; the full per-event field list is in the
-[Audit Event Catalog on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)
+[Audit Event Catalog on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)
 under the *Webhook lifecycle events* table.
 
 ## Slack / Teams / Discord ingestion
diff --git a/docs/usermanuals/en/reference/configuration.md b/docs/usermanuals/en/reference/configuration.md
index 60b0f959..22e7eba5 100644
--- a/docs/usermanuals/en/reference/configuration.md
+++ b/docs/usermanuals/en/reference/configuration.md
@@ -302,7 +302,7 @@ auth:
 
 There is no `deployment:` top-level YAML key in v0.5.5 — `ForgeConfig` rejects unknown keys (`extra="forbid"`), so adding one to your training config raises `ConfigError` at load time. Deployment knobs are exposed as `forgelm deploy` CLI flags instead. The live target choices are `--target {ollama,vllm,tgi,hf-endpoints}`; see the [Deploy targets page](#/deployment/deploy-targets) and the [CLI reference](#/reference/cli) for the full surface.
 
-> **Planned for v0.6.0+:** A YAML-backed `deployment:` section is on the [Phase 14 pipeline-chains roadmap on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md) (deferred from earlier v0.5.x placeholders). Until then, treat any "deployment:" YAML you find in third-party templates as informational; only the `forgelm deploy` flags are authoritative.
+> **Planned for v0.6.0+:** A YAML-backed `deployment:` section is on the [Phase 14 pipeline-chains roadmap on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md) (deferred from earlier v0.5.x placeholders). Until then, treat any "deployment:" YAML you find in third-party templates as informational; only the `forgelm deploy` flags are authoritative.
 
 ## See also
 
diff --git a/docs/usermanuals/en/reference/exit-codes.md b/docs/usermanuals/en/reference/exit-codes.md
index a653b494..3f4a5e1b 100644
--- a/docs/usermanuals/en/reference/exit-codes.md
+++ b/docs/usermanuals/en/reference/exit-codes.md
@@ -18,7 +18,7 @@ ForgeLM's exit codes are a public contract. CI/CD pipelines, schedulers, and das
 | **4** | `EXIT_AWAITING_APPROVAL` | `evaluation.require_human_approval: true` blocking. | Hold pipeline; trigger reviewer |
 | **5** | `EXIT_WIZARD_CANCELLED` | `forgelm --wizard` exited without producing a YAML — Ctrl-C, non-tty stdin refusal, or operator declined to save. Distinct from `EXIT_SUCCESS` so CI can tell "wizard finished" from "wizard never wrote anything". | Treat as no-op; surface message; do NOT continue with stale config |
 
-These six integers are the entire public contract — see [`forgelm/cli/_exit_codes.py`](https://github.com/cemililik/ForgeLM/blob/main/forgelm/cli/_exit_codes.py) for the canonical definition. Any other non-zero value (including signal-derived 128+N codes) is clamped to `EXIT_TRAINING_ERROR` (2) before the process exits.
+These six integers are the entire public contract — see [`forgelm/cli/_exit_codes.py`](https://github.com/HodeTech/ForgeLM/blob/main/forgelm/cli/_exit_codes.py) for the canonical definition. Any other non-zero value (including signal-derived 128+N codes) is clamped to `EXIT_TRAINING_ERROR` (2) before the process exits.
 
 ## Mapping to CI patterns
 
diff --git a/docs/usermanuals/en/reference/json-output.md b/docs/usermanuals/en/reference/json-output.md
index c9473433..a72704b2 100644
--- a/docs/usermanuals/en/reference/json-output.md
+++ b/docs/usermanuals/en/reference/json-output.md
@@ -5,7 +5,7 @@ description: The locked --output-format json envelope shape for every forgelm su
 
 # JSON output schemas
 
-Every `forgelm` subcommand that supports `--output-format json` produces a stable JSON envelope on stdout. Field names + nesting are part of the public CLI contract per the [release standard on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/release.md): renaming a key is a MAJOR-version break.
+Every `forgelm` subcommand that supports `--output-format json` produces a stable JSON envelope on stdout. Field names + nesting are part of the public CLI contract per the [release standard on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/release.md): renaming a key is a MAJOR-version break.
 
 This page is the canonical reference. CI/CD pipelines that parse `forgelm` output should pin against the shapes documented here.
 
@@ -13,7 +13,7 @@ This page is the canonical reference. CI/CD pipelines that parse `forgelm` outpu
 
 - **stdout vs stderr.** The JSON envelope goes to **stdout**. Human-friendly logs (info / warning / error) go to **stderr**. Pipe `forgelm ... --output-format json | jq .` and read your operator-facing messages from `2>` separately.
 - **Top-level wrapper.** Every envelope starts with `"success": true | false`. Consumers can branch on this single key before parsing the rest.
-- **Error envelope.** When `success: false`, the envelope carries `"error": "<message>"` (string). Optional richer fields (`exit_code`, `error_type`, `details`) MAY be present per the [error-handling standard on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/error-handling.md). Consumers that need certainty on these fields should also check the process exit code via `$?`.
+- **Error envelope.** When `success: false`, the envelope carries `"error": "<message>"` (string). Optional richer fields (`exit_code`, `error_type`, `details`) MAY be present per the [error-handling standard on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/error-handling.md). Consumers that need certainty on these fields should also check the process exit code via `$?`.
 - **Exit codes.** See [Exit Codes](#/reference/exit-codes). The envelope is consistent with the exit code: `success: true` ⟺ exit `0`; `success: false` ⟺ non-zero exit.
 
 ## `forgelm doctor`
@@ -525,10 +525,10 @@ A new subcommand that supports `--output-format json` MUST land with:
 2. A test in `tests/test_json_envelope_contract.py` (or a per-subcommand test file) that pins the exact set of top-level keys.
 3. The per-collection key follows the convention "results live under a key named after the subcommand's primary noun" (so `doctor` → `checks`, `approvals --pending` → `pending`, etc.).
 
-Renaming a key after merge is a MAJOR-version bump per the [release standard on GitHub](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/release.md).
+Renaming a key after merge is a MAJOR-version bump per the [release standard on GitHub](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/release.md).
 
 ## See also
 
 - [Exit Codes](#/reference/exit-codes) — the contract `success: bool` aligns with.
-- [`error-handling.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/error-handling.md) — the error envelope contract (GitHub source).
-- [`release.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/release.md) — when JSON renames count as breaking (GitHub source).
+- [`error-handling.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/error-handling.md) — the error envelope contract (GitHub source).
+- [`release.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/release.md) — when JSON renames count as breaking (GitHub source).
diff --git a/docs/usermanuals/en/reference/library-api.md b/docs/usermanuals/en/reference/library-api.md
index 1e39e765..0012fe66 100644
--- a/docs/usermanuals/en/reference/library-api.md
+++ b/docs/usermanuals/en/reference/library-api.md
@@ -43,11 +43,11 @@ assert "torch" not in sys.modules     # pinned by tests/test_library_api.py
 ## Where to read more
 
 - The complete reference, with every signature and worked examples, ships with the toolkit on GitHub:
-  [`library_api_reference.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/library_api_reference.md).
+  [`library_api_reference.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/library_api_reference.md).
 - The deep guide, with three end-to-end pipeline patterns and common pitfalls:
-  [`library_api.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/library_api.md) on GitHub.
+  [`library_api.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/library_api.md) on GitHub.
 - The Phase 18 design rationale (stability tiers, type contract, deprecation cadence):
-  [`library_api.md` design note](https://github.com/cemililik/ForgeLM/blob/main/docs/design/library_api.md) on GitHub.
+  [`library_api.md` design note](https://github.com/HodeTech/ForgeLM/blob/main/docs/design/library_api.md) on GitHub.
 
 ## See also
 
diff --git a/docs/usermanuals/en/reference/performance.md b/docs/usermanuals/en/reference/performance.md
index bbb43c81..b53bc229 100644
--- a/docs/usermanuals/en/reference/performance.md
+++ b/docs/usermanuals/en/reference/performance.md
@@ -36,10 +36,10 @@ Three orthogonal tools to fit a model that otherwise wouldn't. They're for **fit
 ## Where to read more
 
 - The deep guide with VRAM-vs-throughput tables, when to use each strategy, and common pitfalls:
-  [`performance.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/performance.md) on GitHub.
+  [`performance.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/performance.md) on GitHub.
 - The full configuration reference (every knob, every default) — also available in this manual under [Configuration](#/reference/configuration).
 - The lazy-import contributor standard the project enforces:
-  [`coding.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/coding.md) on GitHub.
+  [`coding.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/coding.md) on GitHub.
 
 ## See also
 
diff --git a/docs/usermanuals/en/reference/yaml-templates.md b/docs/usermanuals/en/reference/yaml-templates.md
index 9aa61529..06c84418 100644
--- a/docs/usermanuals/en/reference/yaml-templates.md
+++ b/docs/usermanuals/en/reference/yaml-templates.md
@@ -171,7 +171,7 @@ training:
 
 ## Field reference
 
-The canonical schema lives in [`forgelm/config.py`](https://github.com/cemililik/ForgeLM/blob/main/forgelm/config.py)
+The canonical schema lives in [`forgelm/config.py`](https://github.com/HodeTech/ForgeLM/blob/main/forgelm/config.py)
 under the Pydantic models `ForgeConfig`, `ModelConfig`, `LoraConfig`,
 `TrainingConfig`, `DataConfig`, `EvaluationConfig`, `BenchmarkConfig`,
 `SafetyConfig`, `JudgeConfig`, `ComplianceMetadataConfig`,
diff --git a/docs/usermanuals/tr/compliance/annex-iv.md b/docs/usermanuals/tr/compliance/annex-iv.md
index 7678b87e..d0f2bc62 100644
--- a/docs/usermanuals/tr/compliance/annex-iv.md
+++ b/docs/usermanuals/tr/compliance/annex-iv.md
@@ -127,4 +127,4 @@ OK: …/annex_iv_metadata.json
 - [Audit Log](#/compliance/audit-log) — append-only event log; `compliance.artifacts_exported` (Madde 11 + Annex IV) bu doğrulayıcının üretici tarafındaki muadilidir.
 - [Audit Log Doğrulama](#/compliance/verify-audit) — audit log için kardeş doğrulayıcı.
 - [GGUF Doğrulama](#/deployment/verify-gguf) — deployment-bütünlük yüzeyindeki kardeş doğrulayıcı.
-- [`verify_annex_iv_subcommand.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/verify_annex_iv_subcommand.md) — tam bayrak tablosu ve kütüphane-sembol atıfları içeren referans doc (GitHub kaynağı).
+- [`verify_annex_iv_subcommand.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/verify_annex_iv_subcommand.md) — tam bayrak tablosu ve kütüphane-sembol atıfları içeren referans doc (GitHub kaynağı).
diff --git a/docs/usermanuals/tr/compliance/audit-log.md b/docs/usermanuals/tr/compliance/audit-log.md
index 0926eaab..dea9f181 100644
--- a/docs/usermanuals/tr/compliance/audit-log.md
+++ b/docs/usermanuals/tr/compliance/audit-log.md
@@ -18,7 +18,7 @@ Satır başına bir JSON nesnesi:
 {"ts":"2026-04-29T14:33:11Z","seq":4,"event":"pipeline.completed","exit_code":0,"prev_hash":"sha256:beef...","_hmac":"..."}
 ```
 
-(Tam canonical olay listesi için aşağıdaki "Olay tipleri" tablosuna ve [GitHub'daki Audit Event Kataloğu](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)'na bakın. Eski draft'larda görünen `run_start` / `run_complete` / `data_audit_complete` / `training_epoch_complete` / `benchmark_complete` / `safety_eval_complete` / `auto_revert` adları ship olmadı — `forgelm/` içinde emit eden hiçbir call site yok.)
+(Tam canonical olay listesi için aşağıdaki "Olay tipleri" tablosuna ve [GitHub'daki Audit Event Kataloğu](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)'na bakın. Eski draft'larda görünen `run_start` / `run_complete` / `data_audit_complete` / `training_epoch_complete` / `benchmark_complete` / `safety_eval_complete` / `auto_revert` adları ship olmadı — `forgelm/` içinde emit eden hiçbir call site yok.)
 
 Her kayıtta:
 - **`ts`** — ISO-8601 UTC zaman damgası.
@@ -46,7 +46,7 @@ Her kayıtta:
 | `cli.legacy_flag_invoked` | Deprecated bir CLI flag'i kullanıldığında. |
 
 Tam event kataloğu (payload şeması ve emit yeri ile)
-[GitHub'daki Audit Event Kataloğu](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md) altındadır.
+[GitHub'daki Audit Event Kataloğu](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md) altındadır.
 
 ## Tasarım gereği append-only
 
diff --git a/docs/usermanuals/tr/compliance/gdpr-erasure.md b/docs/usermanuals/tr/compliance/gdpr-erasure.md
index 36575b0f..f430e5c0 100644
--- a/docs/usermanuals/tr/compliance/gdpr-erasure.md
+++ b/docs/usermanuals/tr/compliance/gdpr-erasure.md
@@ -7,7 +7,7 @@ description: `forgelm purge` ve `forgelm reverse-pii` subcommand'ları ile Madde
 
 ForgeLM, en yaygın iki GDPR veri-sahibi hakkı için kardeş subcommand'lar ship eder: `forgelm purge` (Madde 17 — silinme hakkı) ve `forgelm reverse-pii` (Madde 15 — erişim hakkı). Per-output-dir salt'ı paylaşırlar; böylece compliance reviewer aynı veri sahibi için silme ve erişim taleplerini tek bir tamper-evident audit zincirinde — cleartext identifier operatör terminalinden hiç çıkmadan — korele edebilir.
 
-Bu sayfa operatör hızlı-referansıdır. Daha derin deployer akışı [GitHub'daki GDPR silme deployer kılavuzunda](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/gdpr_erasure-tr.md) bulunur; flag-başına referanslar manuel içindeki [CLI Referansı](#/reference/cli) ve GitHub'daki özel subcommand sayfaları [`purge_subcommand-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/purge_subcommand-tr.md) + [`reverse_pii_subcommand-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/reverse_pii_subcommand-tr.md) sayfalarındadır.
+Bu sayfa operatör hızlı-referansıdır. Daha derin deployer akışı [GitHub'daki GDPR silme deployer kılavuzunda](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/gdpr_erasure-tr.md) bulunur; flag-başına referanslar manuel içindeki [CLI Referansı](#/reference/cli) ve GitHub'daki özel subcommand sayfaları [`purge_subcommand-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/purge_subcommand-tr.md) + [`reverse_pii_subcommand-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/reverse_pii_subcommand-tr.md) sayfalarındadır.
 
 ## İki hak, tek zincir
 
@@ -37,7 +37,7 @@ forgelm purge --check-policy --config configs/run.yaml --output-dir ./outputs
 
 ### Neyi kaydeder
 
-Audit zincirine altı event yazılır (bkz. [GitHub'daki Audit Event Kataloğu](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog-tr.md)):
+Audit zincirine altı event yazılır (bkz. [GitHub'daki Audit Event Kataloğu](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog-tr.md)):
 
 - `data.erasure_requested` — herhangi bir silmeden ÖNCE, ilk yayılır.
 - `data.erasure_completed` — disk operasyonu başarılı sonra son yayılır.
@@ -125,6 +125,6 @@ Kod 3 (`EXIT_EVAL_FAILURE`) ve 4 (`EXIT_AWAITING_APPROVAL`) iki subcommand'ın d
 
 - [Audit Log](#/compliance/audit-log) — `data.*` event'lerinin kaydedildiği yer.
 - [İnsan Gözetimi](#/compliance/human-oversight) — yüksek-riskli deployment'lar için GDPR haklarıyla eşleşen Madde 14 kardeş kapısı.
-- [GDPR silme deployer kılavuzu](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/gdpr_erasure-tr.md) — tam deployer akışı (GitHub kaynağı).
-- [`purge_subcommand-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/purge_subcommand-tr.md) — `forgelm purge` flag-başına referans (GitHub kaynağı).
-- [`reverse_pii_subcommand-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/reverse_pii_subcommand-tr.md) — `forgelm reverse-pii` flag-başına referans (GitHub kaynağı).
+- [GDPR silme deployer kılavuzu](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/gdpr_erasure-tr.md) — tam deployer akışı (GitHub kaynağı).
+- [`purge_subcommand-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/purge_subcommand-tr.md) — `forgelm purge` flag-başına referans (GitHub kaynağı).
+- [`reverse_pii_subcommand-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/reverse_pii_subcommand-tr.md) — `forgelm reverse-pii` flag-başına referans (GitHub kaynağı).
diff --git a/docs/usermanuals/tr/compliance/gdpr.md b/docs/usermanuals/tr/compliance/gdpr.md
index 27211266..57be3f7a 100644
--- a/docs/usermanuals/tr/compliance/gdpr.md
+++ b/docs/usermanuals/tr/compliance/gdpr.md
@@ -108,7 +108,7 @@ Yüksek-riskli işleme için GDPR Md. 35 DPIA gerektirir. ForgeLM DPIA'nızı ya
 - Uygulanan azaltıcılar → `compliance.risk_assessment.mitigations`'dan.
 - Kalıntı riskler → `compliance.risk_assessment.residual_risks`'tan.
 
-DPIA çalışması için yukarıdaki girdileri [GitHub'daki QMS risk tedavi planı](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/risk_treatment_plan-tr.md) ve [Uygulanabilirlik Beyanı](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/statement_of_applicability-tr.md) ile eşleştirin (toolkit ile gelen GitHub QMS şablonları). Adanmış bir DPIA şablonu yol haritasındadır; şimdilik risk tedavi planı aynı zemini kapsıyor.
+DPIA çalışması için yukarıdaki girdileri [GitHub'daki QMS risk tedavi planı](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/risk_treatment_plan-tr.md) ve [Uygulanabilirlik Beyanı](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/statement_of_applicability-tr.md) ile eşleştirin (toolkit ile gelen GitHub QMS şablonları). Adanmış bir DPIA şablonu yol haritasındadır; şimdilik risk tedavi planı aynı zemini kapsıyor.
 
 ## Konfigürasyon referansı
 
diff --git a/docs/usermanuals/tr/compliance/human-approval-gate.md b/docs/usermanuals/tr/compliance/human-approval-gate.md
index 64a46ed8..80f853b4 100644
--- a/docs/usermanuals/tr/compliance/human-approval-gate.md
+++ b/docs/usermanuals/tr/compliance/human-approval-gate.md
@@ -7,7 +7,7 @@ description: İnsan Gözetimi'nin deployer-yüzlü tamamlayıcısı — Madde 14
 
 Bu sayfa [İnsan Gözetimi](#/compliance/human-oversight)'nin deployer-yüzlü tamamlayıcısıdır. Daha kısa olan İnsan Gözetimi sayfası operatör hızlı-referansıdır; bu sayfa kapıyı uçtan uca ayağa kaldırırken bir deployer'ın ihtiyaç duyduğu wiring detaylarını — CI entegrasyonu, görev ayrılığı, audit-kanıt doğrulama — toplar.
 
-Tam walkthrough için bkz. [GitHub'daki insan onay kapısı deployer kılavuzu](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/human_approval_gate-tr.md). Flag-başına referanslar için bkz. GitHub'daki [`approve_subcommand-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/approve_subcommand-tr.md) ve [`approvals_subcommand-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/approvals_subcommand-tr.md).
+Tam walkthrough için bkz. [GitHub'daki insan onay kapısı deployer kılavuzu](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/human_approval_gate-tr.md). Flag-başına referanslar için bkz. GitHub'daki [`approve_subcommand-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/approve_subcommand-tr.md) ve [`approvals_subcommand-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/approvals_subcommand-tr.md).
 
 ## Kapı ne zaman ateşlenir
 
@@ -68,7 +68,7 @@ forgelm reject   <run_id> --output-dir <dir> --comment "..."  # staged modeli at
 
 ## Görev ayrılığı (Madde 14 + ISO A.5.3 + SOC 2 CC1.5)
 
-Onaylayanın `FORGELM_OPERATOR`'ı trainer'ınkinden FARKLI OLMALIDIR. ForgeLM bunu zorunlu kılmaz — bu deployer-tarafı IdP kontrolüdür — ancak audit zinciri her ikisini kaydeder; ihlal [GitHub'daki `access_control.md` QMS şablonunun](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/access_control.md) §6'sındaki kanonik `jq -rs` cookbook'uyla post-hoc tespit edilebilir:
+Onaylayanın `FORGELM_OPERATOR`'ı trainer'ınkinden FARKLI OLMALIDIR. ForgeLM bunu zorunlu kılmaz — bu deployer-tarafı IdP kontrolüdür — ancak audit zinciri her ikisini kaydeder; ihlal [GitHub'daki `access_control.md` QMS şablonunun](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/access_control.md) §6'sındaki kanonik `jq -rs` cookbook'uyla post-hoc tespit edilebilir:
 
 ```bash
 jq -rs '
@@ -87,7 +87,7 @@ Desen: CI runner'ları makine-okunabilir kimlik kullanır (`gha:Acme/pipelines:t
 
 ## Yayılan audit event'leri
 
-Üç event kapının tam yaşam döngüsünü tarif eder (bkz. [GitHub'daki Audit Event Kataloğu](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)):
+Üç event kapının tam yaşam döngüsünü tarif eder (bkz. [GitHub'daki Audit Event Kataloğu](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)):
 
 | Event | Kim yayar | Ne zaman |
 |---|---|---|
@@ -149,7 +149,7 @@ jq -rs '
 
 - [İnsan Gözetimi](#/compliance/human-oversight) — operatör hızlı-referans tamamlayıcısı.
 - [Audit Log](#/compliance/audit-log) — `human_approval.*` event'lerinin kaydedildiği yer.
-- [İnsan onay kapısı deployer kılavuzu](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/human_approval_gate-tr.md) — tam deployer akışı (GitHub kaynağı).
-- [`approve_subcommand-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/approve_subcommand-tr.md) — `approve` / `reject` flag-başına referans (GitHub kaynağı).
-- [`approvals_subcommand-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/approvals_subcommand-tr.md) — `approvals` flag-başına referans (GitHub kaynağı).
-- [`access_control.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/access_control.md) §6 — kanonik segregation-of-duties cookbook (GitHub QMS şablonu).
+- [İnsan onay kapısı deployer kılavuzu](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/human_approval_gate-tr.md) — tam deployer akışı (GitHub kaynağı).
+- [`approve_subcommand-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/approve_subcommand-tr.md) — `approve` / `reject` flag-başına referans (GitHub kaynağı).
+- [`approvals_subcommand-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/approvals_subcommand-tr.md) — `approvals` flag-başına referans (GitHub kaynağı).
+- [`access_control.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/access_control.md) §6 — kanonik segregation-of-duties cookbook (GitHub QMS şablonu).
diff --git a/docs/usermanuals/tr/compliance/overview.md b/docs/usermanuals/tr/compliance/overview.md
index 8b5124c3..3ee011c0 100644
--- a/docs/usermanuals/tr/compliance/overview.md
+++ b/docs/usermanuals/tr/compliance/overview.md
@@ -62,7 +62,7 @@ checkpoints/run/
 | **15** | Doğruluk ve sağlamlık | Benchmark kapıları + güvenlik eval + cybersec (ingest'te PII / sırlar). |
 | **16-17** | Uygunluk ve QMS | Beyan iskeleti + toolkit ile birlikte gelen QMS SOP'ları. |
 
-Tam kod referansları için [GitHub'daki Compliance özeti](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/compliance_summary.md).
+Tam kod referansları için [GitHub'daki Compliance özeti](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/compliance_summary.md).
 
 ## ForgeLM'in iddia *etmediği*
 
diff --git a/docs/usermanuals/tr/compliance/verify-audit.md b/docs/usermanuals/tr/compliance/verify-audit.md
index b5e2fb92..dd7ccd61 100644
--- a/docs/usermanuals/tr/compliance/verify-audit.md
+++ b/docs/usermanuals/tr/compliance/verify-audit.md
@@ -128,4 +128,4 @@ Her iki durumda da çıkış kodu `1`'dir. Log'u kanıt saymadan önce inceleyin
 - [Audit Log](#/compliance/audit-log) — bu komutun doğruladığı log'a dair operatör-odaklı kılavuz.
 - [Annex IV](#/compliance/annex-iv) — doğrulayıcısı (`forgelm verify-annex-iv`) bu komutun tasarım desenini paylaşan teknik dokümantasyon artifact'ı.
 - [GGUF Doğrulama](#/deployment/verify-gguf) — deployment-bütünlük yüzeyindeki kardeş doğrulayıcı.
-- [`audit_event_catalog.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md) — doğrulanan log'un *içinde* görünen event'ler (GitHub kaynağı).
+- [`audit_event_catalog.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md) — doğrulanan log'un *içinde* görünen event'ler (GitHub kaynağı).
diff --git a/docs/usermanuals/tr/data/deduplication.md b/docs/usermanuals/tr/data/deduplication.md
index 9965bf5e..e9d3345a 100644
--- a/docs/usermanuals/tr/data/deduplication.md
+++ b/docs/usermanuals/tr/data/deduplication.md
@@ -78,7 +78,7 @@ MinHash büyük hız için küçük doğruluk ödünleşir — milyon-satır dat
 | `--dedup-method minhash` | Varsayılan simhash detector'dan MinHash LSH'e geçin. `forgelm[ingestion-scale]` ekstrasını gerektirir (datasketch). |
 | `--jaccard-threshold` | Jaccard benzerlik eşiği (varsayılan 0.85). Simhash altında yok sayılır. |
 
-Permutasyon sayısı ve LSH banding bugün kullanıcı tarafından ayarlanabilir değil — 50K-1M satır aralığında temiz benchmark veren kütüphane varsayılanlarına sabit. Bunları açan planlanan `forgelm[ingestion-scale]` knob'ları için [GitHub'daki Phase 13 yol haritası](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)'na bakın.
+Permutasyon sayısı ve LSH banding bugün kullanıcı tarafından ayarlanabilir değil — 50K-1M satır aralığında temiz benchmark veren kütüphane varsayılanlarına sabit. Bunları açan planlanan `forgelm[ingestion-scale]` knob'ları için [GitHub'daki Phase 13 yol haritası](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)'na bakın.
 
 ## Streaming davranış
 
@@ -109,7 +109,7 @@ Tekrarlar tek split içindeyken ForgeLM ilk tekrarı tutar. Split arasında vars
 :::
 
 :::warn
-**MinHash recall'ı permutasyon sayısına bağlıdır.** ForgeLM, recall'ı %95'in üstünde tutan datasketch varsayılanlarını yayınlar (≥128 permutasyon). Manuel override [GitHub'daki Phase 13 yol haritasında](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md) — o zamana kadar `--num-perm` bayrağına güvenmeyin (mevcut değil).
+**MinHash recall'ı permutasyon sayısına bağlıdır.** ForgeLM, recall'ı %95'in üstünde tutan datasketch varsayılanlarını yayınlar (≥128 permutasyon). Manuel override [GitHub'daki Phase 13 yol haritasında](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md) — o zamana kadar `--num-perm` bayrağına güvenmeyin (mevcut değil).
 :::
 
 :::tip
diff --git a/docs/usermanuals/tr/data/pii-masking.md b/docs/usermanuals/tr/data/pii-masking.md
index 959e0dfa..af6e95f3 100644
--- a/docs/usermanuals/tr/data/pii-masking.md
+++ b/docs/usermanuals/tr/data/pii-masking.md
@@ -62,7 +62,7 @@ PII regex'leri bilinçli olarak **düşük false-positive oran** için ayarlanı
 
 1. False positive sessizce verinizi bozar — gerçek kelimeleri `[EMAIL_REDACTED]` ile değiştirmek örnekleri mahveder.
 2. Audit aşaması maskelemenin kaçırdığını yakalar; satır başına düzeltme veya düşürme kararı sizde.
-3. Agresif regex'ler gerçek-dünya ML pipeline kesintilerine yol açtı (Phase 11.5 olayı [GitHub'daki katkıda bulunan regex standardında](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/regex.md) belgelenmiştir).
+3. Agresif regex'ler gerçek-dünya ML pipeline kesintilerine yol açtı (Phase 11.5 olayı [GitHub'daki katkıda bulunan regex standardında](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/regex.md) belgelenmiştir).
 
 Daha katı tespit gerekirse — örneğin yüksek-stake bir hukuk corpus'u — maskeleyiciyi manuel inceleme adımıyla birleştirin. Regex'leri zorlamayın.
 
diff --git a/docs/usermanuals/tr/deployment/chat.md b/docs/usermanuals/tr/deployment/chat.md
index 8f8ee858..459698c8 100644
--- a/docs/usermanuals/tr/deployment/chat.md
+++ b/docs/usermanuals/tr/deployment/chat.md
@@ -63,9 +63,9 @@ $ forgelm chat "Qwen/Qwen2.5-7B" --adapter ./checkpoints/run/
 
 ## Güvenlik routing'i
 
-> Not: `forgelm chat` üzerinde yerleşik `--safety` bayrağı v0.6.0+ Pro CLI için planlanmıştır ([GitHub'daki Phase 13 yol haritası](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)). Bugün her-tur tarama davranışı yalnızca **YAML pipeline** (`safety:` bloğu) üzerinden yayınlanmıştır — chat REPL'i bu config'i okur ve her prompt + yanıtı Llama Guard'a yönlendirir. Aşağıdaki bayraklı çağrı planlanan UX'in önizlemesi olup BUGÜN runnable DEĞİLDİR.
+> Not: `forgelm chat` üzerinde yerleşik `--safety` bayrağı v0.6.0+ Pro CLI için planlanmıştır ([GitHub'daki Phase 13 yol haritası](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)). Mevcut sürüm chat REPL'inde her-tur güvenlik taramasını **desteklemez**: `forgelm chat`'in `--safety` bayrağı yoktur ve hiçbir YAML config okumaz (chat subcommand parser'ında doğrulanabilir, `forgelm/cli/_parser.py`). `evaluation.safety.enabled: true` config bloğu yalnızca eğitim pipeline'ının auto-revert güvenlik kapısı (`forgelm/trainer.py`) ve bağımsız `forgelm safety-eval` subcommand'ı tarafından okunur — chat REPL'i tarafından asla. Aşağıdaki snippet planlanan `--safety` UX'in önizlemesidir; bugün runnable bir komut DEĞİLDİR.
 
-`safety: enabled: true` config'iyle her prompt ve yanıt Llama Guard tarafından taranır:
+Planlanan `--safety` bayrağı altında (yalnız önizleme — yukarıdaki nota bakın) her prompt ve yanıt Llama Guard tarafından taranır:
 
 ```text
 forgelm> [adversarial prompt]
@@ -108,7 +108,7 @@ Oturumlar şu durumlar için faydalı:
 
 ## İki modeli karşılaştırma
 
-> Not: `chat-compare` subcommand'ı v0.6.0+ Pro CLI için planlanmıştır ([GitHub'daki Phase 13 yol haritası](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)). Bugün aynı karşılaştırma her checkpoint'e karşı `forgelm --benchmark-only` ve aşağı akış judge config'i ile koşturulur; aşağıdaki snippet planlanan özel UX'i önizler.
+> Not: `chat-compare` subcommand'ı — judge hakemliğiyle interaktif, yan-yana chat-prompt karşılaştırması — v0.6.0+ Pro CLI katmanı için planlanmıştır ([GitHub'daki Phase 13 yol haritası](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)). Bugün eşdeğeri yoktur: `forgelm --benchmark-only` (bkz. `forgelm/cli/_no_train_modes.py`) her seferinde **tek** bir checkpoint üzerinde lm-evaluation-harness benchmark'ları çalıştırır — yan-yana karşılaştırma veya judge hakemliği yapmaz. İki checkpoint'i şimdi karşılaştırmak için `--benchmark-only`'yi checkpoint başına bir kez çalıştırın, judge'ı ayrıca koşturun ve sonuçları kendiniz birleştirin. Aşağıdaki snippet planlanan UX'i önizler.
 
 ```shell
 $ forgelm chat-compare ./checkpoints/v1 ./checkpoints/v2 --prompts data/probes.jsonl
diff --git a/docs/usermanuals/tr/deployment/model-merging.md b/docs/usermanuals/tr/deployment/model-merging.md
index 669f46b8..f9870153 100644
--- a/docs/usermanuals/tr/deployment/model-merging.md
+++ b/docs/usermanuals/tr/deployment/model-merging.md
@@ -169,7 +169,7 @@ merge_adapters(
 :::
 
 :::tip
-Keşif birleştirmesi için küçük bir `(algoritma, parametre)` kombinasyonu grid'i üretip her birini değerlendirin. Bunu otomatikleştiren bir `forgelm merge-sweep` yardımcısı **Faz 14 sonrası** planlanmaya devam ediyor — Faz 14'ün kendisi çok-aşamalı SFT/DPO/GRPO pipeline zincirlemesini `v0.7.0` ile yayınladı (bkz. [GitHub'daki Faz 14 completed-phases girişi](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap/completed-phases.md#phase-14-multi-stage-pipeline-chains-v070)) ama merge-sweep CLI'sını içermedi; o yardımcı explicit operatör talebini bekliyor. O zamana kadar her `(algoritma, parametre)` çiftini `forgelm` ile bir kez çağıran küçük bir shell döngüsü yazın.
+Keşif birleştirmesi için küçük bir `(algoritma, parametre)` kombinasyonu grid'i üretip her birini değerlendirin. Bunu otomatikleştiren bir `forgelm merge-sweep` yardımcısı **Faz 14 sonrası** planlanmaya devam ediyor — Faz 14'ün kendisi çok-aşamalı SFT/DPO/GRPO pipeline zincirlemesini `v0.7.0` ile yayınladı (bkz. [GitHub'daki Faz 14 completed-phases girişi](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap/completed-phases.md#phase-14-multi-stage-pipeline-chains-v070)) ama merge-sweep CLI'sını içermedi; o yardımcı explicit operatör talebini bekliyor. O zamana kadar her `(algoritma, parametre)` çiftini `forgelm` ile bir kez çağıran küçük bir shell döngüsü yazın.
 :::
 
 ## Bkz.
diff --git a/docs/usermanuals/tr/deployment/verify-gguf.md b/docs/usermanuals/tr/deployment/verify-gguf.md
index 13bc7db5..9d7603b1 100644
--- a/docs/usermanuals/tr/deployment/verify-gguf.md
+++ b/docs/usermanuals/tr/deployment/verify-gguf.md
@@ -156,4 +156,4 @@ Meta veri katmanını geri eklemek için `pip install gguf` ile yükleyin. Bu, p
 - [GGUF Export](#/deployment/gguf-export) — bu doğrulayıcının tükettiği sidecar'ı yazan üretim tarafı.
 - [Audit Log Doğrulama](#/compliance/verify-audit) — uyumluluk yüzeyindeki kardeş doğrulayıcı.
 - [Annex IV Doğrulama](#/compliance/annex-iv) — teknik dokümantasyon artifact'ı için kardeş doğrulayıcı.
-- [`verify_gguf_subcommand-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/verify_gguf_subcommand-tr.md) — tam bayrak tablosu ve kütüphane-sembol atıfları içeren referans doc (GitHub kaynağı).
+- [`verify_gguf_subcommand-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/verify_gguf_subcommand-tr.md) — tam bayrak tablosu ve kütüphane-sembol atıfları içeren referans doc (GitHub kaynağı).
diff --git a/docs/usermanuals/tr/evaluation/trend-tracking.md b/docs/usermanuals/tr/evaluation/trend-tracking.md
index 312697a9..b0cc79cd 100644
--- a/docs/usermanuals/tr/evaluation/trend-tracking.md
+++ b/docs/usermanuals/tr/evaluation/trend-tracking.md
@@ -74,7 +74,7 @@ Bu dosyayı commit edin. Küçüktür (koşu başına bir satır, JSON) ve CI ko
 
 ## Görselleştirme
 
-ForgeLM bir CLI raporu yayınlar. Özel `forgelm trend` subcommand'ı v0.6.0+ Pro CLI seviyesi için planlanmıştır ([GitHub'daki Phase 13 yol haritası](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)) — bugün aynı veri JSONL'dan `jq` ile sorgulanabilir. Bugünkü çalışan akış:
+ForgeLM bir CLI raporu yayınlar. Özel `forgelm trend` subcommand'ı v0.6.0+ Pro CLI seviyesi için planlanmıştır ([GitHub'daki Phase 13 yol haritası](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)) — bugün aynı veri JSONL'dan `jq` ile sorgulanabilir. Bugünkü çalışan akış:
 
 ```shell
 # Son 20 S5 (iftira) skoru:
diff --git a/docs/usermanuals/tr/getting-started/installation.md b/docs/usermanuals/tr/getting-started/installation.md
index 349c2a95..e01b7ec1 100644
--- a/docs/usermanuals/tr/getting-started/installation.md
+++ b/docs/usermanuals/tr/getting-started/installation.md
@@ -87,8 +87,8 @@ Bu kasıtlıdır — DeepSpeed / bitsandbytes / Presidio / sentence-transformers
 Python bağımlılıklarını ana makinenize kurmak istemiyorsanız resmi Docker imajı tüm extra'larla ForgeLM'i paketler:
 
 ```shell
-$ docker pull ghcr.io/cemililik/forgelm:latest
-$ docker run --gpus all -v $PWD:/workspace ghcr.io/cemililik/forgelm:latest \
+$ docker pull ghcr.io/hodetech/forgelm:latest
+$ docker run --gpus all -v $PWD:/workspace ghcr.io/hodetech/forgelm:latest \
     forgelm --config /workspace/configs/run.yaml
 ```
 
diff --git a/docs/usermanuals/tr/operations/docker.md b/docs/usermanuals/tr/operations/docker.md
index 08a62f54..8a59de53 100644
--- a/docs/usermanuals/tr/operations/docker.md
+++ b/docs/usermanuals/tr/operations/docker.md
@@ -12,12 +12,12 @@ ForgeLM, yerel geliştirme, on-prem cluster ve cloud GPU'lar arası yeniden üre
 Resmi imajı çekin:
 
 ```shell
-$ docker pull ghcr.io/cemililik/forgelm:latest
+$ docker pull ghcr.io/hodetech/forgelm:latest
 $ docker run --gpus all \
     -v $PWD:/workspace \
     -v $HOME/.cache/huggingface:/root/.cache/huggingface \
     -e HF_TOKEN \
-    ghcr.io/cemililik/forgelm:latest \
+    ghcr.io/hodetech/forgelm:latest \
     forgelm --config /workspace/configs/run.yaml
 ```
 
@@ -43,7 +43,7 @@ version: "3.9"
 
 services:
   trainer:
-    image: ghcr.io/cemililik/forgelm:latest
+    image: ghcr.io/hodetech/forgelm:latest
     deploy:
       resources:
         reservations:
@@ -81,7 +81,7 @@ $ docker compose up trainer
 Özel modifikasyonlar gerekirse:
 
 ```shell
-$ git clone https://github.com/cemililik/ForgeLM
+$ git clone https://github.com/HodeTech/ForgeLM
 $ cd ForgeLM
 $ docker build -t forgelm:custom -f Dockerfile .
 $ docker run --gpus all forgelm:custom forgelm --version
@@ -95,7 +95,7 @@ Air-gap ortamlar için her şey önceden cache'lenmiş imaj kurun:
 
 ```dockerfile
 # airgap.Dockerfile
-FROM ghcr.io/cemililik/forgelm:latest
+FROM ghcr.io/hodetech/forgelm:latest
 
 # Base modeli önceden cache'le
 RUN forgelm cache-models --model "Qwen/Qwen2.5-7B-Instruct"
diff --git a/docs/usermanuals/tr/operations/experiment-tracking.md b/docs/usermanuals/tr/operations/experiment-tracking.md
index b522d8ca..2cd80f33 100644
--- a/docs/usermanuals/tr/operations/experiment-tracking.md
+++ b/docs/usermanuals/tr/operations/experiment-tracking.md
@@ -107,7 +107,7 @@ ForgeLM `training.wandb:` veya `training.mlflow:` sub-bloğu **sunmaz**. Artifac
 
 Her backend'in UI'sı karşılaştırmayı doğal şekilde halleder — karşılaştırılabilir koşular `run_name` öneki, etiketler ve config hash paylaşır. Yerleşik CLI özeti yolda:
 
-> Not: `forgelm compare-runs` subcommand'ı v0.6.0+ Pro CLI seviyesi için planlanmıştır ([GitHub'daki Phase 13 yol haritası](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md)). Bugün aynı karşılaştırma tracking backend'inizin UI'sı (W&B / MLflow / Comet) veya her koşunun JSON envelope'una karşı küçük bir `jq` ile koşturulur.
+> Not: `forgelm compare-runs` subcommand'ı v0.6.0+ Pro CLI seviyesi için planlanmıştır ([GitHub'daki Phase 13 yol haritası](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md)). Bugün aynı karşılaştırma tracking backend'inizin UI'sı (W&B / MLflow / Comet) veya her koşunun JSON envelope'una karşı küçük bir `jq` ile koşturulur.
 
 Bugünkü çalışan akış (W&B / MLflow / Comet UI canonical yüzey; aşağıdaki ad-hoc CLI karşılaştırma için `jq` kısayolu):
 
diff --git a/docs/usermanuals/tr/operations/gpu-cost.md b/docs/usermanuals/tr/operations/gpu-cost.md
index b85aad74..c4c1289e 100644
--- a/docs/usermanuals/tr/operations/gpu-cost.md
+++ b/docs/usermanuals/tr/operations/gpu-cost.md
@@ -11,7 +11,7 @@ description: 16 GPU profilinde otomatik tespit ve saatlik tarifenize göre koşu
 > planlanmıştır** ve `forgelm/config.py` tarafından şu an honure
 > edilmiyor. Aşağıdaki `cost_tracking:` örnekleri ileriye dönük
 > yer tutuculardır — YAML yüzeyi inene kadar saatlik tarifeleri
-> manuel ayarlayın. Erteleme için bkz. [GitHub'daki risks-and-decisions yol haritası](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap/risks-and-decisions.md).
+> manuel ayarlayın. Erteleme için bkz. [GitHub'daki risks-and-decisions yol haritası](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap/risks-and-decisions.md).
 
 ForgeLM, üzerinde koştuğunuz GPU'yu tespit eder, profilini (bellek, compute, tipik saatlik tarife) bulur ve koşu başı maliyeti izler. Her koşunun ardından audit log tam olarak ne kadar GPU zamanı kullanıldığını ve maliyetini kaydeder.
 
diff --git a/docs/usermanuals/tr/operations/iso-soc2-deployer.md b/docs/usermanuals/tr/operations/iso-soc2-deployer.md
index 111d138e..b197f5c8 100644
--- a/docs/usermanuals/tr/operations/iso-soc2-deployer.md
+++ b/docs/usermanuals/tr/operations/iso-soc2-deployer.md
@@ -34,23 +34,23 @@ Derin rehber her birini tam `jq` / CLI komutu + döndürdüğü artefakt ile yan
 Aşağıdaki dosyaların tümü toolkit ile birlikte GitHub'da yayımlanır — depoda yer alırlar ama manual görüntüleyicisinin parçası değildirler.
 
 - Derin rehber — tam operatör cookbook'u, on-iki maddelik kurulum checklist'i, yaygın tuzaklar:
-  [`iso_soc2_deployer_guide-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide-tr.md)
+  [`iso_soc2_deployer_guide-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide-tr.md)
 - Tam ISO 27001:2022 Annex A kontrol eşlemesi × ForgeLM kanıtı:
-  [`iso27001_control_mapping-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/iso27001_control_mapping-tr.md)
+  [`iso27001_control_mapping-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/iso27001_control_mapping-tr.md)
 - Tam SOC 2 Trust Services Criteria eşlemesi:
-  [`soc2_trust_criteria_mapping-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/soc2_trust_criteria_mapping-tr.md)
+  [`soc2_trust_criteria_mapping-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/soc2_trust_criteria_mapping-tr.md)
 - Önceden doldurulmuş 93-kontrollü Statement of Applicability matrisi:
-  [`statement_of_applicability-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/statement_of_applicability-tr.md)
+  [`statement_of_applicability-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/statement_of_applicability-tr.md)
 - Önceden doldurulmuş risk register:
-  [`risk_treatment_plan-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/risk_treatment_plan-tr.md)
+  [`risk_treatment_plan-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/risk_treatment_plan-tr.md)
 - Substrate-tarafı şifreleme rehberliği:
-  [`encryption_at_rest-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/encryption_at_rest-tr.md)
+  [`encryption_at_rest-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/encryption_at_rest-tr.md)
 - Operatör kimliği + secret yönetimi:
-  [`access_control-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/access_control-tr.md)
+  [`access_control-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/access_control-tr.md)
 - Olay müdahale runbook'u:
-  [`sop_incident_response-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/sop_incident_response-tr.md)
+  [`sop_incident_response-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/sop_incident_response-tr.md)
 - Değişiklik yönetimi runbook'u:
-  [`sop_change_management-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/qms/sop_change_management-tr.md)
+  [`sop_change_management-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/qms/sop_change_management-tr.md)
 
 ## Ayrıca bakınız
 
diff --git a/docs/usermanuals/tr/operations/supply-chain.md b/docs/usermanuals/tr/operations/supply-chain.md
index 69a30334..0f4d0410 100644
--- a/docs/usermanuals/tr/operations/supply-chain.md
+++ b/docs/usermanuals/tr/operations/supply-chain.md
@@ -85,11 +85,11 @@ ForgeLM **varsayılan proje-seviyesi bir ignore listesi yayınlamaz**. Projenin
 ## Daha fazla okumak için nereye
 
 - Tam referans (severity politikası, suppression syntax'ı, ilgili ISO/SOC 2 kontrolleri):
-  [`supply_chain_security-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/supply_chain_security-tr.md) (GitHub kaynağı).
+  [`supply_chain_security-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/supply_chain_security-tr.md) (GitHub kaynağı).
 - Operatör denetim cookbook'u (Q4 SBOM'u yürür, Q5 erişim kontrollerini yürür, Q7 olay müdahalesini yürür):
-  [`iso_soc2_deployer_guide-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide-tr.md) (GitHub kaynağı).
+  [`iso_soc2_deployer_guide-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide-tr.md) (GitHub kaynağı).
 - SBOM emitter kaynağı (pure stdlib, sıfır dep):
-  [`tools/generate_sbom.py`](https://github.com/cemililik/ForgeLM/blob/main/tools/generate_sbom.py) (GitHub kaynağı).
+  [`tools/generate_sbom.py`](https://github.com/HodeTech/ForgeLM/blob/main/tools/generate_sbom.py) (GitHub kaynağı).
 
 ## Ayrıca bakınız
 
diff --git a/docs/usermanuals/tr/operations/troubleshooting.md b/docs/usermanuals/tr/operations/troubleshooting.md
index 0c54f56c..d5794e3c 100644
--- a/docs/usermanuals/tr/operations/troubleshooting.md
+++ b/docs/usermanuals/tr/operations/troubleshooting.md
@@ -172,7 +172,7 @@ audit:
 3. `config.yaml`'iniz (sırlar redakte edilmiş).
 4. `forgelm doctor` çıktısı.
 
-Issue açın: <https://github.com/cemililik/ForgeLM/issues>. Maintainer ekibi 48 saat içinde triaj eder.
+Issue açın: <https://github.com/HodeTech/ForgeLM/issues>. Maintainer ekibi 48 saat içinde triaj eder.
 
 ## Bkz.
 
diff --git a/docs/usermanuals/tr/operations/webhooks.md b/docs/usermanuals/tr/operations/webhooks.md
index aad88c26..76af2ef6 100644
--- a/docs/usermanuals/tr/operations/webhooks.md
+++ b/docs/usermanuals/tr/operations/webhooks.md
@@ -32,7 +32,7 @@ $ forgelm --config configs/run.yaml
 ## Wire-format event'ler
 
 ForgeLM tam **beş** webhook event'i yayar. Aşağıdaki tablo
-[GitHub'daki Audit Event Kataloğu](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)
+[GitHub'daki Audit Event Kataloğu](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)
 ile aynalanan kanonik yüzeydir:
 
 | Event | Ne zaman fırlar | Gate |
@@ -59,7 +59,7 @@ sarmalama **yapmaz**:
 ```
 
 Payload anahtarları event'e göre değişir; tam per-event alan listesi
-[GitHub'daki Audit Event Kataloğu](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)
+[GitHub'daki Audit Event Kataloğu](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/audit_event_catalog.md)
 *Webhook lifecycle events* tablosundadır.
 
 ## Slack / Teams / Discord ingest
diff --git a/docs/usermanuals/tr/reference/configuration.md b/docs/usermanuals/tr/reference/configuration.md
index cde836c2..f912a6e4 100644
--- a/docs/usermanuals/tr/reference/configuration.md
+++ b/docs/usermanuals/tr/reference/configuration.md
@@ -286,7 +286,7 @@ auth:
 
 v0.5.5'te `deployment:` üst-seviye YAML anahtarı yoktur — `ForgeConfig` bilinmeyen anahtarları reddeder (`extra="forbid"`), dolayısıyla eğitim config'inize eklerseniz yükleme anında `ConfigError` fırlar. Deployment knob'ları YAML yerine `forgelm deploy` CLI bayrakları olarak açılır. Canlı target seçenekleri `--target {ollama,vllm,tgi,hf-endpoints}`'dir; tam surface için [Deploy hedefleri sayfasına](#/deployment/deploy-targets) ve [CLI referansına](#/reference/cli) bakın.
 
-> **v0.6.0+ için planlanan:** YAML-destekli `deployment:` bölümü [GitHub'daki Phase 14 pipeline-chains yol haritasında](https://github.com/cemililik/ForgeLM/blob/main/docs/roadmap.md) (eski v0.5.x placeholder'larından ertelendi). O zamana kadar, üçüncü taraf şablonlarda gördüğünüz herhangi bir "deployment:" YAML'ını bilgilendirici sayın; otoriter olan yalnızca `forgelm deploy` bayraklarıdır.
+> **v0.6.0+ için planlanan:** YAML-destekli `deployment:` bölümü [GitHub'daki Phase 14 pipeline-chains yol haritasında](https://github.com/HodeTech/ForgeLM/blob/main/docs/roadmap.md) (eski v0.5.x placeholder'larından ertelendi). O zamana kadar, üçüncü taraf şablonlarda gördüğünüz herhangi bir "deployment:" YAML'ını bilgilendirici sayın; otoriter olan yalnızca `forgelm deploy` bayraklarıdır.
 
 ## Bkz.
 
diff --git a/docs/usermanuals/tr/reference/exit-codes.md b/docs/usermanuals/tr/reference/exit-codes.md
index 0abe8d09..11a7db6f 100644
--- a/docs/usermanuals/tr/reference/exit-codes.md
+++ b/docs/usermanuals/tr/reference/exit-codes.md
@@ -18,7 +18,7 @@ ForgeLM'in exit kodları kamuya açık bir kontrattır. CI/CD hatları, schedule
 | **4** | `EXIT_AWAITING_APPROVAL` | `evaluation.require_human_approval: true` engelliyor. | Hattı tut; reviewer'ı tetikle |
 | **5** | `EXIT_WIZARD_CANCELLED` | `forgelm --wizard` YAML üretmeden çıktı — Ctrl-C, non-tty stdin reddi veya operatör kaydetmeyi reddetti. `EXIT_SUCCESS`'tan ayrı ki CI "wizard tamamlandı" ile "wizard hiçbir şey yazmadı" arasını ayırt edebilsin. | No-op olarak kabul et; mesajı yüzeyle; eski config ile DEVAM ETME |
 
-Bu altı tam sayı tüm kamuya açık kontratı oluşturur — kanonik tanım için bkz. [`forgelm/cli/_exit_codes.py`](https://github.com/cemililik/ForgeLM/blob/main/forgelm/cli/_exit_codes.py). Diğer her sıfır olmayan değer (sinyal kaynaklı 128+N kodları dahil) süreç çıkmadan önce `EXIT_TRAINING_ERROR` (2) değerine sıkıştırılır.
+Bu altı tam sayı tüm kamuya açık kontratı oluşturur — kanonik tanım için bkz. [`forgelm/cli/_exit_codes.py`](https://github.com/HodeTech/ForgeLM/blob/main/forgelm/cli/_exit_codes.py). Diğer her sıfır olmayan değer (sinyal kaynaklı 128+N kodları dahil) süreç çıkmadan önce `EXIT_TRAINING_ERROR` (2) değerine sıkıştırılır.
 
 ## CI pattern'lerine eşleme
 
diff --git a/docs/usermanuals/tr/reference/json-output.md b/docs/usermanuals/tr/reference/json-output.md
index ac3dfcc1..65ac76ef 100644
--- a/docs/usermanuals/tr/reference/json-output.md
+++ b/docs/usermanuals/tr/reference/json-output.md
@@ -5,7 +5,7 @@ description: Her forgelm subcommand için kilitli --output-format json envelope
 
 # JSON çıktı şemaları
 
-`--output-format json` destekleyen her `forgelm` subcommand'ı stdout'a stabil bir JSON envelope üretir. Alan adları ve nesting [GitHub'daki release standardı](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/release.md) gereği public CLI kontratının parçası: bir anahtarı yeniden adlandırmak MAJOR-version break sayılır.
+`--output-format json` destekleyen her `forgelm` subcommand'ı stdout'a stabil bir JSON envelope üretir. Alan adları ve nesting [GitHub'daki release standardı](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/release.md) gereği public CLI kontratının parçası: bir anahtarı yeniden adlandırmak MAJOR-version break sayılır.
 
 Bu sayfa kanonik referanstır. `forgelm` çıktısını parse eden CI/CD pipeline'ları burada belgelenen yapılara karşı pin'lemelidir.
 
@@ -13,7 +13,7 @@ Bu sayfa kanonik referanstır. `forgelm` çıktısını parse eden CI/CD pipelin
 
 - **stdout vs stderr.** JSON envelope **stdout**'a gider. İnsana okunabilir loglar (info / warning / error) **stderr**'e gider. `forgelm ... --output-format json | jq .` ile pipe edip operatör mesajlarını `2>` ile ayrı okuyun.
 - **Üst seviye sarmalayıcı.** Her envelope `"success": true | false` ile başlar. Tüketiciler önce bu tek anahtarda branch açabilir.
-- **Hata envelope'u.** `success: false` olduğunda envelope `"error": "<mesaj>"` (string) taşır. Opsiyonel zenginleştirilmiş alanlar (`exit_code`, `error_type`, `details`) [GitHub'daki error-handling standardı](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/error-handling.md) gereği var olabilir. Bu alanlardan kesinlik isteyen tüketiciler `$?` ile süreç exit kodunu da kontrol etmelidir.
+- **Hata envelope'u.** `success: false` olduğunda envelope `"error": "<mesaj>"` (string) taşır. Opsiyonel zenginleştirilmiş alanlar (`exit_code`, `error_type`, `details`) [GitHub'daki error-handling standardı](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/error-handling.md) gereği var olabilir. Bu alanlardan kesinlik isteyen tüketiciler `$?` ile süreç exit kodunu da kontrol etmelidir.
 - **Exit kodları.** Bkz. [Exit Kodları](#/reference/exit-codes). Envelope, exit code ile tutarlıdır: `success: true` ⟺ exit `0`; `success: false` ⟺ non-zero exit.
 
 ## `forgelm doctor`
@@ -528,10 +528,10 @@ Wave 2b Phase 36 — GGUF model dosyası bütünlük kontrolü.
 2. Üst seviye anahtarların tam setini pin'leyen `tests/test_json_envelope_contract.py` (veya per-subcommand test dosyası) testi.
 3. Per-collection anahtar "sonuçlar subcommand'in birincil ismine göre adlandırılmış bir anahtar altında yaşar" konvansiyonunu izler (yani `doctor` → `checks`, `approvals --pending` → `pending` vb.).
 
-Merge sonrası bir anahtarı yeniden adlandırmak [GitHub'daki release standardı](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/release.md) gereği MAJOR-version bump'tır.
+Merge sonrası bir anahtarı yeniden adlandırmak [GitHub'daki release standardı](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/release.md) gereği MAJOR-version bump'tır.
 
 ## Ayrıca bakın
 
 - [Exit Kodları](#/reference/exit-codes) — `success: bool`'ın aligned olduğu kontrat.
-- [`error-handling.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/error-handling.md) — hata envelope kontratı (GitHub kaynağı).
-- [`release.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/release.md) — JSON yeniden adlandırmaları ne zaman breaking sayılır (GitHub kaynağı).
+- [`error-handling.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/error-handling.md) — hata envelope kontratı (GitHub kaynağı).
+- [`release.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/release.md) — JSON yeniden adlandırmaları ne zaman breaking sayılır (GitHub kaynağı).
diff --git a/docs/usermanuals/tr/reference/library-api.md b/docs/usermanuals/tr/reference/library-api.md
index 1416f8b5..be75032f 100644
--- a/docs/usermanuals/tr/reference/library-api.md
+++ b/docs/usermanuals/tr/reference/library-api.md
@@ -43,11 +43,11 @@ assert "torch" not in sys.modules     # tests/test_library_api.py ile pinlenir
 ## Daha fazla okumak için nereye
 
 - Her imza ve işlenmiş örnek dahil tam referans toolkit ile birlikte GitHub'da yayımlanır:
-  [`library_api_reference-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/library_api_reference-tr.md).
+  [`library_api_reference-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/library_api_reference-tr.md).
 - Uçtan uca üç pipeline deseni ve yaygın tuzaklar dahil derin rehber:
-  [`library_api-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/library_api-tr.md) (GitHub kaynağı).
+  [`library_api-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/library_api-tr.md) (GitHub kaynağı).
 - Faz 18 tasarım gerekçesi (kararlılık katmanları, tip kontratı, deprecation cadence):
-  [`library_api.md` tasarım notu](https://github.com/cemililik/ForgeLM/blob/main/docs/design/library_api.md) (GitHub kaynağı).
+  [`library_api.md` tasarım notu](https://github.com/HodeTech/ForgeLM/blob/main/docs/design/library_api.md) (GitHub kaynağı).
 
 ## Ayrıca bakınız
 
diff --git a/docs/usermanuals/tr/reference/performance.md b/docs/usermanuals/tr/reference/performance.md
index 58fce987..a94926cf 100644
--- a/docs/usermanuals/tr/reference/performance.md
+++ b/docs/usermanuals/tr/reference/performance.md
@@ -36,10 +36,10 @@ Aksi takdirde sığmayacak bir modeli sığdırmak için üç ortogonal araç. B
 ## Daha fazla okumak için nereye
 
 - VRAM-vs-throughput tabloları, her stratejinin ne zaman kullanılacağı ve yaygın tuzaklarla derin rehber:
-  [`performance-tr.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/performance-tr.md) (GitHub kaynağı).
+  [`performance-tr.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/performance-tr.md) (GitHub kaynağı).
 - Tam konfigürasyon referansı (her düğme, her varsayılan) — bu manual içinde [Konfigürasyon](#/reference/configuration)'da da bulunur.
 - Projenin dayattığı lazy-import katkıda bulunan standardı:
-  [`coding.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/standards/coding.md) (GitHub kaynağı).
+  [`coding.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/standards/coding.md) (GitHub kaynağı).
 
 ## Ayrıca bakınız
 
diff --git a/docs/usermanuals/tr/reference/yaml-templates.md b/docs/usermanuals/tr/reference/yaml-templates.md
index 0610d0cc..3b0255e5 100644
--- a/docs/usermanuals/tr/reference/yaml-templates.md
+++ b/docs/usermanuals/tr/reference/yaml-templates.md
@@ -173,7 +173,7 @@ opt-in olarak kullanın.
 
 ## Field referansı
 
-Kanonik şema [`forgelm/config.py`](https://github.com/cemililik/ForgeLM/blob/main/forgelm/config.py)
+Kanonik şema [`forgelm/config.py`](https://github.com/HodeTech/ForgeLM/blob/main/forgelm/config.py)
 altında, Pydantic modelleri `ForgeConfig`, `ModelConfig`, `LoraConfig`,
 `TrainingConfig`, `DataConfig`, `EvaluationConfig`, `BenchmarkConfig`,
 `SafetyConfig`, `JudgeConfig`, `ComplianceMetadataConfig`,
diff --git a/forgelm/model_card.py b/forgelm/model_card.py
index 430de594..b9e6e993 100644
--- a/forgelm/model_card.py
+++ b/forgelm/model_card.py
@@ -24,7 +24,7 @@
 
 # {model_name}
 
-Fine-tuned with [ForgeLM](https://github.com/cemililik/ForgeLM) — config-driven LLM fine-tuning toolkit.
+Fine-tuned with [ForgeLM](https://github.com/HodeTech/ForgeLM) — config-driven LLM fine-tuning toolkit.
 
 ## Training Details
 
diff --git a/notebooks/data_curation.ipynb b/notebooks/data_curation.ipynb
index 300610d7..c00a39a1 100644
--- a/notebooks/data_curation.ipynb
+++ b/notebooks/data_curation.ipynb
@@ -13,7 +13,7 @@
     "\n",
     "**Requirements:** Any runtime works — no GPU needed. Both commands are CPU-bound and stream their input.\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/data_curation.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/data_curation.ipynb)"
    ]
   },
   {
@@ -383,7 +383,7 @@
   {
    "cell_type": "markdown",
    "metadata": {},
-   "source": "## What's next\n\n- **Train on the curated JSONL**: point any of the training notebooks at\n  `./curated/policies.jsonl` via `data.dataset_name_or_path`.\n  - [`quickstart_sft.ipynb`](./quickstart_sft.ipynb) — first SFT run\n  - [`multi_dataset.ipynb`](./multi_dataset.ipynb) — mix the curated\n    set with public datasets\n- **Long-form guides**:\n  - [`docs/guides/ingestion.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/ingestion.md)\n    — every flag, every chunking strategy, every extra\n  - [`docs/guides/data_audit.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/data_audit.md)\n    — audit JSON schema, severity tiers, governance integration\n- **Wizard**: `forgelm --wizard` offers to run `forgelm ingest` inline\n  when you point it at a directory of raw docs, and offers to run\n  `forgelm audit` automatically once a JSONL is selected — closes the\n  BYOD audit loop end-to-end.\n- **Other v0.5.0 audit add-ons**:\n  - `--croissant` emits a [Google Croissant 1.0](http://mlcommons.org/croissant/)\n    dataset card under the report's `croissant` key so the same JSON\n    file doubles as both the EU AI Act Article 10 governance artifact\n    and a Croissant-consumer dataset card.\n  - `--pii-ml [--pii-ml-language LANG]` layers\n    [Presidio](https://github.com/microsoft/presidio) NER on top of\n    the regex detector — adds `person` / `organization` /\n    `location` categories to `pii_summary` / `pii_severity`. **Two-step\n    install:**\n    ```bash\n    pip install 'forgelm[ingestion-pii-ml]'\n    python -m spacy download en_core_web_lg\n    ```\n    `presidio-analyzer` does not transitively ship a spaCy NER model;\n    without the model `--pii-ml` raises an `ImportError` with the\n    install recipe **before** any rows are scanned. Pass\n    `--pii-ml-language tr` (and download the matching spaCy model) to\n    audit Turkish corpora."
+   "source": "## What's next\n\n- **Train on the curated JSONL**: point any of the training notebooks at\n  `./curated/policies.jsonl` via `data.dataset_name_or_path`.\n  - [`quickstart_sft.ipynb`](./quickstart_sft.ipynb) — first SFT run\n  - [`multi_dataset.ipynb`](./multi_dataset.ipynb) — mix the curated\n    set with public datasets\n- **Long-form guides**:\n  - [`docs/guides/ingestion.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/ingestion.md)\n    — every flag, every chunking strategy, every extra\n  - [`docs/guides/data_audit.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/data_audit.md)\n    — audit JSON schema, severity tiers, governance integration\n- **Wizard**: `forgelm --wizard` offers to run `forgelm ingest` inline\n  when you point it at a directory of raw docs, and offers to run\n  `forgelm audit` automatically once a JSONL is selected — closes the\n  BYOD audit loop end-to-end.\n- **Other v0.5.0 audit add-ons**:\n  - `--croissant` emits a [Google Croissant 1.0](http://mlcommons.org/croissant/)\n    dataset card under the report's `croissant` key so the same JSON\n    file doubles as both the EU AI Act Article 10 governance artifact\n    and a Croissant-consumer dataset card.\n  - `--pii-ml [--pii-ml-language LANG]` layers\n    [Presidio](https://github.com/microsoft/presidio) NER on top of\n    the regex detector — adds `person` / `organization` /\n    `location` categories to `pii_summary` / `pii_severity`. **Two-step\n    install:**\n    ```bash\n    pip install 'forgelm[ingestion-pii-ml]'\n    python -m spacy download en_core_web_lg\n    ```\n    `presidio-analyzer` does not transitively ship a spaCy NER model;\n    without the model `--pii-ml` raises an `ImportError` with the\n    install recipe **before** any rows are scanned. Pass\n    `--pii-ml-language tr` (and download the matching spaCy model) to\n    audit Turkish corpora."
   }
  ],
  "metadata": {
diff --git a/notebooks/dpo_alignment.ipynb b/notebooks/dpo_alignment.ipynb
index a260d089..c3bada72 100644
--- a/notebooks/dpo_alignment.ipynb
+++ b/notebooks/dpo_alignment.ipynb
@@ -10,7 +10,7 @@
     "\n",
     "**Requirements:** GPU runtime required (Runtime → Change runtime type → T4 GPU)\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/dpo_alignment.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/dpo_alignment.ipynb)"
    ]
   },
   {
diff --git a/notebooks/galore_memory_optimization.ipynb b/notebooks/galore_memory_optimization.ipynb
index b55a85ef..80b1b5b7 100644
--- a/notebooks/galore_memory_optimization.ipynb
+++ b/notebooks/galore_memory_optimization.ipynb
@@ -33,7 +33,7 @@
     "\n",
     "**Requirements:** GPU runtime required (Runtime → Change runtime type → T4 GPU)\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/galore_memory_optimization.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/galore_memory_optimization.ipynb)"
    ]
   },
   {
diff --git a/notebooks/grpo_reasoning.ipynb b/notebooks/grpo_reasoning.ipynb
index 240c5650..15530dee 100644
--- a/notebooks/grpo_reasoning.ipynb
+++ b/notebooks/grpo_reasoning.ipynb
@@ -10,7 +10,7 @@
     "\n",
     "**Requirements:** GPU runtime required (Runtime → Change runtime type → T4 GPU)\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/grpo_reasoning.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/grpo_reasoning.ipynb)"
    ]
   },
   {
diff --git a/notebooks/ingestion_playground.ipynb b/notebooks/ingestion_playground.ipynb
index 64c81ce5..0ed6bc7b 100644
--- a/notebooks/ingestion_playground.ipynb
+++ b/notebooks/ingestion_playground.ipynb
@@ -18,7 +18,7 @@
     "\n",
     "**Requirements:** any runtime — no GPU needed. Both `ingest` and `audit` are CPU-bound and stream their input.\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/ingestion_playground.ipynb)\n"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/ingestion_playground.ipynb)\n"
    ]
   },
   {
@@ -405,8 +405,8 @@
     "- **Token-aware chunking.** If your model context is the real cap\n",
     "  (not characters), swap `--chunk-size N` for `--chunk-tokens N\n",
     "  --tokenizer HF_ID` in Step 3.\n",
-    "- **Long-form guides:** [`docs/guides/ingestion.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/ingestion.md)\n",
-    "  and [`docs/guides/data_audit.md`](https://github.com/cemililik/ForgeLM/blob/main/docs/guides/data_audit.md)\n",
+    "- **Long-form guides:** [`docs/guides/ingestion.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/ingestion.md)\n",
+    "  and [`docs/guides/data_audit.md`](https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/data_audit.md)\n",
     "  cover every flag, every chunking strategy, and the full audit\n",
     "  JSON schema.\n"
    ]
diff --git a/notebooks/kto_binary_feedback.ipynb b/notebooks/kto_binary_feedback.ipynb
index 324240b1..b63298e0 100644
--- a/notebooks/kto_binary_feedback.ipynb
+++ b/notebooks/kto_binary_feedback.ipynb
@@ -10,7 +10,7 @@
     "\n",
     "**Requirements:** GPU runtime required (Runtime → Change runtime type → T4 GPU)\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/kto_binary_feedback.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/kto_binary_feedback.ipynb)"
    ]
   },
   {
diff --git a/notebooks/multi_dataset.ipynb b/notebooks/multi_dataset.ipynb
index 55fa51e4..d81fd00b 100644
--- a/notebooks/multi_dataset.ipynb
+++ b/notebooks/multi_dataset.ipynb
@@ -10,7 +10,7 @@
     "\n",
     "**Requirements:** GPU runtime recommended (Runtime → Change runtime type → T4 GPU)\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/multi_dataset.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/multi_dataset.ipynb)"
    ]
   },
   {
diff --git a/notebooks/post_training_workflow.ipynb b/notebooks/post_training_workflow.ipynb
index 56baa08f..15fd912e 100644
--- a/notebooks/post_training_workflow.ipynb
+++ b/notebooks/post_training_workflow.ipynb
@@ -25,7 +25,7 @@
     "`quickstart_sft.ipynb`) under `./checkpoints/final_model`, or any\n",
     "HuggingFace model directory.\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/post_training_workflow.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/post_training_workflow.ipynb)"
    ]
   },
   {
@@ -40,7 +40,7 @@
     "# Download config_template.yaml from the v0.5.7 tag (NOT main) so the YAML\n",
     "# matches the wheel above — `main` drifts as features land and would otherwise\n",
     "# reference fields the installed Pydantic schema rejects.\n",
-    "!wget -q https://raw.githubusercontent.com/cemililik/ForgeLM/v0.5.7/config_template.yaml\n",
+    "!wget -q https://raw.githubusercontent.com/HodeTech/ForgeLM/v0.5.7/config_template.yaml\n",
     "!forgelm --version"
    ]
   },
@@ -309,8 +309,8 @@
     "  `galore_memory_optimization.ipynb`, `multi_dataset.ipynb`,\n",
     "  `synthetic_data_training.ipynb`\n",
     "- Eval notebook: `safety_evaluation.ipynb`\n",
-    "- Full configuration reference: [docs/reference/configuration.md](https://github.com/cemililik/ForgeLM/blob/main/docs/reference/configuration.md)\n",
-    "- Release history: [CHANGELOG.md](https://github.com/cemililik/ForgeLM/blob/main/CHANGELOG.md)"
+    "- Full configuration reference: [docs/reference/configuration.md](https://github.com/HodeTech/ForgeLM/blob/main/docs/reference/configuration.md)\n",
+    "- Release history: [CHANGELOG.md](https://github.com/HodeTech/ForgeLM/blob/main/CHANGELOG.md)"
    ]
   }
  ],
diff --git a/notebooks/quickstart_sft.ipynb b/notebooks/quickstart_sft.ipynb
index d52fc599..50ebed48 100644
--- a/notebooks/quickstart_sft.ipynb
+++ b/notebooks/quickstart_sft.ipynb
@@ -16,7 +16,7 @@
     "> (length / language / dedup / leakage / quality), then point this\n",
     "> notebook's `data.dataset_name_or_path` at the curated JSONL.\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/quickstart_sft.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/quickstart_sft.ipynb)"
    ]
   },
   {
diff --git a/notebooks/safety_evaluation.ipynb b/notebooks/safety_evaluation.ipynb
index 83084a2a..c1ac974b 100644
--- a/notebooks/safety_evaluation.ipynb
+++ b/notebooks/safety_evaluation.ipynb
@@ -12,7 +12,7 @@
     "\n",
     "**Requirements:** GPU runtime required (Runtime → Change runtime type → T4 GPU)\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/safety_evaluation.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/safety_evaluation.ipynb)"
    ]
   },
   {
@@ -165,7 +165,7 @@
     "        import subprocess  # nosec B404 — intentional git invocation; no shell, fixed argv  # noqa: S404\n",
     "\n",
     "        result = subprocess.run(  # nosec B603 — fixed argv, no shell, no user input  # noqa: S603\n",
-    "            [\"git\", \"clone\", \"--depth\", \"1\", \"https://github.com/cemililik/ForgeLM.git\", clone_target],\n",
+    "            [\"git\", \"clone\", \"--depth\", \"1\", \"https://github.com/HodeTech/ForgeLM.git\", clone_target],\n",
     "            capture_output=True,\n",
     "            text=True,\n",
     "        )\n",
@@ -187,7 +187,7 @@
     "            import urllib.request  # noqa: S310 — pinned HTTPS to a known repo; no user-controlled URL\n",
     "\n",
     "            url = (\n",
-    "                \"https://raw.githubusercontent.com/cemililik/ForgeLM/v0.5.7/configs/safety_prompts/general_safety.jsonl\"\n",
+    "                \"https://raw.githubusercontent.com/HodeTech/ForgeLM/v0.5.7/configs/safety_prompts/general_safety.jsonl\"\n",
     "            )\n",
     "            try:\n",
     "                urllib.request.urlretrieve(url, target_file)  # noqa: S310 — see comment above\n",
diff --git a/notebooks/synthetic_data_training.ipynb b/notebooks/synthetic_data_training.ipynb
index 673eb675..5bbd7a7e 100644
--- a/notebooks/synthetic_data_training.ipynb
+++ b/notebooks/synthetic_data_training.ipynb
@@ -15,7 +15,7 @@
     "\n",
     "**Requirements:** GPU runtime recommended (Runtime → Change runtime type → T4 GPU)\n",
     "\n",
-    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/cemililik/ForgeLM/blob/main/notebooks/synthetic_data_training.ipynb)"
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/HodeTech/ForgeLM/blob/main/notebooks/synthetic_data_training.ipynb)"
    ]
   },
   {
diff --git a/pyproject.toml b/pyproject.toml
index 3e46bdcf..802b149f 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -170,11 +170,11 @@ security = [
 ]
 
 [project.urls]
-Homepage = "https://github.com/cemililik/ForgeLM"
-Documentation = "https://github.com/cemililik/ForgeLM/tree/main/docs/guides"
-Repository = "https://github.com/cemililik/ForgeLM"
-Issues = "https://github.com/cemililik/ForgeLM/issues"
-Changelog = "https://github.com/cemililik/ForgeLM/blob/main/CHANGELOG.md"
+Homepage = "https://github.com/HodeTech/ForgeLM"
+Documentation = "https://github.com/HodeTech/ForgeLM/tree/main/docs/guides"
+Repository = "https://github.com/HodeTech/ForgeLM"
+Issues = "https://github.com/HodeTech/ForgeLM/issues"
+Changelog = "https://github.com/HodeTech/ForgeLM/blob/main/CHANGELOG.md"
 
 [project.scripts]
 forgelm = "forgelm.cli:main"
diff --git a/site/README.md b/site/README.md
index 41a7e6bd..216ad2fa 100644
--- a/site/README.md
+++ b/site/README.md
@@ -59,10 +59,10 @@ To use your own Formspree form:
 
 ### 2. GitHub repo URL
 
-Search-and-replace `cemililik/ForgeLM` if you fork the project under a different organisation:
+Search-and-replace `HodeTech/ForgeLM` if you fork the project under a different organisation:
 
 ```bash
-grep -rl "cemililik/ForgeLM" site/ | xargs sed -i '' 's|cemililik/ForgeLM|YOUR_ORG/YourFork|g'
+grep -rl "HodeTech/ForgeLM" site/ | xargs sed -i '' 's|HodeTech/ForgeLM|YOUR_ORG/YourFork|g'
 ```
 
 ### 3. Domain / og-image / favicon
diff --git a/site/compliance.html b/site/compliance.html
index 46d21160..ed5296df 100644
--- a/site/compliance.html
+++ b/site/compliance.html
@@ -68,7 +68,7 @@
   "name": "ForgeLM",
   "url": "https://forgelm.dev/",
   "sameAs": [
-    "https://github.com/cemililik/ForgeLM",
+    "https://github.com/HodeTech/ForgeLM",
     "https://pypi.org/project/forgelm/"
   ]
 }
@@ -255,7 +255,7 @@ <h3 data-i18n="compliance.iso.supply.title">Supply chain</h3>
       </article>
     </div>
 
-    <p class="compliance-cookbook" data-i18n-html="compliance.iso.cookbook">For the full audit cookbook, including 8 audit-floor questions and a 93-control coverage map, see <a href="https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md" target="_blank" rel="noopener"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.</p>
+    <p class="compliance-cookbook" data-i18n-html="compliance.iso.cookbook">For the full audit cookbook, including 8 audit-floor questions and a 93-control coverage map, see <a href="https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md" target="_blank" rel="noopener"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.</p>
   </div>
 </section>
 
@@ -321,7 +321,7 @@ <h2 data-i18n-html="compliance.limits.title">What ForgeLM does <em>not</em> clai
       <h2 data-i18n="compliance.cta.title">Want a deeper look?</h2>
       <p data-i18n-html="compliance.cta.body">The compliance module, audit log schema, and Annex IV generator are all in <code>forgelm/compliance.py</code>.</p>
       <div class="cta-actions">
-        <a href="https://github.com/cemililik/ForgeLM/blob/main/forgelm/compliance.py" target="_blank" rel="noopener" class="btn btn-primary" data-i18n="compliance.cta.btn1">View compliance.py</a>
+        <a href="https://github.com/HodeTech/ForgeLM/blob/main/forgelm/compliance.py" target="_blank" rel="noopener" class="btn btn-primary" data-i18n="compliance.cta.btn1">View compliance.py</a>
         <a href="contact.html" class="btn btn-ghost" data-i18n="compliance.cta.btn2">Talk to us</a>
       </div>
     </div>
@@ -358,10 +358,10 @@ <h4 data-i18n="common.footer.product">Product</h4>
       <div class="footer-col">
         <h4 data-i18n="common.footer.community">Community</h4>
         <ul>
-          <li><a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
         </ul>
       </div>
 
diff --git a/site/contact.html b/site/contact.html
index 728fc04e..a069e78e 100644
--- a/site/contact.html
+++ b/site/contact.html
@@ -68,7 +68,7 @@
   "name": "ForgeLM",
   "url": "https://forgelm.dev/",
   "sameAs": [
-    "https://github.com/cemililik/ForgeLM",
+    "https://github.com/HodeTech/ForgeLM",
     "https://pypi.org/project/forgelm/"
   ]
 }
@@ -197,7 +197,7 @@ <h2 data-i18n="contact.channels.title">Other channels</h2>
             <div class="channel-text">
               <h3>GitHub Issues</h3>
               <p data-i18n="contact.channel.issues_body">Reproducible bug? File an issue with config + log excerpt.</p>
-              <a href="https://github.com/cemililik/ForgeLM/issues/new" target="_blank" rel="noopener" data-i18n="contact.channel.issues_cta">Open an issue →</a>
+              <a href="https://github.com/HodeTech/ForgeLM/issues/new" target="_blank" rel="noopener" data-i18n="contact.channel.issues_cta">Open an issue →</a>
             </div>
           </li>
 
@@ -208,7 +208,7 @@ <h3>GitHub Issues</h3>
             <div class="channel-text">
               <h3>GitHub Discussions</h3>
               <p data-i18n="contact.channel.discussions_body">Open-ended questions, design ideas — discuss with the community.</p>
-              <a href="https://github.com/cemililik/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="contact.channel.discussions_cta">Join the conversation →</a>
+              <a href="https://github.com/HodeTech/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="contact.channel.discussions_cta">Join the conversation →</a>
             </div>
           </li>
 
@@ -229,7 +229,7 @@ <h3 data-i18n="contact.channel.security_title">Security disclosure</h3>
             <div class="channel-text">
               <h3 data-i18n="contact.channel.contribute_title">Contribute</h3>
               <p data-i18n-html="contact.channel.contribute_body">PRs welcome. Read <code>CONTRIBUTING.md</code> for the standards.</p>
-              <a href="https://github.com/cemililik/ForgeLM/blob/main/CONTRIBUTING.md" target="_blank" rel="noopener" data-i18n="contact.channel.contribute_cta">Read the guide →</a>
+              <a href="https://github.com/HodeTech/ForgeLM/blob/main/CONTRIBUTING.md" target="_blank" rel="noopener" data-i18n="contact.channel.contribute_cta">Read the guide →</a>
             </div>
           </li>
         </ul>
@@ -268,10 +268,10 @@ <h4 data-i18n="common.footer.product">Product</h4>
       <div class="footer-col">
         <h4 data-i18n="common.footer.community">Community</h4>
         <ul>
-          <li><a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
         </ul>
       </div>
 
diff --git a/site/features.html b/site/features.html
index 0d365f71..2aa612d3 100644
--- a/site/features.html
+++ b/site/features.html
@@ -68,7 +68,7 @@
   "name": "ForgeLM",
   "url": "https://forgelm.dev/",
   "sameAs": [
-    "https://github.com/cemililik/ForgeLM",
+    "https://github.com/HodeTech/ForgeLM",
     "https://pypi.org/project/forgelm/"
   ]
 }
@@ -448,7 +448,7 @@ <h2 data-i18n="features.cta.title">Want to see it in YAML?</h2>
       <p data-i18n="features.cta.body">Every feature on this page maps to a field on a single YAML config.</p>
       <div class="cta-actions">
         <a href="quickstart.html" class="btn btn-primary" data-i18n="features.cta.btn">Open the Quickstart</a>
-        <a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener" class="btn btn-ghost">GitHub</a>
+        <a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener" class="btn btn-ghost">GitHub</a>
       </div>
     </div>
   </div>
@@ -484,10 +484,10 @@ <h4 data-i18n="common.footer.product">Product</h4>
       <div class="footer-col">
         <h4 data-i18n="common.footer.community">Community</h4>
         <ul>
-          <li><a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
         </ul>
       </div>
 
diff --git a/site/guide.html b/site/guide.html
index 2cd5723d..5dc9ccc1 100644
--- a/site/guide.html
+++ b/site/guide.html
@@ -74,7 +74,7 @@
   "name": "ForgeLM",
   "url": "https://forgelm.dev/",
   "sameAs": [
-    "https://github.com/cemililik/ForgeLM",
+    "https://github.com/HodeTech/ForgeLM",
     "https://pypi.org/project/forgelm/"
   ]
 }
@@ -208,10 +208,10 @@ <h4 data-i18n="common.footer.product">Product</h4>
       <div class="footer-col">
         <h4 data-i18n="common.footer.community">Community</h4>
         <ul>
-          <li><a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
         </ul>
       </div>
 
diff --git a/site/index.html b/site/index.html
index 5f21ba91..e58d064e 100644
--- a/site/index.html
+++ b/site/index.html
@@ -68,7 +68,7 @@
   "name": "ForgeLM",
   "url": "https://forgelm.dev/",
   "sameAs": [
-    "https://github.com/cemililik/ForgeLM",
+    "https://github.com/HodeTech/ForgeLM",
     "https://pypi.org/project/forgelm/"
   ]
 }
@@ -123,7 +123,7 @@
         <svg class="icon-moon" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M21 12.79A9 9 0 1 1 11.21 3 7 7 0 0 0 21 12.79z"/></svg>
         <svg class="icon-sun" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="12" cy="12" r="4"/><path d="M12 2v2M12 20v2M4.93 4.93l1.41 1.41M17.66 17.66l1.41 1.41M2 12h2M20 12h2M4.93 19.07l1.41-1.41M17.66 6.34l1.41-1.41"/></svg>
       </button>
-      <a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener" class="btn btn-secondary btn-sm">
+      <a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener" class="btn btn-secondary btn-sm">
         <svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M12 0c-6.626 0-12 5.373-12 12 0 5.302 3.438 9.8 8.207 11.387.599.111.793-.261.793-.577v-2.234c-3.338.726-4.033-1.416-4.033-1.416-.546-1.387-1.333-1.756-1.333-1.756-1.089-.745.083-.729.083-.729 1.205.084 1.839 1.237 1.839 1.237 1.07 1.834 2.807 1.304 3.492.997.107-.775.418-1.305.762-1.604-2.665-.305-5.467-1.334-5.467-5.931 0-1.311.469-2.381 1.236-3.221-.124-.303-.535-1.524.117-3.176 0 0 1.008-.322 3.301 1.23.957-.266 1.983-.399 3.003-.404 1.02.005 2.047.138 3.006.404 2.291-1.552 3.297-1.23 3.297-1.23.653 1.653.242 2.874.118 3.176.77.84 1.235 1.911 1.235 3.221 0 4.609-2.807 5.624-5.479 5.921.43.372.823 1.102.823 2.222v3.293c0 .319.192.694.801.576 4.765-1.589 8.199-6.086 8.199-11.386 0-6.627-5.373-12-12-12z"/></svg>
         GitHub
       </a>
@@ -157,7 +157,7 @@ <h2 id="hero-slide-engineer-title" data-i18n-html="home.hero.engineer.title">YAM
               <svg width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><polygon points="5 3 19 12 5 21 5 3"/></svg>
               <span data-i18n="home.hero.engineer.cta1">Get started</span>
             </a>
-            <a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener" class="btn btn-secondary">
+            <a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener" class="btn btn-secondary">
               <svg width="18" height="18" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M12 0c-6.626 0-12 5.373-12 12 0 5.302 3.438 9.8 8.207 11.387.599.111.793-.261.793-.577v-2.234c-3.338.726-4.033-1.416-4.033-1.416-.546-1.387-1.333-1.756-1.333-1.756-1.089-.745.083-.729.083-.729 1.205.084 1.839 1.237 1.839 1.237 1.07 1.834 2.807 1.304 3.492.997.107-.775.418-1.305.762-1.604-2.665-.305-5.467-1.334-5.467-5.931 0-1.311.469-2.381 1.236-3.221-.124-.303-.535-1.524.117-3.176 0 0 1.008-.322 3.301 1.23.957-.266 1.983-.399 3.003-.404 1.02.005 2.047.138 3.006.404 2.291-1.552 3.297-1.23 3.297-1.23.653 1.653.242 2.874.118 3.176.77.84 1.235 1.911 1.235 3.221 0 4.609-2.807 5.624-5.479 5.921.43.372.823 1.102.823 2.222v3.293c0 .319.192.694.801.576 4.765-1.589 8.199-6.086 8.199-11.386 0-6.627-5.373-12-12-12z"/></svg>
               <span data-i18n="home.hero.engineer.cta2">View on GitHub</span>
             </a>
@@ -202,7 +202,7 @@ <h2 id="hero-slide-pipeline-title" data-i18n-html="home.hero.pipeline.title">SFT
               <svg width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M3 5h6a3 3 0 0 1 3 3v8a3 3 0 0 0 3 3h6"/><circle cx="3" cy="5" r="1.5"/><circle cx="12" cy="11" r="1.5"/><circle cx="21" cy="19" r="1.5"/></svg>
               <span data-i18n="home.hero.pipeline.cta1">Read the pipeline guide</span>
             </a>
-            <a href="https://github.com/cemililik/ForgeLM/blob/main/docs/guides/pipeline.md" class="btn btn-secondary">
+            <a href="https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/pipeline.md" class="btn btn-secondary">
               <span data-i18n="home.hero.pipeline.cta2">See the YAML example</span>
             </a>
           </div>
@@ -666,7 +666,7 @@ <h2 data-i18n-html="home.cta.title">Ship your next fine-tune in <span class="tex
       <p data-i18n="home.cta.body">Pick a template, point it at your data, watch the audit report go green.</p>
       <div class="cta-actions">
         <a href="quickstart.html" class="btn btn-primary" data-i18n="home.cta.btn1">Quickstart in 5 minutes</a>
-        <a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener" class="btn btn-ghost" data-i18n="home.cta.btn2">Star on GitHub</a>
+        <a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener" class="btn btn-ghost" data-i18n="home.cta.btn2">Star on GitHub</a>
       </div>
     </div>
   </div>
@@ -703,10 +703,10 @@ <h4 data-i18n="common.footer.product">Product</h4>
       <div class="footer-col">
         <h4 data-i18n="common.footer.community">Community</h4>
         <ul>
-          <li><a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
         </ul>
       </div>
 
diff --git a/site/js/guide.js b/site/js/guide.js
index 2a823601..9cfa90b6 100644
--- a/site/js/guide.js
+++ b/site/js/guide.js
@@ -21,7 +21,7 @@
   'use strict';
 
   var GUIDE_BASE = 'guide.html';
-  var GH_EDIT_BASE = 'https://github.com/cemililik/ForgeLM/edit/main/docs/usermanuals';
+  var GH_EDIT_BASE = 'https://github.com/HodeTech/ForgeLM/edit/main/docs/usermanuals';
   var DEFAULT_ROUTE = 'getting-started/introduction';
 
   var state = {
diff --git a/site/js/translations.js b/site/js/translations.js
index 604cf724..ed4e376b 100644
--- a/site/js/translations.js
+++ b/site/js/translations.js
@@ -3882,7 +3882,7 @@
     "compliance.iso.lineage.body":"<code>data_provenance.json</code> (SHA-256 fingerprint + size + mtime + HF Hub revision pin) and <code>data_governance_report.json</code> (collection method, annotation process, known biases, personal-data flag, DPIA completion) cover the lineage questions an auditor asks first.",
     "compliance.iso.supply.title":"Supply chain",
     "compliance.iso.supply.body": "CycloneDX 1.5 SBOM emitted per release tag for every (OS x Python-version) cell of the publish matrix. Wave 4 added <code>pip-audit</code> nightly + <code>bandit</code> in CI for static + dynamic security scanning of the build itself.",
-    "compliance.iso.cookbook":    "For the full audit cookbook, including 8 audit-floor questions and a 93-control coverage map, see <a href=\"https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
+    "compliance.iso.cookbook":    "For the full audit cookbook, including 8 audit-floor questions and a 93-control coverage map, see <a href=\"https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
     "compliance.artifact.eyebrow":"What you get on disk",
     "compliance.artifact.title":  "A run's compliance footprint",
     "compliance.artifact.lead":   "After every successful (or failed) run, this is what lands in your output directory.",
@@ -3941,7 +3941,7 @@
     "compliance.iso.lineage.body":"<code>data_provenance.json</code> (SHA-256 parmak izi + boyut + mtime + HF Hub revision pin) ve <code>data_governance_report.json</code> (toplama yöntemi, anotasyon süreci, bilinen bias, kişisel-veri bayrağı, DPIA tamamlanması) — denetçinin önce sorduğu köken sorularını kapsar.",
     "compliance.iso.supply.title":"Tedarik zinciri",
     "compliance.iso.supply.body": "Publish matrisinin her (OS x Python-version) hücresi için release tag başına CycloneDX 1.5 SBOM. Wave 4, build'in kendisi için statik + dinamik güvenlik taraması olarak gecelik <code>pip-audit</code> + CI'da <code>bandit</code> ekledi.",
-    "compliance.iso.cookbook":    "8 audit-floor sorusu ve 93 kontrol kapsama haritası dahil tam audit cookbook için bkz. <a href=\"https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
+    "compliance.iso.cookbook":    "8 audit-floor sorusu ve 93 kontrol kapsama haritası dahil tam audit cookbook için bkz. <a href=\"https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
     "compliance.artifact.eyebrow":"Diskte ne elde edersiniz",
     "compliance.artifact.title":  "Bir koşunun uyumluluk ayak izi",
     "compliance.artifact.lead":   "Her başarılı (veya başarısız) koşudan sonra çıktı dizininize bunlar düşer.",
@@ -4342,7 +4342,7 @@
     "privacy.header.eyebrow":     "Privacy",
     "privacy.header.title":       "Privacy policy",
     "privacy.header.lead":        "ForgeLM is open-source software you run on your own infrastructure. This page covers what this <em>website</em> does — not the toolkit itself.",
-    "privacy.body":               "<h2>Short version</h2><p>This site is static HTML. We do not run analytics, tracking pixels, advertising trackers, A/B tests, fingerprinting, or any third-party telemetry. Three third-party requests can happen here: <strong>Google Fonts</strong> is fetched on every page load (the <em>Inter</em> and <em>JetBrains Mono</em> typefaces); <strong>Mermaid</strong> is loaded from jsDelivr on the <a href=\"guide.html\">Guide page</a> only (to render diagrams); and <strong>Formspree</strong> only when you submit the contact form. All three are detailed below; nothing else.</p><h2>What we collect</h2><h3>From normal browsing</h3><p>Nothing. No cookies are set. Two values are stored in <code>localStorage</code> on your device:</p><ul><li><code>forgelm-lang</code> — your chosen interface language (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — your chosen colour theme (<code>dark</code> or <code>light</code>).</li></ul><p>Both stay on your device and are never transmitted. Clearing your browser storage removes them.</p><h3>From the contact form</h3><p>When you submit the form on the Contact page, the values you typed (name, email, organisation, topic, subject, message) are sent to Formspree, which forwards them to the project maintainer. Formspree's privacy practices are governed by their own policy at <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>Your email is used <strong>only</strong> to reply to your message. We do not add it to a mailing list, do not share it with third parties, and do not retain it after the conversation is resolved.</p><h2>Hosting</h2><p>This site is served as static files. Your browser will exchange standard request headers (User-Agent, Accept-Language, IP address) with whichever CDN / web server hosts the files; that exchange is governed by the hosting provider's privacy practices and is not under ForgeLM's control. We do not log this traffic ourselves.</p><h2>Third-party assets</h2><p>The site loads:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — the <em>Inter</em> and <em>JetBrains Mono</em> typefaces. Google may log requests as described in their privacy policy.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 is loaded on the <a href=\"guide.html\">Guide page only</a> to render the architecture / flow diagrams. jsDelivr may log requests as described in their privacy policy.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — only when you submit the contact form, as described above.</li></ul><p>Nothing else is loaded from a third party. There is no Google Analytics, no Facebook pixel, no Hotjar, no Mixpanel, no whatever-the-current-tracker is.</p><h2>Children</h2><p>This site is aimed at developers, ML engineers, and compliance professionals. It is not directed at children under 16.</p><h2>Your rights (GDPR / KVKK)</h2><p>If you believe we hold personal data about you and you want it accessed, corrected, or deleted, write to us via the contact form (or <a href=\"https://github.com/cemililik/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>) and we will respond within 30 days. Because the only personal data we hold is what you sent in the contact form, deletion is straightforward: we delete the email thread.</p><h2>The toolkit itself</h2><p>The <strong>ForgeLM</strong> Python package — installed via <code>pip install forgelm==0.5.5</code> — does not phone home. It does not collect telemetry, does not send usage data anywhere, and works offline (air-gap-capable). Models, datasets, and tokenizers you reference in your YAML config are downloaded only at your explicit request and only from sources you specify.</p><h2>Data-subject rights you can ship in your own pipeline</h2><p>If your organisation deploys ForgeLM, the toolkit gives you concrete primitives for the data-subject rights side of GDPR: <code>forgelm reverse-pii</code> scans the corpus for plaintext residuals or salted-digest matches of a subject identifier and reports every row where they appear (Article 15 access), and <code>forgelm purge</code> deletes those rows from your training corpora and stamps the deletion in the append-only audit log (Article 17 erasure). On top of that, ForgeLM is aligned with ISO 27001 / SOC 2 Type II controls — see the <a href=\"compliance.html\">Compliance page</a> for the full evidence map.</p><h2>Changes</h2><p>If we update this page, the date at the top changes. Material changes are noted in the project's <code>CHANGELOG.md</code>.</p><h2>Questions</h2><p>Open the <a href=\"contact.html\">contact form</a> or a <a href=\"https://github.com/cemililik/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>.</p>"
+    "privacy.body":               "<h2>Short version</h2><p>This site is static HTML. We do not run analytics, tracking pixels, advertising trackers, A/B tests, fingerprinting, or any third-party telemetry. Three third-party requests can happen here: <strong>Google Fonts</strong> is fetched on every page load (the <em>Inter</em> and <em>JetBrains Mono</em> typefaces); <strong>Mermaid</strong> is loaded from jsDelivr on the <a href=\"guide.html\">Guide page</a> only (to render diagrams); and <strong>Formspree</strong> only when you submit the contact form. All three are detailed below; nothing else.</p><h2>What we collect</h2><h3>From normal browsing</h3><p>Nothing. No cookies are set. Two values are stored in <code>localStorage</code> on your device:</p><ul><li><code>forgelm-lang</code> — your chosen interface language (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — your chosen colour theme (<code>dark</code> or <code>light</code>).</li></ul><p>Both stay on your device and are never transmitted. Clearing your browser storage removes them.</p><h3>From the contact form</h3><p>When you submit the form on the Contact page, the values you typed (name, email, organisation, topic, subject, message) are sent to Formspree, which forwards them to the project maintainer. Formspree's privacy practices are governed by their own policy at <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>Your email is used <strong>only</strong> to reply to your message. We do not add it to a mailing list, do not share it with third parties, and do not retain it after the conversation is resolved.</p><h2>Hosting</h2><p>This site is served as static files. Your browser will exchange standard request headers (User-Agent, Accept-Language, IP address) with whichever CDN / web server hosts the files; that exchange is governed by the hosting provider's privacy practices and is not under ForgeLM's control. We do not log this traffic ourselves.</p><h2>Third-party assets</h2><p>The site loads:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — the <em>Inter</em> and <em>JetBrains Mono</em> typefaces. Google may log requests as described in their privacy policy.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 is loaded on the <a href=\"guide.html\">Guide page only</a> to render the architecture / flow diagrams. jsDelivr may log requests as described in their privacy policy.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — only when you submit the contact form, as described above.</li></ul><p>Nothing else is loaded from a third party. There is no Google Analytics, no Facebook pixel, no Hotjar, no Mixpanel, no whatever-the-current-tracker is.</p><h2>Children</h2><p>This site is aimed at developers, ML engineers, and compliance professionals. It is not directed at children under 16.</p><h2>Your rights (GDPR / KVKK)</h2><p>If you believe we hold personal data about you and you want it accessed, corrected, or deleted, write to us via the contact form (or <a href=\"https://github.com/HodeTech/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>) and we will respond within 30 days. Because the only personal data we hold is what you sent in the contact form, deletion is straightforward: we delete the email thread.</p><h2>The toolkit itself</h2><p>The <strong>ForgeLM</strong> Python package — installed via <code>pip install forgelm</code> — does not phone home. It does not collect telemetry, does not send usage data anywhere, and works offline (air-gap-capable). Models, datasets, and tokenizers you reference in your YAML config are downloaded only at your explicit request and only from sources you specify.</p><h2>Data-subject rights you can ship in your own pipeline</h2><p>If your organisation deploys ForgeLM, the toolkit gives you concrete primitives for the data-subject rights side of GDPR: <code>forgelm reverse-pii</code> scans the corpus for plaintext residuals or salted-digest matches of a subject identifier and reports every row where they appear (Article 15 access), and <code>forgelm purge</code> deletes those rows from your training corpora and stamps the deletion in the append-only audit log (Article 17 erasure). On top of that, ForgeLM is aligned with ISO 27001 / SOC 2 Type II controls — see the <a href=\"compliance.html\">Compliance page</a> for the full evidence map.</p><h2>Changes</h2><p>If we update this page, the date at the top changes. Material changes are noted in the project's <code>CHANGELOG.md</code>.</p><h2>Questions</h2><p>Open the <a href=\"contact.html\">contact form</a> or a <a href=\"https://github.com/HodeTech/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>.</p>"
   });
 
   Object.assign(T.tr, {
@@ -4351,7 +4351,7 @@
     "privacy.header.eyebrow":     "Gizlilik",
     "privacy.header.title":       "Gizlilik politikası",
     "privacy.header.lead":        "ForgeLM, kendi altyapınızda çalıştırdığınız açık kaynaklı bir yazılımdır. Bu sayfa <em>web sitesinin</em> ne yaptığını açıklar — toolkit'i değil.",
-    "privacy.body":               "<h2>Kısa versiyon</h2><p>Bu site statik HTML'dir. Analitik, izleme pixel'i, reklam takipçisi, A/B test, fingerprinting veya üçüncü-taraf telemetri çalıştırmıyoruz. Burada üç üçüncü-taraf isteği gerçekleşebilir: <strong>Google Fonts</strong> her sayfa yüklemesinde alınır (<em>Inter</em> ve <em>JetBrains Mono</em> yazıtipleri); <strong>Mermaid</strong> yalnızca <a href=\"guide.html\">Rehber sayfasında</a> jsDelivr'dan yüklenir (diyagramları render etmek için); ve <strong>Formspree</strong> yalnızca iletişim formunu gönderdiğinizde. Üçü de aşağıda detaylıdır; başka hiçbir şey yok.</p><h2>Neler topluyoruz</h2><h3>Normal gezinmeden</h3><p>Hiçbir şey. Hiçbir cookie set edilmez. Cihazınızda yalnızca iki değer <code>localStorage</code>'a yazılır:</p><ul><li><code>forgelm-lang</code> — seçtiğiniz arayüz dili (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — seçtiğiniz renk teması (<code>dark</code> veya <code>light</code>).</li></ul><p>İkisi de cihazınızda kalır ve hiçbir yere iletilmez. Tarayıcı depolamasını temizlemek bunları siler.</p><h3>İletişim formundan</h3><p>İletişim sayfasındaki formu gönderdiğinizde girdiğiniz değerler (isim, e-posta, organizasyon, konu başlığı, konu, mesaj) Formspree'ye gönderilir; Formspree de bunları proje yürütücüsüne iletir. Formspree'nin gizlilik uygulamaları kendi politikasıyla yönetilir: <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>E-postanız <strong>yalnızca</strong> mesajınıza cevap vermek için kullanılır. Mailing listesine eklenmez, üçüncü taraflarla paylaşılmaz, görüşme sona erdikten sonra saklanmaz.</p><h2>Hosting</h2><p>Site statik dosya olarak servis edilir. Tarayıcınız, dosyaları barındıran CDN / web sunucusuyla standart istek header'larını (User-Agent, Accept-Language, IP) takas eder; bu takas hosting sağlayıcısının gizlilik uygulamalarıyla yönetilir ve ForgeLM'in kontrolünde değildir. Bu trafiği biz kendimiz loglamıyoruz.</p><h2>Üçüncü-taraf varlıklar</h2><p>Site şunları yükler:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — <em>Inter</em> ve <em>JetBrains Mono</em> yazıtipleri. Google istekleri kendi gizlilik politikasında açıklandığı gibi loglayabilir.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 yalnızca <a href=\"guide.html\">Rehber sayfasında</a> mimari / akış diyagramlarını render etmek için yüklenir. jsDelivr istekleri kendi gizlilik politikasında açıklandığı gibi loglayabilir.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — yalnızca iletişim formunu gönderdiğinizde, yukarıda açıklandığı gibi.</li></ul><p>Üçüncü taraftan başka hiçbir şey yüklenmez. Google Analytics yok, Facebook pixel yok, Hotjar yok, Mixpanel yok, güncel-takipçi-her-neyse yok.</p><h2>Çocuklar</h2><p>Bu site geliştiricilere, ML mühendislerine ve compliance profesyonellerine yöneliktir. 16 yaş altındaki çocukları hedeflemez.</p><h2>Haklarınız (KVKK / GDPR)</h2><p>Hakkınızda kişisel veri tuttuğumuzu düşünüyor ve erişim, düzeltme veya silme istiyorsanız iletişim formundan (veya <a href=\"https://github.com/cemililik/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a> üzerinden) bize yazın; 30 gün içinde döneriz. Tuttuğumuz tek kişisel veri iletişim formundan gönderdikleriniz olduğu için silme kolay: e-posta thread'ini sileriz.</p><h2>Toolkit'in kendisi</h2><p><code>pip install forgelm==0.5.5</code> ile kurulan <strong>ForgeLM</strong> Python paketi eve telefon etmez. Telemetri toplamaz, kullanım verisi göndermez, offline çalışır (air-gap uyumlu). YAML konfigürasyonunuzda referans verdiğiniz modeller, veri setleri ve tokenizer'lar yalnızca açık talebinizle ve yalnızca sizin belirttiğiniz kaynaklardan indirilir.</p><h2>Kendi pipeline'ınızda sevk edebileceğiniz veri sahibi hakları</h2><p>Organizasyonunuz ForgeLM dağıtıyorsa, toolkit GDPR'ın veri sahibi hakları tarafına somut primitifler sunar: <code>forgelm reverse-pii</code> bir özne tanımlayıcısının düz-metin kalıntılarını veya tuzlanmış-digest eşleşmelerini corpus'ta tarar ve geçtiği her satırı raporlar (Madde 15 erişim) ve <code>forgelm purge</code> bu satırları eğitim corpus'unuzdan siler ve silmeyi append-only audit log'a damgalar (Madde 17 silme). Üstüne, ForgeLM ISO 27001 / SOC 2 Type II kontrolleriyle hizalıdır — tam kanıt haritası için <a href=\"compliance.html\">Uyumluluk sayfası</a>na bakın.</p><h2>Değişiklikler</h2><p>Bu sayfayı güncellersek yukarıdaki tarih değişir. Maddi değişiklikler projenin <code>CHANGELOG.md</code>'sine düşer.</p><h2>Sorular</h2><p><a href=\"contact.html\">İletişim formunu</a> veya bir <a href=\"https://github.com/cemililik/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>'ı açın.</p>"
+    "privacy.body":               "<h2>Kısa versiyon</h2><p>Bu site statik HTML'dir. Analitik, izleme pixel'i, reklam takipçisi, A/B test, fingerprinting veya üçüncü-taraf telemetri çalıştırmıyoruz. Burada üç üçüncü-taraf isteği gerçekleşebilir: <strong>Google Fonts</strong> her sayfa yüklemesinde alınır (<em>Inter</em> ve <em>JetBrains Mono</em> yazıtipleri); <strong>Mermaid</strong> yalnızca <a href=\"guide.html\">Rehber sayfasında</a> jsDelivr'dan yüklenir (diyagramları render etmek için); ve <strong>Formspree</strong> yalnızca iletişim formunu gönderdiğinizde. Üçü de aşağıda detaylıdır; başka hiçbir şey yok.</p><h2>Neler topluyoruz</h2><h3>Normal gezinmeden</h3><p>Hiçbir şey. Hiçbir cookie set edilmez. Cihazınızda yalnızca iki değer <code>localStorage</code>'a yazılır:</p><ul><li><code>forgelm-lang</code> — seçtiğiniz arayüz dili (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — seçtiğiniz renk teması (<code>dark</code> veya <code>light</code>).</li></ul><p>İkisi de cihazınızda kalır ve hiçbir yere iletilmez. Tarayıcı depolamasını temizlemek bunları siler.</p><h3>İletişim formundan</h3><p>İletişim sayfasındaki formu gönderdiğinizde girdiğiniz değerler (isim, e-posta, organizasyon, konu başlığı, konu, mesaj) Formspree'ye gönderilir; Formspree de bunları proje yürütücüsüne iletir. Formspree'nin gizlilik uygulamaları kendi politikasıyla yönetilir: <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>E-postanız <strong>yalnızca</strong> mesajınıza cevap vermek için kullanılır. Mailing listesine eklenmez, üçüncü taraflarla paylaşılmaz, görüşme sona erdikten sonra saklanmaz.</p><h2>Hosting</h2><p>Site statik dosya olarak servis edilir. Tarayıcınız, dosyaları barındıran CDN / web sunucusuyla standart istek header'larını (User-Agent, Accept-Language, IP) takas eder; bu takas hosting sağlayıcısının gizlilik uygulamalarıyla yönetilir ve ForgeLM'in kontrolünde değildir. Bu trafiği biz kendimiz loglamıyoruz.</p><h2>Üçüncü-taraf varlıklar</h2><p>Site şunları yükler:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — <em>Inter</em> ve <em>JetBrains Mono</em> yazıtipleri. Google istekleri kendi gizlilik politikasında açıklandığı gibi loglayabilir.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 yalnızca <a href=\"guide.html\">Rehber sayfasında</a> mimari / akış diyagramlarını render etmek için yüklenir. jsDelivr istekleri kendi gizlilik politikasında açıklandığı gibi loglayabilir.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — yalnızca iletişim formunu gönderdiğinizde, yukarıda açıklandığı gibi.</li></ul><p>Üçüncü taraftan başka hiçbir şey yüklenmez. Google Analytics yok, Facebook pixel yok, Hotjar yok, Mixpanel yok, güncel-takipçi-her-neyse yok.</p><h2>Çocuklar</h2><p>Bu site geliştiricilere, ML mühendislerine ve compliance profesyonellerine yöneliktir. 16 yaş altındaki çocukları hedeflemez.</p><h2>Haklarınız (KVKK / GDPR)</h2><p>Hakkınızda kişisel veri tuttuğumuzu düşünüyor ve erişim, düzeltme veya silme istiyorsanız iletişim formundan (veya <a href=\"https://github.com/HodeTech/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a> üzerinden) bize yazın; 30 gün içinde döneriz. Tuttuğumuz tek kişisel veri iletişim formundan gönderdikleriniz olduğu için silme kolay: e-posta thread'ini sileriz.</p><h2>Toolkit'in kendisi</h2><p><code>pip install forgelm</code> ile kurulan <strong>ForgeLM</strong> Python paketi eve telefon etmez. Telemetri toplamaz, kullanım verisi göndermez, offline çalışır (air-gap uyumlu). YAML konfigürasyonunuzda referans verdiğiniz modeller, veri setleri ve tokenizer'lar yalnızca açık talebinizle ve yalnızca sizin belirttiğiniz kaynaklardan indirilir.</p><h2>Kendi pipeline'ınızda sevk edebileceğiniz veri sahibi hakları</h2><p>Organizasyonunuz ForgeLM dağıtıyorsa, toolkit GDPR'ın veri sahibi hakları tarafına somut primitifler sunar: <code>forgelm reverse-pii</code> bir özne tanımlayıcısının düz-metin kalıntılarını veya tuzlanmış-digest eşleşmelerini corpus'ta tarar ve geçtiği her satırı raporlar (Madde 15 erişim) ve <code>forgelm purge</code> bu satırları eğitim corpus'unuzdan siler ve silmeyi append-only audit log'a damgalar (Madde 17 silme). Üstüne, ForgeLM ISO 27001 / SOC 2 Type II kontrolleriyle hizalıdır — tam kanıt haritası için <a href=\"compliance.html\">Uyumluluk sayfası</a>na bakın.</p><h2>Değişiklikler</h2><p>Bu sayfayı güncellersek yukarıdaki tarih değişir. Maddi değişiklikler projenin <code>CHANGELOG.md</code>'sine düşer.</p><h2>Sorular</h2><p><a href=\"contact.html\">İletişim formunu</a> veya bir <a href=\"https://github.com/HodeTech/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>'ı açın.</p>"
   });
 
   Object.assign(T.de, {
@@ -4360,7 +4360,7 @@
     "privacy.header.eyebrow":     "Datenschutz",
     "privacy.header.title":       "Datenschutzerklärung",
     "privacy.header.lead":        "ForgeLM ist Open-Source-Software, die Sie auf Ihrer eigenen Infrastruktur betreiben. Diese Seite behandelt, was diese <em>Website</em> tut — nicht das Toolkit selbst.",
-    "privacy.body":               "<h2>Kurzversion</h2><p>Diese Seite ist statisches HTML. Wir betreiben keine Analytik, keine Tracking-Pixel, keine Werbe-Tracker, keine A/B-Tests, kein Fingerprinting und keine Drittanbieter-Telemetrie. Hier können drei Drittanbieter-Anfragen erfolgen: <strong>Google Fonts</strong> wird bei jedem Seitenaufruf abgerufen (die Schriften <em>Inter</em> und <em>JetBrains Mono</em>); <strong>Mermaid</strong> wird ausschließlich auf der <a href=\"guide.html\">Guide-Seite</a> von jsDelivr geladen (zum Rendern der Diagramme); und <strong>Formspree</strong> nur, wenn Sie das Kontaktformular absenden. Alle drei werden unten detailliert beschrieben; sonst nichts.</p><h2>Was wir erfassen</h2><h3>Beim normalen Surfen</h3><p>Nichts. Es werden keine Cookies gesetzt. Auf Ihrem Gerät werden zwei Werte in <code>localStorage</code> gespeichert:</p><ul><li><code>forgelm-lang</code> — Ihre gewählte Oberflächensprache (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — Ihr gewähltes Farbschema (<code>dark</code> oder <code>light</code>).</li></ul><p>Beide bleiben auf Ihrem Gerät und werden nie übertragen. Das Leeren Ihres Browser-Speichers entfernt sie.</p><h3>Vom Kontaktformular</h3><p>Wenn Sie das Formular auf der Kontakt-Seite absenden, werden die eingegebenen Werte (Name, E-Mail, Organisation, Thema, Betreff, Nachricht) an Formspree gesendet, das sie an den Projekt-Maintainer weiterleitet. Die Datenschutzpraktiken von Formspree unterliegen ihrer eigenen Richtlinie unter <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>Ihre E-Mail wird <strong>ausschließlich</strong> zur Beantwortung Ihrer Nachricht verwendet. Wir nehmen sie nicht in eine Mailingliste auf, geben sie nicht an Dritte weiter und behalten sie nach Abschluss der Konversation nicht zurück.</p><h2>Hosting</h2><p>Die Seite wird als statische Dateien ausgeliefert. Ihr Browser tauscht Standard-Request-Header (User-Agent, Accept-Language, IP-Adresse) mit dem CDN / Webserver aus, der die Dateien hostet; dieser Austausch unterliegt den Datenschutzpraktiken des Hosting-Anbieters und liegt nicht in der Kontrolle von ForgeLM. Wir loggen diesen Verkehr selbst nicht.</p><h2>Drittanbieter-Assets</h2><p>Die Seite lädt:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — die Schriften <em>Inter</em> und <em>JetBrains Mono</em>. Google kann Anfragen wie in seiner Datenschutzrichtlinie beschrieben loggen.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 wird ausschließlich auf der <a href=\"guide.html\">Guide-Seite</a> geladen, um die Architektur- / Flussdiagramme zu rendern. jsDelivr kann Anfragen wie in seiner Datenschutzrichtlinie beschrieben loggen.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — nur wenn Sie das Kontaktformular absenden, wie oben beschrieben.</li></ul><p>Sonst wird nichts von Drittanbietern geladen. Kein Google Analytics, kein Facebook-Pixel, kein Hotjar, kein Mixpanel, kein wie-auch-immer-aktueller-Tracker.</p><h2>Kinder</h2><p>Diese Seite richtet sich an Entwickler, ML-Ingenieure und Compliance-Fachleute. Sie richtet sich nicht an Kinder unter 16.</p><h2>Ihre Rechte (DSGVO / KVKK)</h2><p>Wenn Sie der Meinung sind, dass wir personenbezogene Daten über Sie speichern, und Sie Auskunft, Berichtigung oder Löschung wünschen, schreiben Sie uns über das Kontaktformular (oder <a href=\"https://github.com/cemililik/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>); wir antworten innerhalb von 30 Tagen. Da die einzigen personenbezogenen Daten, die wir halten, das sind, was Sie im Kontaktformular gesendet haben, ist die Löschung einfach: Wir löschen den E-Mail-Thread.</p><h2>Das Toolkit selbst</h2><p>Das <strong>ForgeLM</strong>-Python-Paket — installiert über <code>pip install forgelm==0.5.5</code> — telefoniert nicht nach Hause. Es sammelt keine Telemetrie, sendet keine Nutzungsdaten irgendwohin und arbeitet offline (Air-Gap-fähig). Modelle, Datensätze und Tokenizer, die Sie in Ihrer YAML-Konfiguration referenzieren, werden nur auf Ihre ausdrückliche Anforderung und nur aus von Ihnen angegebenen Quellen heruntergeladen.</p><h2>Datensubjekt-Rechte, die Sie in Ihrer eigenen Pipeline ausliefern können</h2><p>Wenn Ihre Organisation ForgeLM einsetzt, liefert das Toolkit konkrete Primitive für die Datensubjekt-Rechte-Seite der DSGVO: <code>forgelm reverse-pii</code> durchsucht den Korpus nach Klartextresten oder gesalzenen Digest-Treffern einer Subjekt-Kennung und meldet jede Zeile, in der diese Person erscheint (Artikel 15 Auskunft), und <code>forgelm purge</code> löscht diese Zeilen aus Ihren Trainingskorpora und stempelt die Löschung in das Append-only-Audit-Log (Artikel 17 Löschung). Darüber hinaus ist ForgeLM mit ISO 27001 / SOC 2 Type II Kontrollen aligned — siehe die <a href=\"compliance.html\">Compliance-Seite</a> für die vollständige Nachweis-Karte.</p><h2>Änderungen</h2><p>Wenn wir diese Seite aktualisieren, ändert sich das Datum oben. Wesentliche Änderungen werden im <code>CHANGELOG.md</code> des Projekts vermerkt.</p><h2>Fragen</h2><p>Öffnen Sie das <a href=\"contact.html\">Kontaktformular</a> oder eine <a href=\"https://github.com/cemililik/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>.</p>"
+    "privacy.body":               "<h2>Kurzversion</h2><p>Diese Seite ist statisches HTML. Wir betreiben keine Analytik, keine Tracking-Pixel, keine Werbe-Tracker, keine A/B-Tests, kein Fingerprinting und keine Drittanbieter-Telemetrie. Hier können drei Drittanbieter-Anfragen erfolgen: <strong>Google Fonts</strong> wird bei jedem Seitenaufruf abgerufen (die Schriften <em>Inter</em> und <em>JetBrains Mono</em>); <strong>Mermaid</strong> wird ausschließlich auf der <a href=\"guide.html\">Guide-Seite</a> von jsDelivr geladen (zum Rendern der Diagramme); und <strong>Formspree</strong> nur, wenn Sie das Kontaktformular absenden. Alle drei werden unten detailliert beschrieben; sonst nichts.</p><h2>Was wir erfassen</h2><h3>Beim normalen Surfen</h3><p>Nichts. Es werden keine Cookies gesetzt. Auf Ihrem Gerät werden zwei Werte in <code>localStorage</code> gespeichert:</p><ul><li><code>forgelm-lang</code> — Ihre gewählte Oberflächensprache (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — Ihr gewähltes Farbschema (<code>dark</code> oder <code>light</code>).</li></ul><p>Beide bleiben auf Ihrem Gerät und werden nie übertragen. Das Leeren Ihres Browser-Speichers entfernt sie.</p><h3>Vom Kontaktformular</h3><p>Wenn Sie das Formular auf der Kontakt-Seite absenden, werden die eingegebenen Werte (Name, E-Mail, Organisation, Thema, Betreff, Nachricht) an Formspree gesendet, das sie an den Projekt-Maintainer weiterleitet. Die Datenschutzpraktiken von Formspree unterliegen ihrer eigenen Richtlinie unter <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>Ihre E-Mail wird <strong>ausschließlich</strong> zur Beantwortung Ihrer Nachricht verwendet. Wir nehmen sie nicht in eine Mailingliste auf, geben sie nicht an Dritte weiter und behalten sie nach Abschluss der Konversation nicht zurück.</p><h2>Hosting</h2><p>Die Seite wird als statische Dateien ausgeliefert. Ihr Browser tauscht Standard-Request-Header (User-Agent, Accept-Language, IP-Adresse) mit dem CDN / Webserver aus, der die Dateien hostet; dieser Austausch unterliegt den Datenschutzpraktiken des Hosting-Anbieters und liegt nicht in der Kontrolle von ForgeLM. Wir loggen diesen Verkehr selbst nicht.</p><h2>Drittanbieter-Assets</h2><p>Die Seite lädt:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — die Schriften <em>Inter</em> und <em>JetBrains Mono</em>. Google kann Anfragen wie in seiner Datenschutzrichtlinie beschrieben loggen.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 wird ausschließlich auf der <a href=\"guide.html\">Guide-Seite</a> geladen, um die Architektur- / Flussdiagramme zu rendern. jsDelivr kann Anfragen wie in seiner Datenschutzrichtlinie beschrieben loggen.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — nur wenn Sie das Kontaktformular absenden, wie oben beschrieben.</li></ul><p>Sonst wird nichts von Drittanbietern geladen. Kein Google Analytics, kein Facebook-Pixel, kein Hotjar, kein Mixpanel, kein wie-auch-immer-aktueller-Tracker.</p><h2>Kinder</h2><p>Diese Seite richtet sich an Entwickler, ML-Ingenieure und Compliance-Fachleute. Sie richtet sich nicht an Kinder unter 16.</p><h2>Ihre Rechte (DSGVO / KVKK)</h2><p>Wenn Sie der Meinung sind, dass wir personenbezogene Daten über Sie speichern, und Sie Auskunft, Berichtigung oder Löschung wünschen, schreiben Sie uns über das Kontaktformular (oder <a href=\"https://github.com/HodeTech/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>); wir antworten innerhalb von 30 Tagen. Da die einzigen personenbezogenen Daten, die wir halten, das sind, was Sie im Kontaktformular gesendet haben, ist die Löschung einfach: Wir löschen den E-Mail-Thread.</p><h2>Das Toolkit selbst</h2><p>Das <strong>ForgeLM</strong>-Python-Paket — installiert über <code>pip install forgelm</code> — telefoniert nicht nach Hause. Es sammelt keine Telemetrie, sendet keine Nutzungsdaten irgendwohin und arbeitet offline (Air-Gap-fähig). Modelle, Datensätze und Tokenizer, die Sie in Ihrer YAML-Konfiguration referenzieren, werden nur auf Ihre ausdrückliche Anforderung und nur aus von Ihnen angegebenen Quellen heruntergeladen.</p><h2>Datensubjekt-Rechte, die Sie in Ihrer eigenen Pipeline ausliefern können</h2><p>Wenn Ihre Organisation ForgeLM einsetzt, liefert das Toolkit konkrete Primitive für die Datensubjekt-Rechte-Seite der DSGVO: <code>forgelm reverse-pii</code> durchsucht den Korpus nach Klartextresten oder gesalzenen Digest-Treffern einer Subjekt-Kennung und meldet jede Zeile, in der diese Person erscheint (Artikel 15 Auskunft), und <code>forgelm purge</code> löscht diese Zeilen aus Ihren Trainingskorpora und stempelt die Löschung in das Append-only-Audit-Log (Artikel 17 Löschung). Darüber hinaus ist ForgeLM mit ISO 27001 / SOC 2 Type II Kontrollen aligned — siehe die <a href=\"compliance.html\">Compliance-Seite</a> für die vollständige Nachweis-Karte.</p><h2>Änderungen</h2><p>Wenn wir diese Seite aktualisieren, ändert sich das Datum oben. Wesentliche Änderungen werden im <code>CHANGELOG.md</code> des Projekts vermerkt.</p><h2>Fragen</h2><p>Öffnen Sie das <a href=\"contact.html\">Kontaktformular</a> oder eine <a href=\"https://github.com/HodeTech/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>.</p>"
   });
 
   Object.assign(T.fr, {
@@ -4369,7 +4369,7 @@
     "privacy.header.eyebrow":     "Confidentialité",
     "privacy.header.title":       "Politique de confidentialité",
     "privacy.header.lead":        "ForgeLM est un logiciel open source que vous exécutez sur votre propre infrastructure. Cette page couvre ce que ce <em>site web</em> fait — pas la boîte à outils elle-même.",
-    "privacy.body":               "<h2>Version courte</h2><p>Ce site est du HTML statique. Nous n'exécutons pas d'analytics, de pixels de tracking, de trackers publicitaires, d'A/B tests, de fingerprinting ou de télémétrie tierce. Trois requêtes tierces peuvent se produire ici : <strong>Google Fonts</strong> est récupéré à chaque chargement de page (les polices <em>Inter</em> et <em>JetBrains Mono</em>) ; <strong>Mermaid</strong> est chargé depuis jsDelivr uniquement sur la <a href=\"guide.html\">page Guide</a> (pour rendre les diagrammes) ; et <strong>Formspree</strong> uniquement lorsque vous soumettez le formulaire de contact. Les trois sont détaillés ci-dessous ; rien d'autre.</p><h2>Ce que nous collectons</h2><h3>De la navigation normale</h3><p>Rien. Aucun cookie n'est défini. Deux valeurs sont stockées dans <code>localStorage</code> sur votre appareil :</p><ul><li><code>forgelm-lang</code> — la langue d'interface choisie (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — votre thème de couleur choisi (<code>dark</code> ou <code>light</code>).</li></ul><p>Les deux restent sur votre appareil et ne sont jamais transmises. Vider le stockage du navigateur les supprime.</p><h3>Du formulaire de contact</h3><p>Lorsque vous soumettez le formulaire sur la page Contact, les valeurs saisies (nom, e-mail, organisation, sujet, objet, message) sont envoyées à Formspree, qui les transmet au mainteneur du projet. Les pratiques de confidentialité de Formspree sont régies par leur propre politique sur <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>Votre e-mail est utilisé <strong>uniquement</strong> pour répondre à votre message. Nous ne l'ajoutons pas à une liste de diffusion, ne le partageons pas avec des tiers et ne le conservons pas après la résolution de la conversation.</p><h2>Hébergement</h2><p>Ce site est servi sous forme de fichiers statiques. Votre navigateur échangera des en-têtes de requête standard (User-Agent, Accept-Language, adresse IP) avec le CDN / serveur web qui héberge les fichiers ; cet échange est régi par les pratiques de confidentialité du fournisseur d'hébergement et n'est pas sous le contrôle de ForgeLM. Nous ne loggons pas ce trafic nous-mêmes.</p><h2>Ressources tierces</h2><p>Le site charge :</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — les polices <em>Inter</em> et <em>JetBrains Mono</em>. Google peut logger les requêtes comme décrit dans sa politique de confidentialité.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 est chargé uniquement sur la <a href=\"guide.html\">page Guide</a> pour rendre les diagrammes d'architecture / flux. jsDelivr peut logger les requêtes comme décrit dans sa politique de confidentialité.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — uniquement lorsque vous soumettez le formulaire de contact, comme décrit ci-dessus.</li></ul><p>Rien d'autre n'est chargé depuis un tiers. Pas de Google Analytics, pas de pixel Facebook, pas de Hotjar, pas de Mixpanel, pas de tracker-du-moment-quel-qu'il-soit.</p><h2>Enfants</h2><p>Ce site s'adresse aux développeurs, ingénieurs ML et professionnels de la conformité. Il n'est pas destiné aux enfants de moins de 16 ans.</p><h2>Vos droits (RGPD / KVKK)</h2><p>Si vous pensez que nous détenons des données personnelles vous concernant et que vous voulez y accéder, les corriger ou les supprimer, écrivez-nous via le formulaire de contact (ou <a href=\"https://github.com/cemililik/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>) et nous répondrons dans les 30 jours. Comme les seules données personnelles que nous détenons sont celles que vous avez envoyées dans le formulaire de contact, la suppression est simple : nous supprimons le fil d'e-mail.</p><h2>La boîte à outils elle-même</h2><p>Le paquet Python <strong>ForgeLM</strong> — installé via <code>pip install forgelm==0.5.5</code> — ne « téléphone pas à la maison ». Il ne collecte pas de télémétrie, n'envoie pas de données d'usage où que ce soit et fonctionne hors-ligne (compatible air-gap). Les modèles, datasets et tokenizers que vous référencez dans votre config YAML ne sont téléchargés qu'à votre demande explicite et uniquement depuis les sources que vous spécifiez.</p><h2>Droits des personnes concernées que vous pouvez livrer dans votre propre pipeline</h2><p>Si votre organisation déploie ForgeLM, le toolkit fournit des primitives concrètes pour le volet droits des personnes concernées du RGPD : <code>forgelm reverse-pii</code> scanne le corpus à la recherche de résidus en clair ou de digests salés d'un identifiant de personne et signale chaque ligne où elle apparaît (Article 15 accès), et <code>forgelm purge</code> supprime ces lignes de vos corpus d'entraînement et estampille la suppression dans le log d'audit append-only (Article 17 effacement). De plus, ForgeLM est aligné avec les contrôles ISO 27001 / SOC 2 Type II — voir la <a href=\"compliance.html\">page Compliance</a> pour la cartographie complète des preuves.</p><h2>Modifications</h2><p>Si nous mettons cette page à jour, la date en haut change. Les changements importants sont notés dans le <code>CHANGELOG.md</code> du projet.</p><h2>Questions</h2><p>Ouvrez le <a href=\"contact.html\">formulaire de contact</a> ou une <a href=\"https://github.com/cemililik/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>.</p>"
+    "privacy.body":               "<h2>Version courte</h2><p>Ce site est du HTML statique. Nous n'exécutons pas d'analytics, de pixels de tracking, de trackers publicitaires, d'A/B tests, de fingerprinting ou de télémétrie tierce. Trois requêtes tierces peuvent se produire ici : <strong>Google Fonts</strong> est récupéré à chaque chargement de page (les polices <em>Inter</em> et <em>JetBrains Mono</em>) ; <strong>Mermaid</strong> est chargé depuis jsDelivr uniquement sur la <a href=\"guide.html\">page Guide</a> (pour rendre les diagrammes) ; et <strong>Formspree</strong> uniquement lorsque vous soumettez le formulaire de contact. Les trois sont détaillés ci-dessous ; rien d'autre.</p><h2>Ce que nous collectons</h2><h3>De la navigation normale</h3><p>Rien. Aucun cookie n'est défini. Deux valeurs sont stockées dans <code>localStorage</code> sur votre appareil :</p><ul><li><code>forgelm-lang</code> — la langue d'interface choisie (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — votre thème de couleur choisi (<code>dark</code> ou <code>light</code>).</li></ul><p>Les deux restent sur votre appareil et ne sont jamais transmises. Vider le stockage du navigateur les supprime.</p><h3>Du formulaire de contact</h3><p>Lorsque vous soumettez le formulaire sur la page Contact, les valeurs saisies (nom, e-mail, organisation, sujet, objet, message) sont envoyées à Formspree, qui les transmet au mainteneur du projet. Les pratiques de confidentialité de Formspree sont régies par leur propre politique sur <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>Votre e-mail est utilisé <strong>uniquement</strong> pour répondre à votre message. Nous ne l'ajoutons pas à une liste de diffusion, ne le partageons pas avec des tiers et ne le conservons pas après la résolution de la conversation.</p><h2>Hébergement</h2><p>Ce site est servi sous forme de fichiers statiques. Votre navigateur échangera des en-têtes de requête standard (User-Agent, Accept-Language, adresse IP) avec le CDN / serveur web qui héberge les fichiers ; cet échange est régi par les pratiques de confidentialité du fournisseur d'hébergement et n'est pas sous le contrôle de ForgeLM. Nous ne loggons pas ce trafic nous-mêmes.</p><h2>Ressources tierces</h2><p>Le site charge :</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — les polices <em>Inter</em> et <em>JetBrains Mono</em>. Google peut logger les requêtes comme décrit dans sa politique de confidentialité.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 est chargé uniquement sur la <a href=\"guide.html\">page Guide</a> pour rendre les diagrammes d'architecture / flux. jsDelivr peut logger les requêtes comme décrit dans sa politique de confidentialité.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — uniquement lorsque vous soumettez le formulaire de contact, comme décrit ci-dessus.</li></ul><p>Rien d'autre n'est chargé depuis un tiers. Pas de Google Analytics, pas de pixel Facebook, pas de Hotjar, pas de Mixpanel, pas de tracker-du-moment-quel-qu'il-soit.</p><h2>Enfants</h2><p>Ce site s'adresse aux développeurs, ingénieurs ML et professionnels de la conformité. Il n'est pas destiné aux enfants de moins de 16 ans.</p><h2>Vos droits (RGPD / KVKK)</h2><p>Si vous pensez que nous détenons des données personnelles vous concernant et que vous voulez y accéder, les corriger ou les supprimer, écrivez-nous via le formulaire de contact (ou <a href=\"https://github.com/HodeTech/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>) et nous répondrons dans les 30 jours. Comme les seules données personnelles que nous détenons sont celles que vous avez envoyées dans le formulaire de contact, la suppression est simple : nous supprimons le fil d'e-mail.</p><h2>La boîte à outils elle-même</h2><p>Le paquet Python <strong>ForgeLM</strong> — installé via <code>pip install forgelm</code> — ne « téléphone pas à la maison ». Il ne collecte pas de télémétrie, n'envoie pas de données d'usage où que ce soit et fonctionne hors-ligne (compatible air-gap). Les modèles, datasets et tokenizers que vous référencez dans votre config YAML ne sont téléchargés qu'à votre demande explicite et uniquement depuis les sources que vous spécifiez.</p><h2>Droits des personnes concernées que vous pouvez livrer dans votre propre pipeline</h2><p>Si votre organisation déploie ForgeLM, le toolkit fournit des primitives concrètes pour le volet droits des personnes concernées du RGPD : <code>forgelm reverse-pii</code> scanne le corpus à la recherche de résidus en clair ou de digests salés d'un identifiant de personne et signale chaque ligne où elle apparaît (Article 15 accès), et <code>forgelm purge</code> supprime ces lignes de vos corpus d'entraînement et estampille la suppression dans le log d'audit append-only (Article 17 effacement). De plus, ForgeLM est aligné avec les contrôles ISO 27001 / SOC 2 Type II — voir la <a href=\"compliance.html\">page Compliance</a> pour la cartographie complète des preuves.</p><h2>Modifications</h2><p>Si nous mettons cette page à jour, la date en haut change. Les changements importants sont notés dans le <code>CHANGELOG.md</code> du projet.</p><h2>Questions</h2><p>Ouvrez le <a href=\"contact.html\">formulaire de contact</a> ou une <a href=\"https://github.com/HodeTech/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>.</p>"
   });
 
   Object.assign(T.es, {
@@ -4378,7 +4378,7 @@
     "privacy.header.eyebrow":     "Privacidad",
     "privacy.header.title":       "Política de privacidad",
     "privacy.header.lead":        "ForgeLM es software de código abierto que ejecuta en su propia infraestructura. Esta página cubre lo que hace este <em>sitio web</em> — no el toolkit en sí.",
-    "privacy.body":               "<h2>Versión corta</h2><p>Este sitio es HTML estático. No ejecutamos analytics, píxeles de tracking, trackers publicitarios, A/B tests, fingerprinting o telemetría de terceros. Aquí pueden ocurrir tres solicitudes a terceros: <strong>Google Fonts</strong> se obtiene en cada carga de página (las tipografías <em>Inter</em> y <em>JetBrains Mono</em>); <strong>Mermaid</strong> se carga desde jsDelivr solo en la <a href=\"guide.html\">página Guía</a> (para renderizar los diagramas); y <strong>Formspree</strong> solo cuando envía el formulario de contacto. Las tres están detalladas abajo; nada más.</p><h2>Qué recopilamos</h2><h3>De la navegación normal</h3><p>Nada. No se establecen cookies. Se almacenan dos valores en <code>localStorage</code> en su dispositivo:</p><ul><li><code>forgelm-lang</code> — su idioma de interfaz elegido (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — su tema de color elegido (<code>dark</code> o <code>light</code>).</li></ul><p>Ambos quedan en su dispositivo y nunca se transmiten. Limpiar el almacenamiento del navegador los elimina.</p><h3>Del formulario de contacto</h3><p>Cuando envía el formulario en la página de Contacto, los valores que escribió (nombre, email, organización, tema, asunto, mensaje) se envían a Formspree, que los reenvía al mantenedor del proyecto. Las prácticas de privacidad de Formspree se rigen por su propia política en <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>Su email se usa <strong>solo</strong> para responder a su mensaje. No lo agregamos a una lista de correo, no lo compartimos con terceros y no lo retenemos después de que la conversación se resuelve.</p><h2>Hosting</h2><p>Este sitio se sirve como archivos estáticos. Su navegador intercambiará cabeceras de solicitud estándar (User-Agent, Accept-Language, dirección IP) con el CDN / servidor web que aloja los archivos; ese intercambio se rige por las prácticas de privacidad del proveedor de hosting y no está bajo el control de ForgeLM. No registramos este tráfico nosotros mismos.</p><h2>Recursos de terceros</h2><p>El sitio carga:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — las tipografías <em>Inter</em> y <em>JetBrains Mono</em>. Google puede registrar las solicitudes como se describe en su política de privacidad.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 se carga solo en la <a href=\"guide.html\">página Guía</a> para renderizar los diagramas de arquitectura / flujo. jsDelivr puede registrar las solicitudes como se describe en su política de privacidad.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — solo cuando envía el formulario de contacto, como se describe arriba.</li></ul><p>Nada más se carga desde un tercero. No hay Google Analytics, no hay píxel de Facebook, no hay Hotjar, no hay Mixpanel, no hay tracker-del-momento-sea-cual-sea.</p><h2>Niños</h2><p>Este sitio está dirigido a desarrolladores, ingenieros de ML y profesionales del cumplimiento. No está dirigido a niños menores de 16 años.</p><h2>Sus derechos (RGPD / KVKK)</h2><p>Si cree que tenemos datos personales sobre usted y desea acceder, corregir o eliminarlos, escríbanos vía el formulario de contacto (o <a href=\"https://github.com/cemililik/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>) y responderemos en 30 días. Dado que los únicos datos personales que tenemos son lo que envió en el formulario de contacto, la eliminación es directa: borramos el hilo de email.</p><h2>El toolkit en sí</h2><p>El paquete Python <strong>ForgeLM</strong> — instalado vía <code>pip install forgelm==0.5.5</code> — no telefonea a casa. No recopila telemetría, no envía datos de uso a ninguna parte y funciona offline (compatible con air-gap). Los modelos, datasets y tokenizers que referencia en su config YAML se descargan solo a petición explícita suya y solo desde fuentes que usted especifica.</p><h2>Derechos del interesado que puede enviar en su propio pipeline</h2><p>Si su organización despliega ForgeLM, el toolkit proporciona primitivas concretas para el lado de los derechos del interesado del RGPD: <code>forgelm reverse-pii</code> escanea el corpus en busca de residuos en texto claro o digests salados de un identificador de sujeto y reporta cada fila en la que aparece (Artículo 15 acceso), y <code>forgelm purge</code> elimina esas filas de sus corpus de entrenamiento y estampa la supresión en el log de auditoría append-only (Artículo 17 supresión). Además, ForgeLM está alineado con los controles ISO 27001 / SOC 2 Type II — vea la <a href=\"compliance.html\">página de Compliance</a> para el mapa completo de pruebas.</p><h2>Cambios</h2><p>Si actualizamos esta página, la fecha en la parte superior cambia. Los cambios materiales se anotan en el <code>CHANGELOG.md</code> del proyecto.</p><h2>Preguntas</h2><p>Abra el <a href=\"contact.html\">formulario de contacto</a> o una <a href=\"https://github.com/cemililik/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>.</p>"
+    "privacy.body":               "<h2>Versión corta</h2><p>Este sitio es HTML estático. No ejecutamos analytics, píxeles de tracking, trackers publicitarios, A/B tests, fingerprinting o telemetría de terceros. Aquí pueden ocurrir tres solicitudes a terceros: <strong>Google Fonts</strong> se obtiene en cada carga de página (las tipografías <em>Inter</em> y <em>JetBrains Mono</em>); <strong>Mermaid</strong> se carga desde jsDelivr solo en la <a href=\"guide.html\">página Guía</a> (para renderizar los diagramas); y <strong>Formspree</strong> solo cuando envía el formulario de contacto. Las tres están detalladas abajo; nada más.</p><h2>Qué recopilamos</h2><h3>De la navegación normal</h3><p>Nada. No se establecen cookies. Se almacenan dos valores en <code>localStorage</code> en su dispositivo:</p><ul><li><code>forgelm-lang</code> — su idioma de interfaz elegido (<code>en</code>, <code>tr</code>, <code>de</code>, <code>fr</code>, <code>es</code>, <code>zh</code>).</li><li><code>forgelm-theme</code> — su tema de color elegido (<code>dark</code> o <code>light</code>).</li></ul><p>Ambos quedan en su dispositivo y nunca se transmiten. Limpiar el almacenamiento del navegador los elimina.</p><h3>Del formulario de contacto</h3><p>Cuando envía el formulario en la página de Contacto, los valores que escribió (nombre, email, organización, tema, asunto, mensaje) se envían a Formspree, que los reenvía al mantenedor del proyecto. Las prácticas de privacidad de Formspree se rigen por su propia política en <a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>.</p><p>Su email se usa <strong>solo</strong> para responder a su mensaje. No lo agregamos a una lista de correo, no lo compartimos con terceros y no lo retenemos después de que la conversación se resuelve.</p><h2>Hosting</h2><p>Este sitio se sirve como archivos estáticos. Su navegador intercambiará cabeceras de solicitud estándar (User-Agent, Accept-Language, dirección IP) con el CDN / servidor web que aloja los archivos; ese intercambio se rige por las prácticas de privacidad del proveedor de hosting y no está bajo el control de ForgeLM. No registramos este tráfico nosotros mismos.</p><h2>Recursos de terceros</h2><p>El sitio carga:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — las tipografías <em>Inter</em> y <em>JetBrains Mono</em>. Google puede registrar las solicitudes como se describe en su política de privacidad.</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 se carga solo en la <a href=\"guide.html\">página Guía</a> para renderizar los diagramas de arquitectura / flujo. jsDelivr puede registrar las solicitudes como se describe en su política de privacidad.</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — solo cuando envía el formulario de contacto, como se describe arriba.</li></ul><p>Nada más se carga desde un tercero. No hay Google Analytics, no hay píxel de Facebook, no hay Hotjar, no hay Mixpanel, no hay tracker-del-momento-sea-cual-sea.</p><h2>Niños</h2><p>Este sitio está dirigido a desarrolladores, ingenieros de ML y profesionales del cumplimiento. No está dirigido a niños menores de 16 años.</p><h2>Sus derechos (RGPD / KVKK)</h2><p>Si cree que tenemos datos personales sobre usted y desea acceder, corregir o eliminarlos, escríbanos vía el formulario de contacto (o <a href=\"https://github.com/HodeTech/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>) y responderemos en 30 días. Dado que los únicos datos personales que tenemos son lo que envió en el formulario de contacto, la eliminación es directa: borramos el hilo de email.</p><h2>El toolkit en sí</h2><p>El paquete Python <strong>ForgeLM</strong> — instalado vía <code>pip install forgelm</code> — no telefonea a casa. No recopila telemetría, no envía datos de uso a ninguna parte y funciona offline (compatible con air-gap). Los modelos, datasets y tokenizers que referencia en su config YAML se descargan solo a petición explícita suya y solo desde fuentes que usted especifica.</p><h2>Derechos del interesado que puede enviar en su propio pipeline</h2><p>Si su organización despliega ForgeLM, el toolkit proporciona primitivas concretas para el lado de los derechos del interesado del RGPD: <code>forgelm reverse-pii</code> escanea el corpus en busca de residuos en texto claro o digests salados de un identificador de sujeto y reporta cada fila en la que aparece (Artículo 15 acceso), y <code>forgelm purge</code> elimina esas filas de sus corpus de entrenamiento y estampa la supresión en el log de auditoría append-only (Artículo 17 supresión). Además, ForgeLM está alineado con los controles ISO 27001 / SOC 2 Type II — vea la <a href=\"compliance.html\">página de Compliance</a> para el mapa completo de pruebas.</p><h2>Cambios</h2><p>Si actualizamos esta página, la fecha en la parte superior cambia. Los cambios materiales se anotan en el <code>CHANGELOG.md</code> del proyecto.</p><h2>Preguntas</h2><p>Abra el <a href=\"contact.html\">formulario de contacto</a> o una <a href=\"https://github.com/HodeTech/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>.</p>"
   });
 
   Object.assign(T.zh, {
@@ -4387,7 +4387,7 @@
     "privacy.header.eyebrow":     "隐私",
     "privacy.header.title":       "隐私政策",
     "privacy.header.lead":        "ForgeLM 是你在自己基础设施上运行的开源软件。本页讲的是这个<em>网站</em>做了什么 — 不是 toolkit 本身。",
-    "privacy.body":               "<h2>简短版</h2><p>本站是静态 HTML。我们不运行分析、跟踪像素、广告跟踪器、A/B 测试、指纹识别或任何第三方遥测。本站可能发生三种第三方请求:<strong>Google Fonts</strong> 在每次页面加载时获取 (<em>Inter</em> 和 <em>JetBrains Mono</em> 字体);<strong>Mermaid</strong> 仅在<a href=\"guide.html\">指南页面</a>从 jsDelivr 加载 (用于渲染图表);<strong>Formspree</strong> 仅在你提交联系表单时。三者均在下方详述;此外没有别的。</p><h2>我们收集什么</h2><h3>正常浏览时</h3><p>什么也没有。不设置 cookie。在你设备的 <code>localStorage</code> 中存储两个值:</p><ul><li><code>forgelm-lang</code> — 你选择的界面语言 (<code>en</code>、<code>tr</code>、<code>de</code>、<code>fr</code>、<code>es</code>、<code>zh</code>)。</li><li><code>forgelm-theme</code> — 你选择的色彩主题 (<code>dark</code> 或 <code>light</code>)。</li></ul><p>两者都留在你设备上,从不发送出去。清除浏览器存储就能移除它们。</p><h3>从联系表单</h3><p>当你在联系页提交表单时,你填写的值 (姓名、邮箱、组织、主题、标题、消息) 会发送到 Formspree,Formspree 再转发给项目维护者。Formspree 的隐私实践由其自身政策管理:<a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>。</p><p>你的邮箱<strong>仅</strong>用于回复你的消息。不会加入任何邮件列表,不会与第三方共享,在对话结束之后也不保留。</p><h2>托管</h2><p>本站以静态文件的方式提供。你的浏览器会与托管文件的 CDN / Web 服务器交换标准请求头 (User-Agent、Accept-Language、IP 地址);该交换由托管提供商的隐私实践管理,不在 ForgeLM 的控制之下。我们自己不记录这部分流量。</p><h2>第三方资源</h2><p>本站加载:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — <em>Inter</em> 和 <em>JetBrains Mono</em> 字体。Google 可能按照其隐私政策记录请求。</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 仅在<a href=\"guide.html\">指南页面</a>加载,用于渲染架构 / 流程图。jsDelivr 可能按照其隐私政策记录请求。</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — 仅在你提交联系表单时,如上所述。</li></ul><p>除此之外不从任何第三方加载。没有 Google Analytics、没有 Facebook 像素、没有 Hotjar、没有 Mixpanel、没有那个时髦的随便什么跟踪器。</p><h2>儿童</h2><p>本站面向开发者、ML 工程师和合规专业人员。不面向 16 岁以下儿童。</p><h2>你的权利 (GDPR / KVKK)</h2><p>如果你认为我们持有关于你的个人数据,并希望访问、更正或删除它,通过联系表单 (或 <a href=\"https://github.com/cemililik/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>) 写信给我们;我们会在 30 天内回复。由于我们持有的唯一个人数据就是你在联系表单中发送的内容,删除很简单:我们删除该邮件 thread。</p><h2>Toolkit 本身</h2><p>通过 <code>pip install forgelm==0.5.5</code> 安装的 <strong>ForgeLM</strong> Python 包不会回拨。不收集遥测,不向任何地方发送使用数据,可离线工作 (支持气隙)。你在 YAML 配置中引用的模型、数据集和 tokenizer 仅在你的明确请求下且仅从你指定的来源下载。</p><h2>你可以在自己的管道中交付的数据主体权利</h2><p>如果你的组织部署 ForgeLM,这套工具为 GDPR 数据主体权利那一面提供了具体原语:<code>forgelm reverse-pii</code> 扫描语料库,查找主体标识的明文残留或加盐 digest 匹配,并报告该主体出现的每一行 (第 15 条访问);<code>forgelm purge</code> 从你的训练语料中删除这些行,并将删除盖戳到 append-only 审计日志中 (第 17 条删除)。此外,ForgeLM 与 ISO 27001 / SOC 2 Type II 控制项保持对齐 — 见<a href=\"compliance.html\">合规页面</a>查看完整证据图。</p><h2>变更</h2><p>如果我们更新本页,顶部日期会变化。重要变更会记入项目的 <code>CHANGELOG.md</code>。</p><h2>问题</h2><p>打开<a href=\"contact.html\">联系表单</a>或一个 <a href=\"https://github.com/cemililik/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>。</p>"
+    "privacy.body":               "<h2>简短版</h2><p>本站是静态 HTML。我们不运行分析、跟踪像素、广告跟踪器、A/B 测试、指纹识别或任何第三方遥测。本站可能发生三种第三方请求:<strong>Google Fonts</strong> 在每次页面加载时获取 (<em>Inter</em> 和 <em>JetBrains Mono</em> 字体);<strong>Mermaid</strong> 仅在<a href=\"guide.html\">指南页面</a>从 jsDelivr 加载 (用于渲染图表);<strong>Formspree</strong> 仅在你提交联系表单时。三者均在下方详述;此外没有别的。</p><h2>我们收集什么</h2><h3>正常浏览时</h3><p>什么也没有。不设置 cookie。在你设备的 <code>localStorage</code> 中存储两个值:</p><ul><li><code>forgelm-lang</code> — 你选择的界面语言 (<code>en</code>、<code>tr</code>、<code>de</code>、<code>fr</code>、<code>es</code>、<code>zh</code>)。</li><li><code>forgelm-theme</code> — 你选择的色彩主题 (<code>dark</code> 或 <code>light</code>)。</li></ul><p>两者都留在你设备上,从不发送出去。清除浏览器存储就能移除它们。</p><h3>从联系表单</h3><p>当你在联系页提交表单时,你填写的值 (姓名、邮箱、组织、主题、标题、消息) 会发送到 Formspree,Formspree 再转发给项目维护者。Formspree 的隐私实践由其自身政策管理:<a href=\"https://formspree.io/legal/privacy-policy\" target=\"_blank\" rel=\"noopener\">formspree.io/legal/privacy-policy</a>。</p><p>你的邮箱<strong>仅</strong>用于回复你的消息。不会加入任何邮件列表,不会与第三方共享,在对话结束之后也不保留。</p><h2>托管</h2><p>本站以静态文件的方式提供。你的浏览器会与托管文件的 CDN / Web 服务器交换标准请求头 (User-Agent、Accept-Language、IP 地址);该交换由托管提供商的隐私实践管理,不在 ForgeLM 的控制之下。我们自己不记录这部分流量。</p><h2>第三方资源</h2><p>本站加载:</p><ul><li><a href=\"https://fonts.googleapis.com\" target=\"_blank\" rel=\"noopener\">Google Fonts</a> — <em>Inter</em> 和 <em>JetBrains Mono</em> 字体。Google 可能按照其隐私政策记录请求。</li><li><a href=\"https://www.jsdelivr.com\" target=\"_blank\" rel=\"noopener\">jsDelivr</a> — Mermaid 10.9.4 仅在<a href=\"guide.html\">指南页面</a>加载,用于渲染架构 / 流程图。jsDelivr 可能按照其隐私政策记录请求。</li><li><a href=\"https://formspree.io\" target=\"_blank\" rel=\"noopener\">Formspree</a> — 仅在你提交联系表单时,如上所述。</li></ul><p>除此之外不从任何第三方加载。没有 Google Analytics、没有 Facebook 像素、没有 Hotjar、没有 Mixpanel、没有那个时髦的随便什么跟踪器。</p><h2>儿童</h2><p>本站面向开发者、ML 工程师和合规专业人员。不面向 16 岁以下儿童。</p><h2>你的权利 (GDPR / KVKK)</h2><p>如果你认为我们持有关于你的个人数据,并希望访问、更正或删除它,通过联系表单 (或 <a href=\"https://github.com/HodeTech/ForgeLM/issues\" target=\"_blank\" rel=\"noopener\">GitHub Issues</a>) 写信给我们;我们会在 30 天内回复。由于我们持有的唯一个人数据就是你在联系表单中发送的内容,删除很简单:我们删除该邮件 thread。</p><h2>Toolkit 本身</h2><p>通过 <code>pip install forgelm</code> 安装的 <strong>ForgeLM</strong> Python 包不会回拨。不收集遥测,不向任何地方发送使用数据,可离线工作 (支持气隙)。你在 YAML 配置中引用的模型、数据集和 tokenizer 仅在你的明确请求下且仅从你指定的来源下载。</p><h2>你可以在自己的管道中交付的数据主体权利</h2><p>如果你的组织部署 ForgeLM,这套工具为 GDPR 数据主体权利那一面提供了具体原语:<code>forgelm reverse-pii</code> 扫描语料库,查找主体标识的明文残留或加盐 digest 匹配,并报告该主体出现的每一行 (第 15 条访问);<code>forgelm purge</code> 从你的训练语料中删除这些行,并将删除盖戳到 append-only 审计日志中 (第 17 条删除)。此外,ForgeLM 与 ISO 27001 / SOC 2 Type II 控制项保持对齐 — 见<a href=\"compliance.html\">合规页面</a>查看完整证据图。</p><h2>变更</h2><p>如果我们更新本页,顶部日期会变化。重要变更会记入项目的 <code>CHANGELOG.md</code>。</p><h2>问题</h2><p>打开<a href=\"contact.html\">联系表单</a>或一个 <a href=\"https://github.com/HodeTech/ForgeLM/discussions\" target=\"_blank\" rel=\"noopener\">GitHub Discussion</a>。</p>"
   });
 
   /* ── Terms page (terms.html) ─────────────────────────────── */
@@ -4464,7 +4464,7 @@
     "compliance.iso.lineage.body": "<code>data_provenance.json</code> (SHA-256-Fingerprint + Größe + mtime + HF-Hub-Revisions-Pin) und <code>data_governance_report.json</code> (Erhebungsmethode, Annotationsprozess, bekannte Verzerrungen, Personenbezogen-Daten-Flag, DPIA-Abschluss) decken die Lineage-Fragen ab, die ein Auditor zuerst stellt.",
     "compliance.iso.supply.title": "Supply Chain",
     "compliance.iso.supply.body": "CycloneDX 1.5 SBOM pro Release-Tag für jede (OS x Python-Version)-Zelle der Publish-Matrix emittiert. Wave 4 fügte <code>pip-audit</code> nightly + <code>bandit</code> in CI für statische + dynamische Sicherheitsscans des Builds selbst hinzu.",
-    "compliance.iso.cookbook": "Für das vollständige Audit-Cookbook, einschließlich 8 Audit-Floor-Fragen und einer 93-Kontrollen-Abdeckungskarte, siehe <a href=\"https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
+    "compliance.iso.cookbook": "Für das vollständige Audit-Cookbook, einschließlich 8 Audit-Floor-Fragen und einer 93-Kontrollen-Abdeckungskarte, siehe <a href=\"https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
     "features.gov.heading": "Compliance- &amp; DSGVO-Tooling",
     "features.gov.body": "EU-AI-Act-Artikel 9-17, DSGVO-Artikel 15 + 17, ISO-27001- / SOC-2-Type-II-Alignment-Nachweise.",
     "features.gov.access.title": "DSGVO-Artikel-15-Auskunft",
@@ -4510,7 +4510,7 @@
     "compliance.iso.lineage.body": "<code>data_provenance.json</code> (empreinte SHA-256 + taille + mtime + pin de révision HF Hub) et <code>data_governance_report.json</code> (méthode de collecte, processus d'annotation, biais connus, drapeau données personnelles, complétion DPIA) couvrent les questions de traçabilité qu'un auditeur pose en premier.",
     "compliance.iso.supply.title": "Supply chain",
     "compliance.iso.supply.body": "SBOM CycloneDX 1.5 émis par tag de release pour chaque cellule (OS x version Python) de la matrice de publication. Wave 4 a ajouté <code>pip-audit</code> nightly + <code>bandit</code> en CI pour le scan de sécurité statique + dynamique du build lui-même.",
-    "compliance.iso.cookbook": "Pour le cookbook d'audit complet, incluant 8 questions audit-floor et une cartographie de couverture de 93 contrôles, voir <a href=\"https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
+    "compliance.iso.cookbook": "Pour le cookbook d'audit complet, incluant 8 questions audit-floor et une cartographie de couverture de 93 contrôles, voir <a href=\"https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
     "features.gov.heading": "Outillage Compliance &amp; RGPD",
     "features.gov.body": "Articles 9-17 de l'EU AI Act, RGPD Articles 15 + 17, preuves d'alignement ISO 27001 / SOC 2 Type II.",
     "features.gov.access.title": "Accès RGPD Article 15",
@@ -4556,7 +4556,7 @@
     "compliance.iso.lineage.body": "<code>data_provenance.json</code> (huella SHA-256 + tamaño + mtime + pin de revisión HF Hub) y <code>data_governance_report.json</code> (método de recolección, proceso de anotación, sesgos conocidos, marca de datos personales, completitud DPIA) cubren las preguntas de trazabilidad que un auditor hace primero.",
     "compliance.iso.supply.title": "Cadena de suministro",
     "compliance.iso.supply.body": "SBOM CycloneDX 1.5 emitido por etiqueta de release para cada celda (OS x versión Python) de la matriz de publicación. Wave 4 añadió <code>pip-audit</code> nightly + <code>bandit</code> en CI para escaneo de seguridad estático + dinámico del propio build.",
-    "compliance.iso.cookbook": "Para el cookbook de auditoría completo, incluidas 8 preguntas audit-floor y un mapa de cobertura de 93 controles, vea <a href=\"https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
+    "compliance.iso.cookbook": "Para el cookbook de auditoría completo, incluidas 8 preguntas audit-floor y un mapa de cobertura de 93 controles, vea <a href=\"https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>.",
     "features.gov.heading": "Tooling Compliance &amp; RGPD",
     "features.gov.body": "Artículos 9-17 del EU AI Act, RGPD Artículos 15 + 17, pruebas de alineamiento ISO 27001 / SOC 2 Type II.",
     "features.gov.access.title": "Acceso RGPD Artículo 15",
@@ -4602,7 +4602,7 @@
     "compliance.iso.lineage.body": "<code>data_provenance.json</code> (SHA-256 指纹 + 大小 + mtime + HF Hub 修订版本固定) 与 <code>data_governance_report.json</code> (采集方法、标注流程、已知偏见、个人数据标记、DPIA 完成情况) 覆盖审计员最先问的血缘问题。",
     "compliance.iso.supply.title": "供应链",
     "compliance.iso.supply.body": "每个 release tag 为 publish 矩阵的每个 (OS x Python 版本) 单元格发布 CycloneDX 1.5 SBOM。Wave 4 在 CI 中加入 nightly <code>pip-audit</code> + <code>bandit</code>,对构建本身进行静态 + 动态安全扫描。",
-    "compliance.iso.cookbook": "完整的审计 cookbook,包括 8 个 audit-floor 问题和 93 控制项覆盖图,见 <a href=\"https://github.com/cemililik/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>。",
+    "compliance.iso.cookbook": "完整的审计 cookbook,包括 8 个 audit-floor 问题和 93 控制项覆盖图,见 <a href=\"https://github.com/HodeTech/ForgeLM/blob/main/docs/guides/iso_soc2_deployer_guide.md\" target=\"_blank\" rel=\"noopener\"><code>docs/guides/iso_soc2_deployer_guide.md</code></a>。",
     "features.gov.heading": "合规 &amp; GDPR 工具",
     "features.gov.body": "EU AI Act 第 9-17 条、GDPR 第 15 + 17 条、ISO 27001 / SOC 2 Type II 对齐证据。",
     "features.gov.access.title": "GDPR 第 15 条访问",
diff --git a/site/privacy.html b/site/privacy.html
index 8c9b151e..da60c4e4 100644
--- a/site/privacy.html
+++ b/site/privacy.html
@@ -68,7 +68,7 @@
   "name": "ForgeLM",
   "url": "https://forgelm.dev/",
   "sameAs": [
-    "https://github.com/cemililik/ForgeLM",
+    "https://github.com/HodeTech/ForgeLM",
     "https://pypi.org/project/forgelm/"
   ]
 }
@@ -169,10 +169,10 @@ <h4 data-i18n="common.footer.product">Product</h4>
       <div class="footer-col">
         <h4 data-i18n="common.footer.community">Community</h4>
         <ul>
-          <li><a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
         </ul>
       </div>
 
diff --git a/site/quickstart.html b/site/quickstart.html
index a33a0431..c15d541d 100644
--- a/site/quickstart.html
+++ b/site/quickstart.html
@@ -68,7 +68,7 @@
   "name": "ForgeLM",
   "url": "https://forgelm.dev/",
   "sameAs": [
-    "https://github.com/cemililik/ForgeLM",
+    "https://github.com/HodeTech/ForgeLM",
     "https://pypi.org/project/forgelm/"
   ]
 }
@@ -349,7 +349,7 @@ <h2 class="quickstart-wizard-h2" data-i18n="quickstart.wizard.title">Prefer a gu
         <p class="quickstart-wizard-p" data-i18n-html="quickstart.wizard.body">Skip the YAML — the in-browser wizard walks through trainer choice, model, dataset, LoRA rank, and evaluation gates, then writes a working config you can run with one command.</p>
         <div class="cta-actions">
           <button type="button" class="btn btn-primary" data-wizard-open data-i18n="quickstart.wizard.btn1">Launch the wizard</button>
-          <a href="https://github.com/cemililik/ForgeLM#quick-start" target="_blank" rel="noopener" class="btn btn-secondary" data-i18n="quickstart.wizard.btn2">CLI version (forgelm --wizard)</a>
+          <a href="https://github.com/HodeTech/ForgeLM#quick-start" target="_blank" rel="noopener" class="btn btn-secondary" data-i18n="quickstart.wizard.btn2">CLI version (forgelm --wizard)</a>
           <a href="features.html" class="btn btn-ghost" data-i18n="quickstart.wizard.btn3">Browse all features</a>
         </div>
       </div>
@@ -449,10 +449,10 @@ <h4 data-i18n="common.footer.product">Product</h4>
       <div class="footer-col">
         <h4 data-i18n="common.footer.community">Community</h4>
         <ul>
-          <li><a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
         </ul>
       </div>
 
diff --git a/site/terms.html b/site/terms.html
index 32404e76..02a71ef5 100644
--- a/site/terms.html
+++ b/site/terms.html
@@ -68,7 +68,7 @@
   "name": "ForgeLM",
   "url": "https://forgelm.dev/",
   "sameAs": [
-    "https://github.com/cemililik/ForgeLM",
+    "https://github.com/HodeTech/ForgeLM",
     "https://pypi.org/project/forgelm/"
   ]
 }
@@ -169,10 +169,10 @@ <h4 data-i18n="common.footer.product">Product</h4>
       <div class="footer-col">
         <h4 data-i18n="common.footer.community">Community</h4>
         <ul>
-          <li><a href="https://github.com/cemililik/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
-          <li><a href="https://github.com/cemililik/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM" target="_blank" rel="noopener">GitHub</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/issues" target="_blank" rel="noopener" data-i18n="common.footer.issues">Issues</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/discussions" target="_blank" rel="noopener" data-i18n="common.footer.discussions">Discussions</a></li>
+          <li><a href="https://github.com/HodeTech/ForgeLM/releases" target="_blank" rel="noopener" data-i18n="common.footer.releases">Releases</a></li>
         </ul>
       </div>
 
diff --git a/sonar-project.properties b/sonar-project.properties
index d0f993ce..19671dab 100644
--- a/sonar-project.properties
+++ b/sonar-project.properties
@@ -1,5 +1,5 @@
-sonar.projectKey=cemililik_ForgeLM
-sonar.organization=cemililik
+sonar.projectKey=HodeTech_ForgeLM
+sonar.organization=hodetech
 
 # Sources analysed for code quality + security.
 sonar.sources=forgelm,site,tools,.github/workflows
diff --git a/tools/pip_audit_ignores.yaml b/tools/pip_audit_ignores.yaml
index a3d8bbfd..1ddde546 100644
--- a/tools/pip_audit_ignores.yaml
+++ b/tools/pip_audit_ignores.yaml
@@ -48,6 +48,31 @@ ignores:
       release with the fix, or when ForgeLM cuts a tracked
       major-version-bump cycle that raises the upper bound.
 
+  - id: PYSEC-2025-217
+    aliases: [CVE-2025-14929]
+    package: transformers
+    reason: >-
+      CVE-2025-14929 — X-CLIP checkpoint-conversion deserialization
+      RCE (CVSS:3.0 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).  The
+      advisory records no fixed version for the 4.x line that
+      pyproject pins.
+    threat_model: >-
+      CVSS is local + user-interaction (AV:L/UI:R): the target must
+      open a malicious checkpoint/file.  Same trust model as
+      ``torch.load(pickle)`` — operators are documented as required
+      to only load trusted checkpoints.  Codebase check on
+      2026-05-24 (``git grep`` over ``forgelm/``): no X-CLIP usage,
+      no checkpoint-conversion path other than the HF->GGUF export
+      wrapper, and zero direct ``torch.load`` call sites — all model
+      loading goes through HuggingFace ``from_pretrained``.  The
+      vulnerable X-CLIP conversion path is therefore not reachable
+      from ForgeLM code.
+    verified_at: '2026-05-24'
+    reevaluate_after: >-
+      Each release cycle, or when the advisory gains a fixed version
+      within the pinned ``transformers<5.0.0`` range, or when ForgeLM
+      bumps to a transformers release that carries the fix.
+
   # ----- torch (added 2026-05-21, triage in issue #58) -----
   #
   # All nine torch CVEs below share the same threat-model carve-out: