The stack and the API · readings measured 2026-11-01
The technology stack: how this layer is put together
One minute: one sentence saying what we are, which grade each of the eleven building blocks is at, which layer of the five-layer map we occupy, and which APIs really answer.
API status: four measured readings
measured 2026-11-01| Method | Path | Measured | What it is |
|---|---|---|---|
| GET | /healthz | 200 | Public probe |
| GET | /readyz | 200 | Public probe |
| GET | /meta | 200 | Public probe |
| POST | /v1/devices | 401 | Device registration |
green · answers amber · under construction grey · not built red · deliberately closed
1. What the technical service layer is
In one sentence: we are the technical service layer between constellation capacity and the networks of sovereign states — layer ③ of the five-layer map, the load-bearing layer of the building. We supply technology, standards, and the definitions for metering and settlement; we hold no licence, no spectrum and no user data.
One analogy: the internet's "rules for asking directions". The internet reaches everywhere not because one company runs every network, but because every network follows the same rules for asking directions (those rules are called BGP). The rules are not a carrier, hold no licence and own no fibre; yet without them each network works on its own and the whole does not work together.
We are building the same kind of thing: not a carrier, but the rules that let different constellations, different networks and different compute ask each other for directions and settle accounts with each other, plus one ledger desk. The rules are written into documents, the desk can produce an account, and a dispute has a route to a decision. Not one sentence above is an adjective — whether it can be delivered is what section 2 below and the measured readings on the status page answer.
2. Eleven building blocks × four grades (real numbers, not rounded)
The ruler is the same everywhere on this site: implemented = one command on one machine produces a result and an exit code; partial = the core mechanism exists, one outer layer is missing; design only = only design documents, runs nothing; not started = the file says, word for word, "does not exist".
| # | Building block | What it is responsible for | Grade today | What is missing (one line) |
|---|---|---|---|---|
| 1 | Access layer | Brings constellations, ground segment and terminals onto one set of definitions | design only | Not one live link has been connected |
| 2 | Metering and capacity definitions | Fixes "what can be added and what cannot" | partial | 3 pairs convertible / 7 pairs not convertible are registered; a non-convertible pair can only enter a verdict by citing a contract annex, and the annex itself is not yet on the register |
| 3 | Ledger and serialisation | After a restart the ledger is unchanged, duplicate submissions are not double-counted, amounts keep their precision | partial | The kernel passed its own acceptance set; integration with the external service is not done |
| 4 | Proof chain | A stranger, offline, can judge "the account was not altered and not truncated" | implemented | No external timestamp and no public register; the signature uses a demonstration key |
| 5 | Reconciliation and settlement | Establishes who should receive how much, and on what basis | partial | Six commercial parameters are unconfirmed, so formal invoicing is always blocked; cross-party reconciliation is not done |
| 6 | Data sovereignty | A regulator can establish "which country the data is in" without trusting the platform | design only | Three quantities have zero implementation in the kernel |
| 7 | Identity and keys | Who is who, who signed, how keys are managed | partial | Demonstration key; the procedures for issuing and rotating keys do not exist |
| 8 | Service and API endpoints | Reachable by a network, and codable by an outsider | implemented partial | The service shell is implemented and the contract partly; the public address, the test environment and end-to-end integration are still missing |
| 9 | Credentials and test environment | How partners obtain credentials and where they can try things | partial | The credential side is implemented (see below); the test environment itself is still not built |
| 10 | Operations and observability | How to know it is alive, and what happened | partial | Measurement collection, log collection, and backup and restore are all still design, pending confirmation |
| 11 | Entities and authorisation chain | Who authorises whom, who signs the contract | design only | Of seven entity conflicts only one is closed; there is no incorporation document for any national operating entity |
Count (counted item by item, not estimated) — snapshot of 2026-10-31:
implemented 2 (proof chain, service and API endpoints) ｜ partial 5 (metering and capacity definitions, ledger and serialisation, reconciliation and settlement, identity and keys, operations and observability) ｜ design only 3 (access layer, data sovereignty, entities and authorisation chain) ｜ not started 1 (credentials and test environment). 2 + 5 + 3 + 1 = 11, which matches the number of rows.
This cell moved on 2026-11-01: block 9, "credentials and test environment", moved one grade up from "not started" to "partial" — the credential side has been built and measured (reference names are 32-character random strings and cannot be guessed; five consecutive rejections with the same credential lock it for 15 minutes; at most 60 requests in 60 seconds; strike one credential off the ledger and the next request cannot get in; change one character in a ledger line and that line is void on the spot), but the test environment itself still does not exist. Recounted today: implemented 2 / partial 6 / design only 3 / not started 0, 2 + 6 + 3 + 0 = 11.
3. Of the five layers, we stand on the third
4. Three endpoints answer, the rest are under construction
The external contract registers 42 operations — 42 is a contract-operation count, not an interface count; operations and interfaces are not one-to-one, and the two registers cannot be added together. The interface register is a second book: 36 interfaces (ledger IF-01–IF-36), of which 3 have measured evidence and 33 do not; there are also 5 public probes, not counted in these 36 (3 of the 5 are reachable from the public internet; the other 2 are implemented but deliberately not exposed). What has actually been turned into something you can call is three write endpoints plus three public probes:
- Device registration
POST /v1/devices - Device heartbeat
POST /v1/devices/{id}/heartbeat - Usage reporting
POST /v1/billing/events - Three public probes
GET /healthz,GET /readyz,GET /meta(no credential needed)
Measured from the public internet on 2026-11-01: all three probes answered 200, and all three write endpoints answered 401 without a credential. The reading for each is on neutralorbit.org/en/status. So what actually answers is the 3 write endpoints and the 3 public probes above; the other 39 operations are not implemented in the service (39 + 3 = 42 — that is the operation book; another 2, proof-package verification, are implemented but not exposed, so only 3 of the 5 probes are reachable from the public internet). Being written in the contract does not make an operation run — this page does not count them as live.