Rename Kagenti Medium blog to Rossoctl

[mrsabath]

Summary

Rename the project's Medium blog / publication from "Kagenti" to "Rossoctl" as part of the org-wide Kagenti → rossoctl rebrand.

Scope

• Rename the Medium publication (name + URL slug) from Kagenti to Rossoctl
• Update the publication description and any Kagenti-branded logo/header assets
• Review existing posts for "Kagenti" references (update where it's the project name; leave historical/verbatim context as-is)
• Update any links pointing to the blog (docs, website, README, social profiles)

How to rename a Medium publication (for whoever does this)

Medium splits this into two controls in two different places. There is no single "rename" button, which is the usual source of confusion. You must be the publication owner for both.

A. Change the display NAME (self-service). This is what readers see; it does not change the URL.

1. Sign in as the owner, open the publication home page.
2. Go to publication Settings (direct URL: https://medium.com/<current-slug>/settings), or avatar menu → Manage publication.
3. Under General, edit the Name field → save.

B. Change the URL / slug (owner-only, but via a support request — no self-service UI). Medium removed self-service URL editing, so even as owner you file a ticket:

1. Sign in as the owner account.
2. Go to https://help.medium.com/hc/en-us/requests/new ("Submit a request").
3. Ask them to change the publication URL, including:
   • Current URL: https://medium.com/kagenti-the-agentic-platform
   • Desired URL: https://medium.com/rossoctl-the-agentic-platform (or another slug)
   • State that you are the owner (they verify against the requesting account).

Blocker to watch: the desired slug rossoctl-the-agentic-platform already exists as a separate publication (the main-repo docs already point there). Medium cannot assign a slug that is taken. So either:

• treat the existing rossoctl-… publication as the keeper — migrate the old Kagenti posts into it and retire the old one (no ticket needed), or
• free up the rossoctl-… slug first (delete/re-slug it), then file the ticket for the old publication.

Caveat: old post URLs under medium.com/kagenti-the-agentic-platform/... do not auto-redirect after a rename. Re-verify each linked post afterward.

Status: URL-change support request submitted 2026-07-27 (mrsabath, owner). Awaiting Medium.

Code references to update

Org-wide scan (2026-07-27) found the old publication slug medium.com/kagenti-the-agentic-platform still referenced only in the website repo (rossoctl/.github). The main rossoctl/rossoctl docs are already migrated to medium.com/rossoctl-the-agentic-platform (15 refs, no action needed).

Files to update in rossoctl/.github:

• docusaurus.config.ts:169 — navbar "Blog" link points to the old publication
• ecosystem/resources.md:8 — social/resources table Blog row
• ecosystem/welcome-copy.md — "publishes on [Medium]" community blurb
• ecosystem/content.md — 4 historical blog-post rows (Oct–Dec 2025) using the old slug

Note: the content.md rows link to already-published posts under the old slug. Those specific post URLs only redirect if Medium preserves them after the publication rename, so they may need per-URL updates rather than a plain slug swap. Verify each after the publication is renamed.

Context

Part of the Kagenti → rossoctl rename tracked in #1972. Branding surface, so needs owner-account access to the Medium publication.

[mrsabath]

Medium publication renamed to https://medium.com/rossoctl-the-agentic-platform (same publication, so post URLs migrated). Site references updated in rossoctl/.github#105 (navbar Blog link, resources, welcome copy, and the 9 historical post URLs in content.md). Closing.