← bizopsmap

For engineers

Maps built from a project's own files, by field.

Software engineering

A web app codebase as layers, with the path from a payment webhook traced

Web app codebase

Entry points, routes, functions, tables and external services by layer, with churn and coverage.

 Running services with error counts from a traces file

Services and telemetry

Compose services joined to their code; errors and spans from OpenTelemetry traces.

 A codebase at week five of eight, new parts outlined

Architecture over time

One frame per week from git history, no checkout; added parts outlined.

 A delivery plan coloured by days late

Delivery plan

Work breakdown from CSV: milestones, deliverables, work packages, people; days late against plan.

 A BMAD project: requirements, epics, stories and the code they changed

BMAD project

Requirements, epics, stories and the code each story touched, placed by status.

 The BMAD project at its last weekly frame

Sprint history

The BMAD plan week by week from sprint-status.yaml's history; days in status.

 A codebase coloured by the number of practice rules each file breaks

Engineering practice

Five per-file rules: tests, size, bus factor, CODEOWNERS, hotspots.

Every example is made up.