systemap map

A generated map of what the parts of systemap are and what they are to each other: 16 components and 4 actors, 67 flows, five layers. Facts from 9b8837e4c2.

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 changedTypeSafethe model askedSkillthe 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 asksSecondOpinionwhat asks for a secondopinionCheckwhat refusesDescribewhat the picture showscommandscheckinitplaceinit, skillextract--base, deltacheckrenderfigurejudgementdescribeaudit, triage, --jevrender to comparerender to compareinterface rulesettingspackage rootsroots, tests dirname, pathsfigures tableignoresanswers, sdksanswers, model, cachemap.jsonquestionstyped answersmoves Jev readthe ways in with no walkthe ways in with no walkentry pointsstartermap.jsonmap.jsonentry pointssurfaceschange mapreachcards, flowspositionsclaimsclaimstopology, meaningmodelroutes, labelsgutters, seatsroutes, seatsgeometryregion order, scoresvg, detailsvggeometrygeometrythe picture in numbersthe pagethe fixwhat moved, and whenverdictproceduremap/model.pycorrectionsmodelthe teaching under each linesecond-pass listjudgement answerscards, sentencesjev lines

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

What you are looking at. A card is one part of this system: something a reader would point at and name. Every card is code in the tree today, and the check refuses one whose modules or entry are not in the facts. A line is something moving from one part to another, labelled with what it carries. A reading colours the lines that answer one question, so the same map can be looked at several ways. A journey walks the map one step at a time, the way a run does.

What the marks mean. A dashed card is an actor outside the code. A dot in a card's top corner marks a note, which the panel shows. A dashed line is a declared flow: no import in the facts joins its two ends, so the map is claiming it rather than observing it; the panel says of every flow whether it is observed, external or declared. A card standing on a second card holds a map of its own, and the panel opens it in place over this page.

How to drive it. Click a component to light what it reaches. Escape clears the selection and returns the view. The arrow keys switch readings, or step a journey while one is on. Double-click a region's name to frame that 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).
  11. check and judgement never reach the network; asking Jev is a separate command that sends nothing without a key (src/systemap/jev_cli.py, docstring).