Skip to main content

momo-cogwork × momo-ticket-system — Systems Integration Guide

SRE Internal · Systems Guide · last updated 2026-07-08 · interactive original ↗

This document brings together the operating notes and system flows of two systems:

  • momo-cogwork — the SRE internal desktop tool (Wails v3, Go + Svelte), with tabs for the release list, Config Server, GitLab, ITSM (Jira), Outlook search, eForm to-dos, slide generation and file search.
  • momo-ticket-system — the release-ticket management platform (ticket.fmt.com.tw) that replaces the Excel release-list process; it is also the data source and write target of the momo-cogwork "Release list" and "Config Server" tabs.

momo-cogwork is a client (it uses the /api/ext/* API-key interface); the momo-ticket-system web front-end is for people who sign in (it uses the /api/* JWT interface) — one data set, two fully isolated entry points.

1 · System landscape​

momo-cogwork directmomo-ticket-system connectionconnected by bothblocked / guardedsolid = relation · staticdashed = traffic · animated User / SREdesktopbrowser + Zitadel SSOMOMO-COGWORK · WAILS V3 · GO + SVELTERelease listConfig ServerGitLabITSM(Jira)OutlookeFormSlidesFile searchUpdate noticeMOMO-TICKET-SYSTEM · GO + VUE · GKE/api/ext/* — X-API-Keycogwork uses this/api/* — JWTweb login usersAlloyDB / PostgreSQLOutlooklocal MAPI/COMLocal filesfilesystem APIRCM ConfigX-Api-KeyKrakenDJira / AtlassianCloud OAuthJenkinsBasic AuthtriggerGitLabTOKENserver mergeZitadel IdPOIDC · SSO

Figure 1 — Whole-system landscape: how the desktop tool, the ticket platform and the external systems connect

Key principle: momo-cogwork reads only metadata through momo-ticket-system — "which Jenkins jobs to call", "which configs to change". The actual deployment (calling Jenkins) and the actual write of configuration values (calling RCM) are done by cogwork directly against the target system, never relayed through momo-ticket-system — momo-ticket-system only records afterwards that "this item has been handled".