Skip to content
EmargenEmargenDocs

AdminHow to

Read a repository's analysis

Read a repository’s analysis when you need to know what the code does without reading it. Who may approve a request, say, or where a new engineer should start. The analysis tells you area by area, in words anyone on the team can follow. Repositories and analyses explains the idea behind it.

Before you start

Section titled “Before you start”
Who can
Everyone in the organisation can read the repositories and their analyses.
You need
The repository must be Analysed. One that’s still being read shows how far it got. To see what changed since an earlier analysis, it needs two.
The pictures
The pictures follow a question a customer’s depot managers ask ACME. Who may approve their people’s access requests, and since when? The answers are in the analyses of ACME’s portal and identity-service.

Steps

Section titled “Steps”

  1. Open Admin in the menu (it opens on Models), click Repositories, then the repository’s name. In the pictures, the portal.

    Open Repositories (opens Emargen in a new tab)

  2. Read the Overview tab. Under the Repository facts at the top, Areas opens with a short introduction to the whole repository, then lists its areas, each with one line on what it does.

    The portal's Overview: its facts with Analysis #3 and its recipes, then Areas 4, a sentence on the whole portal, and the areas approvals, people, reports and settings.The portal's Overview: its facts with Analysis #3 and its recipes, then Areas 4, a sentence on the whole portal, and the areas approvals, people, reports and settings.
    1. #3: the analysis you are reading, when it was written, and at which commit.
    2. A recipe the analysis followed, with how many areas it applied to. Click it to read what it asked the analysis to write.
    3. The area that answers the question: approvals.

  3. Click the area to open its overview.

    The approvals area open: its recipes, Written 30 Oct 2026 · at 5bf55dc, a summary, then Purpose, Relevance, Starting points, and Business rules with its first rules.The approvals area open: its recipes, Written 30 Oct 2026 · at 5bf55dc, a summary, then Purpose, Relevance, Starting points, and Business rules with its first rules.
    1. Business rules: what the code allows and refuses. Here, who decides which requests.

    Starting points names the files an engineer should open first. The portal’s approvals area says a depot approver sees requests from people whose home depot they approve for. Administrators cover every depot.

  4. Check the analysis is up to date. In the Repository facts, Head is the commit Emargen’s copy is at. Analysis names the commit the analysis was written at. When the copy has moved on, the repository shows Out of date, beside its name and in the Status column of Repositories. In the portal’s facts in step 2, both name the same commit. Every repository in the pictures is analysed at its head.

    An out-of-date analysis still describes the code as it was when it was written. Ask someone who may analyse repositories to click Analyse on its Analysis tab. Or ask them to set its Schedule there, so it’s analysed again as the code moves.

  5. To see what changed, open your repository from Repositories, then its History tab. It lists every analysis of it, newest first. The pictures show identity-service’s, where the rules themselves live.

    Open Repositories (opens Emargen in a new tab)
    identity-service's History: #3, Current, Ana Ruiz, 604a2d1, Ready, 30 Oct 2026; #2, Ana Ruiz, 1711a0b, Ready, 2 Oct 2026; #1, Ana Ruiz, c2518b4, Ready, 27 Apr 2026.identity-service's History: #3, Current, Ana Ruiz, 604a2d1, Ready, 30 Oct 2026; #2, Ana Ruiz, 1711a0b, Ready, 2 Oct 2026; #1, Ana Ruiz, c2518b4, Ready, 27 Apr 2026.
    1. #1: the earliest analysis. Click it.

  6. Read the earlier analysis, and compare it with the current one on Overview. Read the same section in both, like Business rules. Each analysis describes the code as it was at its commit, following the guidance and recipes it had then. No analysis records the day a rule changed. For “since when”, read the rule itself, which may say so, or the code’s history.

    identity-service's overview in analysis #1: among its business rules, Only administrators approve or decline requests, and never their own; the approver at a depot sees the requests routed to them but cannot decide them.identity-service's overview in analysis #1: among its business rules, Only administrators approve or decline requests, and never their own; the approver at a depot sees the requests routed to them but cannot decide them.
    1. In April’s #1, only administrators could approve requests. The current #3 says requests go to the manager of the requester’s home depot, if they hold the Approver role there. Administrators still decide at every depot.

    All analyses goes back to the list.

What you get

Section titled “What you get”

An answer based on the code at the analysed commit. To pass it on, work it into a topic. The agent reads the same analyses there, and the code where it needs more.

Next

Section titled “Next”

How to

Page by page