For software owners

You own the code. Do you own the understanding?

Understand what you actually built.

A map of your components, their dependencies, what is claimed about them and the evidence behind each claim — built from an analysis run by a coding agent you already trust.

Build your project map — free See the map

No repository access. No source-code upload to 1ADK. Someone with access to the code runs one instruction — you, your developer, or your agency. Nothing to install, and 1ADK gets no access to anything.

app.1adk.com / projects / orbita-billing demonstration data

Orbita Billing

68 open gaps medium last scan 2 hours ago

Requirements, and what was actually found

REQ-0142

Password reset completes within 5 seconds

Should Timeout ≤ 5 s, enforced Is Configuration declares 30 s

High risk Observed Observed — found in the implementation

REQ-0143

Reset emails are delivered through a queue

Should Asynchronous delivery Is Redis queue, one worker

Confirmed Verified Verified — confirmed by evidence

REQ-0151

Payment webhooks are idempotent

Should Repeat delivery is safe Is Unknown — nobody has confirmed this

Unknown Declared Declared — stated by documentation

Components discovered 412 Available

Interfaces registered 12 of 19 Available

Runtime behaviour not measured Partial

Recovery procedure no evidence found Temporarily unavailable

Should

Timeout ≤ 5 s, enforced and measured

Is

Configuration declares 30 s; runtime not measured

The parts of your system, and what is still unconfirmed.

Not a diagram somebody drew from memory. A picture assembled from what an agent found in your own repository, with the uncertain parts left visibly uncertain.

Container Billing API PHP 8.2 · 42 endpoints

Datastore PostgreSQL orbita_main · 34 tables

Queue Redis · emails 1 worker · retries 3

Endpoint POST /auth/reset No rate limit found

External Payment provider Not confirmed

Worker Invoice worker cron · nightly

Endpoint POST /webhooks/payment Repeat delivery not confirmed safe

Boundary Reconciliation Outside the scanned boundary

Service Log pipeline One masked value written

Confirmed by evidence Found, with a gap Found, and it is a risk Nobody has confirmed it

Orbita Billing — a demonstration project, rendered live by the 1ADK design system. Every figure below is that project's, not a customer's.

412 components discovered

12 of 19 interfaces registered

68 gaps left open rather than guessed

Code can belong to the company while understanding of the system leaves with a person.

That is not a documentation problem. It is an ownership problem, and it only becomes visible at the moment it is most expensive.

When someone leaves
When the agency changes
When it is time to sell

How it works

Your agent reads the code. We never do.

The analysis runs in a tool you already trust, on your side. What reaches 1ADK is a description of your system that you have seen and approved first.

1ADK writes the instruction

You get a set of instructions for the coding agent you already use. Nothing is installed, nothing is connected.
The agent reads your system

Claude Code, Codex or a local model does the reading, in the environment you choose, with the access it already has.
You see what will be sent — and approve it

The names of the parts, what each one is for, what it connects to, and what that conclusion is based on. Not your source files.
And when the system changes, you run it again

1ADK builds the picture, and the next analysis shows you what moved.

What will be sent

example

Billing API container · PHP 8.2 · 42 endpoints
PostgreSQL datastore · 34 tables · no contents
Redis · emails queue · 1 worker
POST /auth/reset endpoint · no rate limit found
Payment provider external · not confirmed

Not in this transfer

Your source files
Secrets, tokens and .env
Database contents
Customer data

Evidence

Claims carry their receipt. Unknowns stay unknown.

For every statement it can support, 1ADK shows the file, configuration or document it came from. What it cannot support, it marks unconfirmed rather than filling in with something plausible.

The password reset endpoint takes 30 seconds, not the five the requirement asks for.

Where it came from Observed config/auth.php:42 Observed — found in the implementation
What the requirement said Timeout ≤ 5 s, enforced and measured — REQ-0142
How sure we are low Evidence confidence runtime was never measured
Why it is red High risk because it is a security requirement, not because it is unfinished

A claim you can follow to its source

Every part of that record points back at something real: the line of configuration, the requirement it contradicts, and the reason the colour is what it is. Nothing on the map asserts anything it cannot show you.

See it on the map

Unknown — no limiter found in the code; absence not proven

Unknown — outside the part of the system that was scanned

Unknown — nothing measured it while it was running

And what nobody has confirmed

Not found is not the same as proven absent. An unknown comes with the reason it is unknown, which is the part you can act on — and it is left on the map rather than quietly filled in.

Declared Reset completes in 5 s REQ-0142

Observed Configuration says 30 s config/auth.php:42

Both sides, never silently resolved

When your documentation and your system disagree, you see both and which is which. 1ADK does not pick one and move on.

What changed

Documentation describes a system. 1ADK shows how the understanding changed with it.

Run the analysis again and the picture does not simply refresh. It tells you what arrived, what moved, what went away — and which of yesterday's answers it can no longer stand behind.

Container Billing API PHP 8.2 · 42 endpoints

Datastore PostgreSQL 34 tables · verifiedevidence file moved

Queue Redis · emails 1 worker3 workers

External Payment provider not confirmedconfirmed · contract found

Endpoint POST /webhooks/payment idempotency not confirmed

Worker Legacy invoice cron no longer in the system

1 Added
1 Changed
1 Removed
1 No longer confirmed
1 Unknown resolved

The same demonstration project at two scans. 1ADK makes no claim here about how often you would run it, or about what any plan includes.

The boundary

What 1ADK never asks for.

The analysis runs on your side. 1ADK receives a reviewed description of your system and never opens a connection to your machine.

Access to GitHub, GitLab or any repository
SSH keys or infrastructure tokens
An archive of your source code
Production credentials or your .env
A database dump
An inbound connection to your machine

The honest limit If you run the analysis with a cloud coding agent, that agent processes your code under its own terms. 1ADK's boundary is the 1ADK service. Choose a local model and the analysis can stay entirely inside your own infrastructure.

When this matters

The moment the understanding changes hands.

The condition is always there — understanding of the system lives in people rather than in the company. These are the moments it stops being theoretical.

And when it is not for you If you are technical, you want a single answer today and you will not need it again — your coding agent on its own is enough. 1ADK is for the case where the answer has to outlast the person who asked it, and be checkable by someone who did not.

A key developer is leaving

The person who knows why it was built that way is working their notice. The code stays; the reasoning is about to walk out with them.

You want to change agency — and are afraid to

Moving contractors means handing your system to someone who has never seen it, with no independent account of what they are inheriting.

It was built fast, partly by AI, and nobody holds the whole

The product works and ships. What is missing is anyone who can say what it now contains, or which parts nobody has checked.

A new technical leader is taking it over

Their first months are spent reconstructing what already exists, from the people who are already busy.

Find out what you actually own.

The first map is free. Someone with access to the code runs one instruction — you, your developer, or your agency.

Build your project map — free Already have an account

Do I have to give 1ADK access to anything?

No. Not your repository, not SSH, not production, not your .env.

Who runs the instruction?

Anyone with access to the code — you, an in-house developer, your agency, or the person who is leaving.

Do I need to install something?

No. The instruction is copied into a coding agent the runner already has.