What the words mean

The words HQ and the terminal use for the map and what's on it. The Guide page in /myorg:hq shows the same list.

The map

  • Mapped: On the code map: every file in the repo, the blocks and modules it falls into, and how they connect. The map covers every file from the start, and /myorg:refresh brings it up to date in seconds.
  • Block: A top-level part of the repo on the map, such as Server or Worker. The Map shows one card per block.
  • Module: A unit of code inside a block: a package, service or folder the scan recognized from its manifest or layout.
  • Area: Any named part of the map: a block or a module.

The semantic map

  • Semantic map: What your agent writes about the code: capabilities, features, risks and decisions, each citing the files it comes from. /myorg:semantic refresh keeps it current.
  • Charted: How much of the code the semantic map has read closely and explained. It counts the code in files that current, valid records cite, file by file, so citing one file doesn't claim the rest of its folder. Complete is 100%: every code file cited.
  • Not yet charted: Mapped, but nothing explains it yet. A /myorg:semantic refresh with no new changes to process charts the next part, about three minutes each.
  • Healthy: At least 60% of the code is charted, and no block holding 5% or more of it is left blank. Gradual charting stops here; /myorg:semantic refresh --chart gets there in one go, and --chart --all charts the rest.

What the semantic map records

  • Capability: Something the system does, such as sign-in or billing, with the files that do it.
  • Feature and feature group: Capabilities grouped into what a user would recognize. HQ's board shows at most seven feature groups.
  • Risk: A known threat to correctness, availability or trust, checked against the current code before it's trusted.
  • Decision: A deliberate technical or product choice, checked against the current code before it's trusted.

Health and what's due

  • Test coverage ring: The ring on a block card. When a test run measured it, it shows how much of the block's code the tests cover; otherwise it reads n/a.
  • Stale: Behind the code: commits landed since the map was last brought up to date. The Guide names the command that catches it up.
  • Needs your attention: What's due now, most important first: the same list /myorg:priorities shows.
  • Guard level: How strictly getmyorg checks your agent's commands and edits in a session: strict, guarded, relaxed (the default) or off. It's yours, in every repo; change it with /myorg:config guards.
  • Gate mode: With it on, the guard asks you in Claude Code's permission prompt about every command that isn't routine. It's for when you've turned Claude Code's own prompts off; change it with /myorg:config gate.

Docs for getmyorg v0.5.21.