Check every claim

A promise on a site and the app on your desk drift apart easily: the text is written in one place and the code in another. Without something comparing them you would find the gap only after paying.

So every promise has a row tied to the code that delivers it. There are 97 rows today, spread across seven parts of the product.

• Support

  The support promise on your plan points at the service your request actually lands in.

• Fingerprint > Change values

  What you see in the Fingerprint window is what the profile gets: one set of rules for the screen and for the launch.

• Bulk actions

  The line on your plan points at the screen where you actually perform them.

A row holds three things and nothing else: what is promised, where it is done, and what checks it. So any row you pick takes you to a file rather than to an argument.

The middle column is a path you can open, not a folder and not the name of a part of the app. The right one is a check you can run yourself, and it turns red when the behaviour breaks.

1. 1

   Read the claim

   Take the row about the proxy covering all of a profile's traffic.

2. 2

   Open the file

   Open apps/desktop/src/lib/forkEngine.js: the rule for the engine is written there.

3. 3

   Run the check

   Run apps/desktop/test/proxy-covers-https.js: it watches what actually leaves through the proxy.

There are 97 promises in the registry today, and every one below is quoted from the file word for word. The path beside each points into the code from the repository root, and every one of them exists.

The spread is deliberate: engine, network, team, money, support, app, languages. You will read the rest of the registry exactly the way you read these.

A document nobody executes rots within a month, and this one would rot fastest, because it is where an inconvenient truth gets quietly edited. So the registry has a check of its own.

It makes seven assertions. Four are about the named thing existing, three are harder.

• You always see the whole list

  At least thirty rows, so a broken read cannot look like a clean registry.

• Every promise names a live file

  The path runs from the repository root and has to exist on disk.

• Every promise names a live check

  The same rule for the right-hand column.

• Every check really runs in the suite

  Its name has to appear in the command that runs that part.

• The check reaches the file it guards

  The hardest of the seven, and the chapter below is about it.

• No empty cells anywhere

  And the file is not the check: a promise cannot be its own proof.

• The most expensive promises are named

  Support, fingerprint, proxy, invitation, paid plan, prices.

File alive, check alive, suite green, and it is exercising something else entirely. Nothing on the screen says so, which makes it the quietest failure there is.

So a check has to reach its file. A mention of the file in a comment does not count as execution.

• By name

  The source of the check names the path or the file name, and too general a root is refused.

• By package name

  The shared package is imported as @armanos/shared, and that name counts.

A written check that no command calls creates the feeling that a place is covered. That feeling is worse than an empty place, because nobody goes back to look.

So the first thing in the whole suite is a check that executes no product code. It compares the check files on disk against what the commands actually call.

• A check on disk that no command calls

  Named in the failure, with the area it belongs to.

• A command that calls a file which does not exist

  A dead path looks exactly like coverage.

• A glob that matches nothing

  An empty pattern runs zero files and reports green.

• An area missing from the root command

  Then all green means green for part of the tree.

• A check written after the summary line

  It runs, it prints, and its result is not counted.

The count of automated checks on this page is measured, not typed. It arrives from a green run of the three real suites.

A red run gives the page nothing: it keeps the previous number rather than a flattering one. Prices and quotas never take this path, because the pricing table reads them from the same package the app uses to decide what you are allowed.

A green check that cannot go red is worth nothing. The method is fixed and boring: break the behaviour the way it really breaks, run the check, and watch it go red for the right reason.

Reading the red message matters as much as seeing it. Red for the wrong reason proves nothing, and neither does a check whose assertions sit below its own summary line.

1. 1

   Break it

   Return the defect to the product file, in the way it actually occurs.

2. 2

   Run the check

   It must go red, and the message must name the real cause.

3. 3

   Read the message

   Red for the wrong reason proves nothing.

4. 4

   Restore

   Put the code back and confirm the green again.

The registry is not only a list of things that work: it carries the two places where measurement failed. WebGPU on Windows is unverified, because the rented machine has no graphics card and Chromium then switches the capability off.

Speech voices on Linux read zero, and zero is the platform norm there. Real Chrome reports none either, while the launch flag that opens the system path gives 13363.

The registry is also a list of what is not sold. A thing with no row is not a claim, and it is not something to count on.

Four of them are asked about often enough to be named here. Each carries the state it is in today, not the one it is heading for.

• Card payment

  The checkout is written and stays inert without keys, so a paid plan is granted to you by hand. apps/server/src/billing/stripe.service.ts.

• Code signing and notarization

  Hardened runtime and entitlements are set, a certificate is not, so your system warns you on the first launch. apps/desktop/electron-builder.yml.

• Terms and refund policy

  Not written. Required for accepting money, not for running the app.

• Proxy resale

  An order is a recorded intent: no money is taken from you and no provider is called. apps/server/src/proxy-store/proxy-store.service.ts.