Skip to content

Cosmos Phase 6+ Roadmap — From 8 May 2026

Sush flagged these 7 workstreams at the close of the 8 May 2026 cosmos unification session. The unification (Phases 1 → 5) is the foundation; this doc is the build-on-top. Future sessions opening cosmos work cold should read cosmos-audit.md first (the master resume artefact) then this file.

🆕 8 May 2026 evening — Plain AI brand-positioning correction + branding audit cycle (4 more taglines)

Plain AI is NOT a museum. It's where to learn AI in plain language — accessible to everyone. The "museum of AI" framing used in early build phases (Direction-C Museum re-skin, PLATE № NN labels, "exhibit" copy) was retired by Sush 8 May 2026. The visual register (dark-default #0B0D14, cyan/purple/pink gradient covers, JetBrains Mono labels) stays unchanged — it's atmosphere, not metaphor. The language has been corrected.

Plus a follow-up audit caught that 4 of the other 6 manifest taglines also lagged the actual offerings. All shipped same evening:

Planet Old tagline New tagline (sourced from production)
🌍 Earth the home — certs, tools, mind maps free cloud + AI guides for IT pros — tools, certs, blog, videos
🌑 Guided cert prep — affordable practice exams practice exams that don't gatekeep — $9, not $79
🪐 CMD Microsoft jargon decoder Microsoft jargon AND error code decoder
🪐 Plain AI museum of AI, in plain English AI explained plainly, for everyone
🪐 Agentic agent cockpit — for techies building with agents MCP reviews, recipes, vendor takes — for techies building with agents

Other surface changes (Plain AI round): Topic page label PLATE № NN → Topic NN · 78 (already shipped earlier) · CMD About cosmos map 78 plates → 78 topics · styles.css pseudo-content // other exhibits → // related topics · Plain AI playbook gets a positioning note explaining museum references describe a retired phase.

Other surface changes (branding audit round): CMD About cosmos map Earth row gets videos added · Guided moon line gets that doesn't gatekeep added · Agentic row says MCP reviews, recipes, vendor takes · Agentic + Claw About cosmosMap arrays slug fix cmd → brainbar (matches canonical) · cosmos doc descriptions in learning-docs updated to match new taglines.

Commit-sets: - Plain AI brand correction (~7 repos): fa4ea981 (aguidetocloud-revamp) · 17ad0f6 (guided) · 998b0c4 (shift) · c5a1df3 (agentic-planet) · b523788 (claw-planet) · 1cc855e (plainai) · 7399c0a + 58a49e8 (learning-docs) - Branding audit corrections (~6 repos): 0775fefc (aguidetocloud-revamp) · 0e27dc4 (guided) · 7f67585 (shift) · 9ac968e (agentic-planet) · 4342063 (claw-planet) · 80b4845 (plainai)

Audit doc with full per-planet evidence: Branding Audit — 8 May 2026 evening.

Future sessions: when authoring planet copy, manifest taglines, or cross-references, source the language from the planet's own hero + OG description first. The audit pattern that caught these (compare manifest tagline against hero h1 + OG meta + cross-planet About cosmosMap) is reusable — repeat after any major content shift.

Forbidden additions to the brand vocabulary (per Plain AI correction): museum · exhibit · plate · gallery · curator · curated AI exhibit. Forbidden additions per branding audit: marketing-words like affordable · enabling · empowering · revolutionary · game-changing · best-in-class · next-generation — describe the actual goods instead.

