This is a demonstration · Synthetic data, not a customer project
Orbita Billing is an invented subscription-billing product. Every component, interface and unknown below was produced by 1ADK from a synthetic analysis, through exactly the pipeline your own project would use — but there is no such company and no such code.
Build the same thing for your own system — the first map is free, and 1ADK never gets access to your repository.
What is known
What this project is made of, what talks to what, and what nobody has established.
The same interfaces as a list. Open Map on a larger screen to see their connections.
Map: 11 components, 4 interfaces on this page. Lists give access to the rest.
Coverage and detailed report
How well the system is known
Fully established: 49. In part: 41. Could not be established: 78.
How much of this project is established
24 things recorded. Each row is a question asked of every one of them.
| What we looked for | Where it stands |
|---|---|
| Identity |
Identity
24
Matches: 7
Minor difference: 17
7 — Established
17 — Partly established
|
| Purpose |
Purpose
24
Minor difference: 24
24 — Partly established
|
| Structural placement |
Structural placement
24
Matches: 8
Unknown: 16
8 — Established
16 — Could not be established
|
| Dependencies |
Dependencies
24
Matches: 4
Unknown: 20
4 — Established
20 — Not looked at yet
|
| Interfaces |
Interfaces
24
Matches: 5
Unknown: 19
5 — Established
19 — Not looked at yet
|
| Data usage |
Data usage
24
Matches: 4
Unknown: 20
4 — Established
20 — Not looked at yet
|
| Algorithm |
Algorithm
24
Matches: 2
Unknown: 3
Planned: 19
2 — Established
3 — Could not be established
19 — Does not apply here
|
| Runtime |
Runtime
24
Unknown: 24
24 — Not looked at yet
|
| Tests |
Tests
24
Unknown: 24
24 — Not looked at yet
|
| Ownership |
Ownership
24
Unknown: 24
24 — Not looked at yet
|
How much has been looked at — the thinnest questions first
What needs attention
-
Open question Is changing plan safe to submit twice?
About Change plan
A double submission could charge the difference twice.
-
Open question What does the dunning worker do after the third failed retry?
About Dunning worker
A subscription could be retried forever, or silently abandoned, and nobody can say which.
-
Open question Is the provider callback protected against being replayed?
About Charge settled or failed
A repeated callback could mark a charge settled twice.
-
Open question Where is the customer data actually stored, and in which country?
About Orbita database
It decides which rules the product has to meet.
-
Open question What is on the work queue besides email?
About Work queue
Work nobody has listed is work nobody is watching.
What is dangerous — every risk, worst first
What nobody has established — every open question, most urgent first
Components
Orbita Billing (Application)
Billing service (Service)
Customer portal (Application)
Dunning worker (Service)
? What does the dunning worker do after the third failed retry?
Invoice PDF renderer (Service)
Subscription service (Service)- Orbita Billing
- Billing service
- Customer portal
- Dunning worker 1 open question — Nothing dangerous has been recorded about this. What is open is that nobody has established the answer.
- Invoice PDF renderer
- Subscription service
Outside this system
Depended on, and not this project's to change.
Where the data lives
| Where | Kind | Who touches it | State |
|---|---|---|---|
| Orbita database 1 open question — Nothing dangerous has been recorded about this. What is open is that nobody has established the answer. | Database | Read by 1, written to by 2. | Active |
| Work queue 1 open question — Nothing dangerous has been recorded about this. What is open is that nobody has established the answer. | Queue | Read by 0, written to by 1. | Active |
Interface registry
| Purpose | Source | Network | Target | Kind | Operation | State |
|---|---|---|---|---|---|---|
| Asks the payment provider to take money from a card. | Billing service | route not established | Payment provider | rest | POST /v1/charges | Active |
| Carries failed charges to the worker that retries them. | Billing service | route not established | Dunning worker | queue | CONSUME billing.retries | Active |
| Lets the customer portal read and change a subscription. | Customer portal | Edge proxy | Subscription service | rest | DELETE /api/subscriptions/{id} +1 | Active |
| Lets the customer portal read and change a subscription. | Customer portal | Edge proxy | Subscription service | rest | POST /api/subscriptions/{id}/plan | Active |
| Lets the payment provider report the outcome of a charge. | Payment provider | Edge proxy | Billing service | webhook | POST /webhooks/provider | Active |
What this page does not answer
-
Not here Why does it exist?
An analysis reads what code does, never why anybody wanted it. Nothing here records what this system is for, and writing a plausible answer would be worse than the gap.
-
Not here What depends on it?
What leans on this project as a whole is outside it, and outside what an analysis of it can see. Each part of it does answer this, on its own page.
-
Not here How do we know?
Evidence is kept per thing, so from here it is two moves and not one: open something, then follow Why this is believed.
This is what 1ADK would build for your system
Someone with access to your code runs one instruction with a coding agent they already use. You see the description before it is sent. 1ADK never connects to your repository, your servers or your machine.