diff --git a/CLAUDE.md b/CLAUDE.md
index 0d0d248..4e78610 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -36,14 +36,14 @@ typikon/
 
 ## Standards
 
-Follow kanon standards (canonical: `~/dev/kanon/crates/basanos/standards/`). Key docs: `STANDARDS.md`, `TESTING.md`, `SECURITY.md`, `WRITING.md`, `GNOMON.md`.
+Follow kanon standards (canonical: `crates/basanos/standards/` in `forkwright/kanon`). Key docs: `STANDARDS.md`, `TESTING.md`, `SECURITY.md`, `WRITING.md`, `GNOMON.md`.
 
 Web-property-specific standards live alongside as kanon STANDARDS/WEB.md (filed against kanon as a follow-up to typikon v1).
 
 ## Locked decisions
 
 - **Static SSG**: Zola 0.23.x with Tera 2 templates. No JavaScript build step, no Node toolchain, no npm in the site build path.
-- **Dual-CI migration window**: consumer sites scaffold both `.kanon-ci.toml` and `.github/workflows/deploy.yml`. Forge is primary; GitHub is the executable fallback until menos validates the forge deploy path end-to-end. Both templates target the same Cloudflare Pages project and main/master branch semantics.
+- **Dual-CI migration window**: consumer sites scaffold both `.kanon-ci.toml` and `.github/workflows/deploy.yml`. Forge is primary; GitHub is the executable fallback until forge runners validate the forge deploy path end-to-end. Both templates target the same Cloudflare Pages project and main/master branch semantics.
 - **Temporary Node deploy-tool exception**: the consumer deploy gates install npm-based `pa11y`, Playwright, and Wrangler so forge and GitHub stay stage-for-stage equivalent during migration. Revisit when forge has native replacements.
 - **Theme distribution**: git submodule under consumer's `themes/typikon/`. (Zola has no theme registry; submodule is current best practice.)
 - **Strict CSP**: no `unsafe-inline` anywhere. CSP-enforce CI gate fails the build on any inline script, style, or `on*=` handler.
diff --git a/docs/AGENTIC.md b/docs/AGENTIC.md
index 35e6fd5..fe2eeea 100644
--- a/docs/AGENTIC.md
+++ b/docs/AGENTIC.md
@@ -216,7 +216,7 @@ When a new fleet site enters the family, do not fork or copy. Consume the substr
 ### 1. Scaffold
 
 ```bash
-typikon-init <site-slug> ~/dev/<site-slug>
+typikon-init <site-slug> <destination-path>
 ```
 
 The scaffolder writes `config.toml`, the `themes/typikon` submodule, `_headers`, `_redirects`, the GitHub Actions workflow, a starter `content/_index.md`, and the operator brief at `CLAUDE.md`. The first commit lands automatically. Once the forge repo exists, the operator pushes (`kanon forge init forkwright/<site-slug>`).