GitMir Models · Case study · Cal.com

Scheduling, modeled.
365,422 lines as a product.

Cal.com is the scheduling infrastructure a lot of companies now book on. GitMir read all of it — booking and rescheduling, availability, calendar and payment integrations, the platform API, the app store — and wrote down what the product does rather than how it is written.

290/290 TASKS COMPLETED · ZERO CONFLICTS · ZERO DANGLING REFERENCES

Interrogate the model

One source of product truth.
The right context for every decision.

Which part of the product carries the most risk to change? What is built but never reached? What would a change to booking actually touch? Every answer below is computed on our servers from the model — deterministic, reproducible, sourced.

VERDICTS ARE TEMPLATE SENTENCES OVER MEASURED NUMBERS — EACH STATES ITS SOURCE AND THRESHOLD. NOTHING HERE IS WRITTEN BY HAND OR BY AI.

The model

Explore the graph.

Open an area to see what is inside it, follow a booking from the moment a slot is picked to the moment money moves, and read the states a booking is allowed to walk.

SOURCE github.com/calcom/cal.comLICENSE MITCOMMIT 176037d0afMODEL BUILT SEP 3, 2026STATUS SYNCHRONIZED

THE GRAPH IS LIVE: OPEN AN AREA TO SEE WHAT IS INSIDE IT, SWITCH BETWEEN VIEWS. EVERY SCENE IS ASSEMBLED ON OUR SERVERS AND ARRIVES READY TO DRAW.

What the run produced

365,422 lines in.
A product you can question.

4,329files read in full
365,422lines of code covered
290/290interpretation tasks completed
0conflicts · 0 dangling references
2,103 honest unknowns

References the run could not resolve are recorded with their evidence rather than guessed at. That number is published because a model that never admits an unknown is a model that invented something.

SCOPE EXCLUDES 223,191 LINES — TESTS (184,814), DOCS AND EXAMPLES (16,916), SUPERSEDED MIGRATIONS (10,281), DATA TABLES (5,193), STATIC ASSETS, BUILD TOOLING AND GENERATED CODE. MEASURED, NOT ESTIMATED.

Why this repository

A product with real consequences.

Booking is where software meets money and time

A change to availability or cancellation reaches calendars, payments, notifications and the people on both sides of the meeting. It is exactly the kind of product where "what would this break" is a question nobody can answer from the files alone.

A third shape for the method

A dense product surface with a large integration store — different again from a database platform and from a coding agent. The same run filled it completely, with zero conflicts and no invented references.

Record status

The figures above come from the run ledger and the model index. Cal.com is published under the MIT licence; the model is built from the source at the commit named above.

Three models published.
Yours next.