systemap map

A generated map of what the parts of systemap are and what they are to each other: 15 components and 3 actors, 54 flows, five layers. Facts from 57014136aa.

Layer
Zoom
Journey
System mapOUTSIDE THE PACKAGEthe people and the runnerthat use itSYSTEMAPone command-line process; nothing is fetched, nothing is served1OPERATE2GATHER3MEAN4DRAW5KEEP TRUEPlacerwhat places the cardsCLIthe commandsFactsExtractorwhat reads the codeScaffoldnever overwrites a file that exists: an upgrade of systemap edits nothing init wrote, so a pinned workflow is bumped by handwhat init writesConfigthe configurationChangeDetectorwhat a branch changedSkillthe procedure the agentfollowsFiguresa picture for a documentPagethe page you openCIthe runner that refusesModelthe map as writtenRouterwhat finds the routesSchematicwhat draws the mapMaintainerthe person who confirmsAgentthe agent that drawsJudgementwhat asksCheckwhat refusesDescribewhat the picture showscommandscheckinitplaceinit, skillextract--base, deltacheckrenderfigurejudgementdescriberender to comparerender to compareinterface rulesettingspackage rootsroots, tests dirname, pathsfigures tableignoresanswers, sdksstartermap.jsonmap.jsonentry pointssurfaceschange mapreachcards, flowspositionsclaimsclaimstopology, meaningmodelroutes, labelsgutters, seatsroutes, seatsgeometryregion order, scoresvg, detailsvggeometrygeometrythe picture in numbersthe pagethe fixverdictproceduremap/model.pycorrectionsmodelsecond-pass listjudgement answers

Scroll to zoom, drag to pan, click a component to frame it, Escape to go back. From the keyboard: Tab moves across the cards, Enter opens one, Escape closes it, the left and right arrows switch readings or step a journey.

System context Data flow Control flow What judges declared built outside actsmeasures

Every card is code in the tree today: the check refuses a component whose modules or entry are not in the facts. A dashed card is an actor outside the code. A dot in a card's top corner marks a note; the panel shows it. Every line carries what it moves and is coloured by the layer it belongs to. A dashed line is a declared flow: no import in the facts joins its two ends; the panel says of every flow whether it is observed, external or declared. A card standing on a second card opens a map of its own; the panel shows a preview of it and a button that opens it in place, over this page. Click a component; press Escape to clear it and return the view; the arrow keys switch readings, or step a journey while one is on; double-click a region's name to frame the region. Text is drawn at 11px and never smaller: at Fit it is scaled down, and zoom brings it back.

Components by region; click one to focus it

1OPERATE

2GATHER

3MEAN

4DRAW

5KEEP TRUE

·OUTSIDE THE SYSTEM

Invariants the rules the chips in the panel point at

  1. No counts of code or tests anywhere on the page: the map explains what the system does, not how much of it there is (README, Principles).
  2. A component is something a reader would point at and name; a module is not a part (README, Principles).
  3. Edges carry the relationships; prose is for emphasis (README, Principles).
  4. The map draws what exists today: every module a component names is in the facts, and nothing on the map is a plan (README, Principles).
  5. Positions are fixed in the model, written once by systemap place or by hand, and the checker decides, so the same system always draws the same picture (README, Principles).
  6. The agent authors, the checker refuses, the person reviews (README, Principles).
  7. The map is built in passes; the second pass is the point (README, Principles).
  8. The page fetches nothing and depends on nothing (README, opening).
  9. An unknown configuration key is refused, never ignored (src/systemap/config.py, load: 'unknown key').
  10. Every ignored module needs a reason (tests/test_coverage.py: test_ignore_without_reason_is_a_config_error).