Skip to content
Understand

Find out what you actually own

Most owners inherit software rather than design it. Before anything can be judged or changed, somebody has to write down what is there — accurately, from the code, not from memory.

What is in this category

Actions that produce a description of reality

Every one of these inspects without modifying anything, and refuses to assert what it cannot point at.

Architecture discovery

What the system is made of, how requests flow through it, and where the boundaries actually are — as opposed to where a diagram once said they were.

System inventory

Services, jobs, scheduled tasks, queues, external calls and the things running that nobody remembers starting.

C4 model generation

Context and container views built from the code, with every element traceable to the place it came from.

Sequence analysis

What happens end to end during the flows that matter: sign-up, checkout, the nightly job that everybody is afraid of.

Dependency map

Internal and external dependencies, which ones are load-bearing, and which single failure takes the product down.

Technical debt analysis

Where the cost of change is concentrated, with an estimate of what it is costing you now rather than a generic scolding.

How a discovery action runs

  1. Read-only inspection

    Nothing is modified, nothing is refactored “while we are here”. The procedure explicitly forbids it, because a discovery run that changes code cannot be trusted afterwards.

  2. Inventory before opinion

    The facts are collected and written down before any judgement is formed, so conclusions can be checked against them later.

  3. Evidence for every claim

    A finding without a file and a line is dropped. This is the single rule that separates a real audit from a confident summary.

  4. A result you can compare next time

    The output has a fixed shape, so running the same action in six months tells you what changed.

When to start here

Start elsewhere if

You already have current, trusted documentation

You know exactly which component is the problem

You need a decision today, not a description

The system is two weeks old and you wrote all of it

Start here if

You inherited the system from someone who left

Different people describe the architecture differently

You are about to hire, replace or brief a developer

A rewrite is being proposed and you cannot judge it

Pick the category that matches your worry

Describe the situation in your own words and see the procedure — and its cost — before you spend anything.