Skip to content

Rollout

Status of the consolidation effort. Update this page as steps land.

# Step Repo PR / issue Status
1 Pull BRAIN.md into aggregator as /docs/brain/; add nav. rig-gitops this PR ✅ done
1a Land Docs Architecture section (this section). rig-gitops this PR ✅ done
2 Worker landing redirect / → /docs/. Drop inline-HTML landing. infra dashecorp/infra#101, #103, #104 ✅ done
3 Drop /conductor-e/* and /ibuild-e/* Worker routes — content already in /docs/components/.... infra dashecorp/infra#106 ✅ done
4 Retire conductor-e-docs and mac-executor-docs Pages projects (delete in CF + Tofu). infra rig-conductor#96, rig-agent-runtime#109, wrangler pages project delete 2026-04-21 ✅ done
5 Fix Astro /research/ CSS — subdomain research.rig.dashecorp.com. rig-docs (Astro) + infra dashecorp/infra#108 ✅ done
5b Move docs to subdomain too (docs.rig.dashecorp.com); replace Worker with discoverable landing page; 301 legacy /docs/* for back-compat. infra dashecorp/infra#110 ✅ done
6 Single-source-of-truth note in claude-3/docs/infrastructure/websites.md pointing to this section as canonical. claude-3 TBD ⏳ pending
7 Per-component notify-aggregator.yml workflow → fires repository_dispatch(docs-update) at rig-gitops on docs push. Reduces latency from hourly to seconds. each of rig-conductor, rig-agent-runtime, rig-memory-mcp, rig-tools, infra TBD ⏳ pending

Order

Strict serial through step 4 (each step changes user-visible URLs and we want one Playwright verification between them). 5 and 6 can run in parallel after 4. 7 is independent — can land any time.

Done means

  • Step 1 — rig.dashecorp.com/docs/brain/ returns 200 with the rendered BRAIN content under the Material theme. Playwright verified.
  • Step 2 — curl -I rig.dashecorp.com/ returns 302 → /docs/.
  • Step 3 — rig.dashecorp.com/conductor-e/ returns 404; same content reachable at /docs/components/rig-conductor/.
  • Step 4 — npx wrangler pages project list no longer shows the two projects.
  • Step 5 — https://research.rig.dashecorp.com/ (or rig.dashecorp.com/research/ if rebuild path chosen) renders with CSS, fonts, JS all 200.
  • Step 6 — claude-3/docs/infrastructure/websites.md has a "see also: Docs Architecture" link and no longer duplicates the topology details.
  • Step 7 — touch a doc in any component repo, watch deploy fire within 60 seconds.

Out of scope

  • Renaming rig-docs Pages project to rig or anything else. Backend names don't matter once rig.dashecorp.com is the single front.
  • Migrating to a different docs generator (Docusaurus, etc.). MkDocs Material works; switching is a Day-2 question.
  • Publishing dashecorp-product docs (Tablez, Nutri-E, …) under rig.dashecorp.com. Those have their own surfaces.

Risks tracked

  • Bookmarked URLs under /conductor-e/... and mac-executor-docs.pages.dev will 404 after step 4. Acceptable — these are internal docs with low external traffic; we accept the breakage rather than maintain redirects forever.
  • Astro base rebuild (step 5 option B) could break links inside the Astro site; subdomain (option A) is safer.
  • Per-repo notify workflows (step 7) require a PAT or App token in each repo with permission to dispatch at rig-gitops. Reuse RIG_DOCS_DISPATCH_TOKEN shape.