How to use this doc

  • Pick a workstream that matches your session's intent.
  • Read its Foundation (what's already shipped — don't redo it).
  • Read its Scope (what's actually in this workstream).
  • Read its File pointers (where the work lives).
  • Read its Next steps (concrete first commits).
  • Run the gates before push: mkdocs build --strict (exit 0) + node scripts/cosmos-drift-audit.mjs (exit 0).

What's already shipped (the foundation)

Don't rebuild any of this. Future sessions inherit it:

  • ✅ 7-planet manifest with 5 in-sync mirrors. Add to cosmos-audit.md Status Table when an 8th joins.
  • ✅ 5-mirror cosmos icon palette rendering 7 slugs (earth · guided · brainbar · shift · plainai · agentic · claw) — drift audit verifies parity in <1s.
  • ✅ Universal Cosmos Law #7 in cosmos-philosophy.md — lotus = default fallback; framework defaults are brand violations.
  • ✅ Dual-surface logo rule — tab/masthead = host identity; cosmos-rail/atlas = cosmic role. Lotus on Earth-family host surfaces; purpose-built mark on cosmic-role surfaces.
  • ✅ Cross-planet About blocks — every planet's About page mentions all 7 (Phase 3, 8 May).
  • ✅ New-planet onboarding checklist in cosmos-audit.md — 10 steps with file maps.
  • ✅ Drift audit script at learning-docs/scripts/cosmos-drift-audit.mjs — pre-commit gate.
  • ✅ Phase 4b mockup HTML at ~/.copilot/session-state/<id>/files/phase4b-mockups.html — pattern to reuse for future design decisions.

Workstream A — 🌌 Cosmos Atlas

An interactive visual map of the universe — all 7 planets shown together with relationships, role descriptions, click-through navigation. Different from the cosmos rail (which is a masthead chip strip); the atlas is a destination page.

Status

🟡 In flight — a parallel cosmos-atlas session shipped Phase 0 + 1 on 8 May (canvas + atmosphere) per the journal entry from that session. Their work lives at learning-docs/docs/cosmos/atlas/.

Foundation already laid

  • The 7-planet manifest is canonical in planets.toml + 4 JSON mirrors.
  • Each planet's purpose-built mark exists as an SVG (per-planet brand kit + 5-mirror cosmos-rail palette).
  • The dual-surface rule means atlas can use the cosmic-role mark for each planet (crescent for Guided, Signal LED for Agentic, etc.) — different from the masthead host-identity rule.

Scope (likely sub-workstreams)

  1. Atlas as a page — atlas.aguidetocloud.com or aguidetocloud.com/atlas/ rendering all 7 with SVG marks + role descriptions + onward links
  2. Atlas as a Loop/Excalidraw artefact — a static visual deliverable for talks/decks
  3. Atlas as MCP-served data — agent-readable JSON describing the cosmos topology (could be the second use of the mcp.aguidetocloud.com star)

Next steps

  1. Read the cosmos-atlas session's Phase 0 + 1 deliverable (their journal entry references it)
  2. Use the drift audit as a parity check between the atlas's planet list and planets.json
  3. Decide: which planet hosts the atlas? Earth is the natural home (it's the home planet — atlas = "the map of the home planet's cosmos")

File pointers

learning-docs/docs/cosmos/atlas/                        # parallel-session WIP
learning-docs/docs/reference/cosmos-philosophy.md        # dual-surface rule (#7)
learning-docs/scripts/cosmos-drift-audit.mjs             # parity gate

Workstream B — 🪐 Phase 4d: Agentic + Claw cosmos-rail rendering (one-way → two-way)

Currently Agentic + Claw are listed in every other planet's cosmos rail, but Agentic + Claw don't render the rail back. Visitors on Agentic/Claw can't navigate to other planets. Per cosmos philosophy, this is the "one-way carve-out" that should eventually become two-way.

Status

🔴 Not started. Architectural carve-out documented in cosmos-audit.md GUARDRAIL #4: "Until then the rail is one-way (cosmos-bound planets render the full 7; agentic + claw don't render the rail)."

Foundation already laid

  • Both planets join planets.toml already (as of 8 May)
  • Both have purpose-built marks (Signal LED for Agentic, [*] for Claw)
  • Both have 5-mirror cosmos icon palette entries (rendered everywhere else)

Scope

For each of Agentic + Claw:

  1. Add siblingPlanets loader to the build (read from a vendored planets.json mirror — they need to add 6th + 7th mirror files)
  2. Add cosmos rail UI to masthead (agentic-planet/src/components/Nav.astro, claw-planet/src/components/Header.astro)
  3. Style cosmos chips per atmosphere (cockpit register for Agentic, study-reference for Claw)
  4. Add the 6 sibling icons inline in their respective Nav/Header (or vendor a copy of the 5-mirror palette)
  5. Mobile patterns per cosmos-nav-playbook.md § Mobile patterns

Next steps

  1. Decide: vendor the icon palette as a 6th + 7th mirror, OR import-and-render at build time
  2. The drift audit script will need updating to know about 6 mirrors total + accept "mirror count = N planets" instead of hardcoded 5

File pointers

agentic-planet/src/components/Nav.astro
claw-planet/src/components/Header.astro
learning-docs/docs/reference/cosmos-nav-playbook.md     # mobile patterns + atmosphere variants

Workstream C — 🔗 Cross-planet About cross-linking (deeper)

Phase 3 (8 May) updated each planet's About prose to mention all 7 planets. The next iteration: every planet has a persistent footer or sidebar showing all 6 sibling planets as named chips with taglines (not just buried in About prose).

Status

🟢 Phase 3 baseline shipped. Cross-linking exists in About pages (CMD ASCII map, Plain AI family paragraph, Shift cosmos map, Agentic About new, Claw About new).

Foundation already laid

  • Each About page has cosmos chip rendering
  • Sibling planets data is data-shaped (slug · name · url · tagline) — easy to render anywhere

Scope

  1. Persistent footer or sidebar with all 6 sibling planets named — not just at the top of mastheads
  2. Inline mentions — when a planet talks about another (e.g. CMD mentions Plain AI), auto-link to the canonical URL
  3. "You may also like" or "Related" sections — algorithmic cross-promo based on topic overlap (e.g. CMD entry about agents → link to Agentic recipes)

Next steps

  1. Decide which surface to add (footer vs sidebar vs floating chip)
  2. Per Cosmos Philosophy, atmosphere autonomy stays — each planet renders its own way
  3. Voice rule: cross-link copy must use Sush voice (no "check out our other amazing products")

File pointers

aguidetocloud-revamp/layouts/partials/footer.html
guided/src/components/layout/Footer.astro
shift/src/layouts/BaseLayout.astro                       # has footer inline
agentic-planet/src/components/Footer.astro
claw-planet/src/components/Footer.astro
plainai/build-shared.mjs                                 # footer() function

Workstream D — 🔍 SEO across the cosmos

Each planet has its own SEO surface, but the cosmos as a family of related sites has no shared SEO strategy. This workstream binds them.

Status

🔴 Not started for the cosmos as a unit. Each planet has its own meta + sitemap independently.

Foundation already laid

  • Each planet has unique purpose-built brand mark (good for distinct OG images)
  • Voice-tone audit done (Phase 2) — copy across planets is on-brand
  • Manifest gives canonical URLs for cross-references

Scope (in priority order)

  1. Sitemap cross-linking — each planet's sitemap.xml could include <sitemap> references to sibling planets (sitemap index pattern)
  2. JSON-LD Organization schema — Earth declares the parent organization with sameAs links to all subdomain planets; each planet declares itself as part of the Organization
  3. OG image polish — every planet's homepage + key pages should have a properly designed 1200×630 OG image (Guided already has one at public/brand/guided-og-image.svg; others vary)
  4. hreflang setup — only relevant if a planet has multilingual content. Plain AI's curriculum work was prepping this (orphan branch curriculum-wip).
  5. Canonical URL audit — every page across every planet should have a <link rel="canonical"> pointing at its own definitive URL (not subdomain confusion)
  6. Robots / noindex discipline — Claw is noindex by design (per its launch rules). Verify other planets have appropriate robot settings.
  7. Microsoft 365 schema markup for cert pages on Guided (FAQ schema, Course schema)

Next steps

  1. Audit current state per-planet — make a small seo-audit-2026-MM-DD.md doc (parallel to the voice-drift + logo-audit pattern)
  2. Decide which sub-workstreams are P0 (sitemap cross-linking + Organization schema are cheapest, biggest win)

File pointers

aguidetocloud-revamp/static/sitemap.xml                  # Hugo-generated; check Hugo config
guided/public/sitemap.xml                                # Astro generates; check astro.config
shift/public/sitemap.xml
plainai/build.mjs                                         # custom sitemap generation
agentic-planet/...
claw-planet/...

Workstream E — 🌐 New custom domain purchase

Sush is considering buying a new domain for one or more planets. Affects branding, DNS, SSL, Cloudflare Pages config, and possibly the cosmos law.

Status

🟡 Decision pending Sush. No technical work until decided.

Foundation already laid

  • Universal Cosmos Law #7 says lotus is the default for any Earth-family planet — but a planet on a custom domain may legitimately want its own visual identity from launch (and that planet may be planet-class, not Earth-family)
  • The [cosmos] config block in planets.toml has parent_site field — a planet on a custom domain can override it

Scope (decision tree)

  1. Which planet(s) get the custom domain?
  2. Why? (Brand independence, SEO authority, project graduation, marketing)
  3. Domain name pattern — .com (memorable), .dev (techie planets), .ai (AI planets), .guide (already aguidetocloud)
  4. Cosmos identity question — does the new-domain planet stay in planets.toml (i.e. still part of the cosmos family) or graduate out (its own universe)?

Next steps

  1. Sush picks a candidate planet + domain
  2. Update Universal Cosmos Law #7 if the new planet is custom-domain-but-still-cosmos-member (lotus might not be the right default for a different brand identity)
  3. Cloudflare Pages custom domain wiring + SSL + DNS
  4. Update parent_site in [cosmos] for any planet that's now hosted off-family

File pointers

aguidetocloud-revamp/data/planets.toml                   # [cosmos] parent_site
learning-docs/docs/reference/cosmos-philosophy.md        # may need Universal Law #7 amendment

Workstream F — 🎙️ Voice re-audit (cycle 2)

Voice drift audit was 8 May 2026. Per the audit doc itself: "Re-run after every major content push." — and after Phase 4c and beyond, there's been content drift to re-check.

Status

🟢 Cycle 1 shipped. Cycle 2 is the next pass.

Foundation already laid

  • voice-drift-2026-05-08.md is the canonical pattern — methodology, per-planet section, action lists with priorities
  • Voice fingerprints are documented in voice-and-tone.md + plain-ai-voice-guardrail.md
  • Forbidden words list exists + is applied in CI on Plain AI (and could be extended to other planets)

Scope

  1. Read each planet's hero + About page (~14 files)
  2. Check against voice fingerprints + forbidden words
  3. Capture findings in voice-drift-2026-MM-DD.md (next dated file)
  4. Generate edit list with priorities (P0/P1/P2)

Next steps

  1. Wait for cosmos atlas + Phase 4d + Workstream C to ship (so there's actually new content to re-audit)
  2. Then re-run the audit pattern from voice-drift-2026-05-08.md
  3. Re-audit cadence target: every 2-4 weeks during active development; quarterly thereafter

File pointers

learning-docs/docs/cosmos/voice-drift-2026-05-08.md       # cycle 1 (the pattern)
learning-docs/docs/reference/voice-and-tone.md            # voice fingerprints
~/.copilot/plain-ai-voice-guardrail.md                    # forbidden words

Workstream G — 🪶 Misc + tooling polish

Smaller items that don't deserve their own workstream but are worth tracking:

Item Effort Foundation laid Notes
Apple-touch-icon SVGs for Shift/Agentic/Claw/Plain AI/CMD 30 min Existing favicons; iOS auto-discovers via <link rel="apple-touch-icon" type="image/svg+xml"> (Safari 12+) Defer until purpose-built marks settle (after atlas)
OG image generators for Agentic + Claw 1-2 hrs each Plain AI per-card OG generator pattern in build.mjs:211 Each planet's atmosphere → its own OG canvas
Cosmos drift audit → GitHub Action / nightly cron 1 hr Script exists at learning-docs/scripts/cosmos-drift-audit.mjs exit 0/1 Wire as a repository_dispatch against all 5 cosmos repos; alert on drift
Phase 4b mockup pattern → reusable 1-2 hrs Pattern in phase4b-mockups.html (session-state) Generalise to a "Sush mockup template" — useful for future design-decision sessions
Lotus PNG vendoring for new planets 30 min Earth's lotus webp is the canonical source Pre-generate 32/180/512 PNG variants once; vendor on each new planet's first deploy
Cosmos SVG sprite sheet 2 hrs All 5 mirrors duplicate the same SVGs Could centralise into one cosmos-icons.svg file with <symbol> elements; each planet <use href="#guided"> — solves drift entirely (compile-time linking)
Cosmos data feed (cosmos-index.json star) 2-3 hrs Manifest + drift audit + onboarding checklist Public JSON describing the cosmos topology — agent-readable, MCP-friendly. Companion to the existing cmd-index.json pattern.
  1. First: Atlas Workstream A — the cosmos atlas session is in flight; let it finish. Drift audit is its parity check.
  2. Then: Workstream C (cross-linking) — quick wins. Once the atlas exists, embedding it (or chip strips of all sibling planets) into footers across planets is fast.
  3. Then: Workstream B (Agentic + Claw two-way rail) — cleans up the "one-way carve-out" that was always meant to be temporary.
  4. Then: Workstream D (SEO) — bigger lift; needs an audit-doc cycle first. Sitemap cross-linking is the cheapest win.
  5. Then: Workstream F (voice re-audit cycle 2) — wait until enough new content has shipped (post atlas + Phase 4d + footer work) to be worth re-auditing.
  6. Anytime: Workstream E (custom domain) — parallel-able; pure decision work followed by DNS/SSL/Cloudflare setup.
  7. Backlog: Workstream G items — pick whichever fits the session's slack.

What this doc is NOT

  • Not a brand book — that's voice-and-tone.md + cosmos-philosophy.md
  • Not a code playbook — each planet's own playbook owns its rules
  • Not a deploy guide — that's deployment-playbook.md
  • Not the Status Table — that's cosmos-audit.md

This is just the next-up roadmap from 8 May 2026, written so any future session can pick up a workstream cold without context-loading from chat history.

Established: 8 May 2026, end-of-day session. Update discipline: each workstream's "Status" line should be kept current. When a workstream ships, move it to a cosmos/<workstream>-shipped-2026-MM-DD.md retrospective and link from here.