Skip to content
Ascend GTM Ops — Docs

Platform Name: "Ascend GTM Platform"

ADR-059 — Platform Name: “Ascend GTM Platform”

Status: Accepted
Date: 2026-05-19
Author: Mishaal Murawala
Supersedes: none
Superseded by: —
INVARIANTS-UNCHANGED — this ADR does not add or modify any of the 15 V5 gateway invariants. It is a branding and naming decision only.

Context

Post-cutover (ADR-057, 2026-05-19), the platform consists of Composio (canonical OAuth SaaS layer) + V5 Worker (frozen fallback) + Mem0 (memory) + AI Gateway (LLM observability). The component formerly called “V5 Gateway” or “V5 Worker” is now a frozen fallback — it is one component of the platform, not the platform itself.

The version number “V5” has leaked into platform-level naming (doc headers, handover titles, external site routes like /v5). This creates two problems:

  1. Brand confusion: “V5” implies a versioned product whose next release would be “V6”. The cutover was not a product version bump — it was an architectural expansion (Composio added as canonical layer). The platform doesn’t have a version number; it has a continuously evolving surface.

  2. Component / platform conflation: When the V5 Worker is described as “the platform,” the frozen status reads as “the platform is frozen.” The platform is not frozen. Only the V5 Worker component is frozen.

Decision

  1. System name: “Ascend GTM Platform” is the canonical name for the entire system. Use this in doc headers, marketing copy, and external URLs.

  2. Component name: “V5 Worker” (or “V5 Gateway Worker”) is retained as the name of the specific Cloudflare Worker component that handles AWS/LLM/call_api/batch_execute. It is described as a frozen fallback, not as the platform.

  3. No version suffix on the platform name. “Ascend GTM Platform V5” is incorrect. “Ascend GTM Platform” (no version) is correct. The V5 Worker component retains its name because renaming a deployed Cloudflare Worker has operational overhead; the component name stays.

  4. External site: The /v5 route on ascendgtm.net is renamed to /platform (ADR-059 implementation in mishaal-cloud/ascendgtm-site).

Scope of changes

Doc renames (in this PR)

FileChange
docs/CURRENT-STACK.mdH1: “Ascend GTM — Current Stack” → “Ascend GTM Platform — Current Stack”
HANDOVER.mdH1: “V5 Gateway — Session Handover” → “Ascend GTM Platform — Session Handover”
README.mdArchitecture section: update stale 2-plane diagram to current single-plane
docs/architecture/PLATFORM-DIAGRAM.mdNew file: two Mermaid diagrams (technical + marketing-simplified)

Site rename (separate PR in mishaal-cloud/ascendgtm-site)

  • Route /v5 → /platform
  • Nav and OG tags updated to “Ascend GTM Platform”
  • Marketing-simplified diagram embedded

What does NOT change

  • Worker name in wrangler.toml: ascend-gateway-v5 (Cloudflare resource name — renaming requires a full redeploy and DNS update; not worth it for branding)
  • KV keys, API paths, auth headers — all reference internal identifiers, not platform names
  • .mcp.json server key ascend-gateway (this is an MCP server identifier, not the platform name)
  • Any reference to “V5 Worker” or “V5 Gateway Worker” as a component name — these are correct and intentional

Consequences

  • Platform-level docs use “Ascend GTM Platform” consistently.
  • “V5” survives only as a component qualifier for the frozen Worker.
  • Future components (e.g., a new CF Worker for a specific provider per ADR-058 Path 2) are named by function (e.g., “QuickBooks Worker”), not versioned sequentially.
  • The marketing site route change may require a 301 redirect from /v5 for existing links.