Example · self-hosted service

A self-hosted monitoring service: louislam/uptime-kuma

A popular open-source uptime monitor, with hundreds of open issues: what the map looks like for a maintainer with a busy backlog.

getmyorg's map of louislam/uptime-kuma, captured with getmyorg 0.5.18 on 2026-11-17, at commit e6ea9509. Not affiliated with the Uptime Kuma maintainers. Newer releases may differ; the docs track the current one.

Map the repo

Inside the repo, run /myorg:init or $myorg:init. It maps the code, installs the git hooks that keep the map current, and builds the semantic map once: what the code does, in plain words, citing the files it explains. Run /myorg:semantic refresh --chart to chart the rest. See Getting started.

What “charted” means

Every code file is mapped from the start. Charted is the share the semantic map has read and explained. Open the map in your browser with /myorg:hq or $myorg:hq: the globe lights up area by area as charting goes, and turns violet when everything is charted. Under it, HQ says in one sentence what the code shows the project is.

All 383 code files are mapped and 99% is charted: the one file left is a stub that only prints TODO. The map found six groups, from monitoring and alerts to status pages, and four decisions already waiting in the issue tracker.

Features

HQ groups what the code does into features, and features into a few groups an outsider would recognize. Open a group to see each feature's state, with open issues placed on the features they touch.

Monitoring alone holds ten features, and hundreds of open requests land on the features they ask for, so a busy backlog reads as a short list: what's queued, what's in flight, what's blocked. Issues nobody has touched for a year are set aside rather than crowding the board.

The map, by system

The Map tab's Architecture view draws the same groups as systems, with the imports between them. Switch to By folder for the directory layout.

Six systems in two tiers. Alerts, status pages and the API build on a shared platform of accounts, storage and settings, with monitoring and the dashboard beside it.

What needs you

The Guide tab says what to do next and why, then lists every command in your agent's syntax.

With the map charted, the Guide's first suggestion is to write down a convention, since the repo has no team rules yet.

Make it yours

The map is a draft for you to correct. Rename or regroup with /myorg:semantic curate, write down the conventions your reviewers repeat with /myorg:codify, and give the project a one-line mission with /myorg:anchor goal. We left this repo without one: a goal is its maintainers' to set, not ours. Every command is in the commands reference.

More examples: vercel/chatbot (AI web app), junegunn/fzf (command-line tool).