Contact

The Arhas standard

Every claim has a code path.

A promise enforced by a settings toggle is not a promise. It is a default, and defaults get changed — by a support agent, by a release, by whoever owns the roadmap next quarter. So we stopped making promises we could only keep by remembering to.

This is the list of the things we have made structurally impossible instead, and the rules that decide which numbers are allowed on this website.

01 — Counting a number

How a number earns its way onto this page.

Four steps. They are not difficult, and almost nothing in this industry survives them.

  1. 01

    Counted from the source.

    A figure begins as a count of something that exists in a repository — rows in a table, entries in a library, a constant in a file. It never begins as a target in a planning document. If nobody can point at the thing that was counted, there is no figure.

  2. 02

    Cited on the page.

    The file, and where possible the line, ships next to the number in mono, where a stranger can read it. A number without its receipt is a rumour, and we would rather print nothing than print a rumour in a large typeface.

  3. 03

    Re-counted when the code changes.

    The number is a property of the code, not of the marketing. When the code moves, the number moves. Until the page catches up, the page is wrong — which is why the count is done by the build and not by a human with a deadline.

  4. 04

    Deleted, rather than rounded.

    When a figure cannot be traced back to something countable, it is not softened into "over 600" or "thousands of" or "up to". It is removed. Most of the numbers a website like this would normally carry died at this step.

A worked example

Where 661 comes from.

BRUTAL Optimizer ships 22 optimization modules. Each declares a TweakCount — how many real Windows settings that module writes, each with its own undo. The headline figure is not a summary of those modules. It is their sum, and nothing else. Here is the table, in module order.

Views/OptimizeView.xaml.cs:56-77

  1. 01 197
  2. 02 32
  3. 03 27
  4. 04 20
  5. 05 33
  6. 06 45
  7. 07 28
  8. 08 16
  9. 09 61
  10. 10 15
  11. 11 9
  12. 12 8
  13. 13 24
  14. 14 32
  15. 15 37
  16. 16 8
  17. 17 15
  18. 18 12
  19. 19 12
  20. 20 10
  21. 21 8
  22. 22 12
Sum of TweakCount across all 22 modules
661 named, counted tweaks

Views/OptimizeView.xaml.cs:56-77 — one TweakCount field per module. Exactly five modules carry IsProOnly, which is where "17 of 22 free" comes from: the same table, counted a second way.

This page adds those 22 numbers up when it builds. If they ever stop summing to 661, the build fails and the page does not ship. That is the difference between a number and a claim.

02 — The code path

The guarantee lives in the code path.

Every vendor in every one of our three markets makes some version of these promises. The question is never whether they said it. The question is what happens when someone tries to do the thing anyway. Three cases, one from each product.

BRUTAL Optimizer 01

“It will never defrag your SSD.”

How the promise is usually kept

Defragmenting flash wears it out and buys no speed, so the promise is easy to make. It is usually kept in a tooltip, a line in the release notes, or an advanced checkbox that ships switched off. All three hold for exactly as long as nobody changes the default.

How it is kept here

Before any maintenance pass runs, the drive is asked what it physically is, and Windows answers with a media type. Flash gets TRIM. Only a disk the operating system confirms is spinning is ever handed to defrag.exe. No toggle can override this, because there is no toggle.

Services/StorageHealthService.cs — WMI MSFT_PhysicalDisk MediaType gate

MedOS 02

“It cannot record fetal sex in a radiology report.”

How the promise is usually kept

A policy document, a training deck for the front desk, and an audit some months later that finds the field was filled in anyway. The PCPNDT Act is enforced on the clinic; the software stays neutral and stores whatever it is handed.

How it is kept here

The entry point refuses it. Sex disclosure is blocked in the radiology API where the data is written, and the report text is scanned for disclosure keywords before submission. It is not a warning the user can acknowledge and continue past.

The same shape, one module over: an expired medicine cannot be dispensed. Not warned about at the counter — blocked at checkout. api/pharmacy/ — expired stock refused at the point of dispensing

api/radiology/ · api/regulatory/ — blocked at the field, not flagged afterwards

LabOS 03

“The approver can never be the technician who entered the result.”

How the promise is usually kept

Hide the approve button when a technician is looking at their own result. The button leaves the screen; the endpoint behind it does not. Anyone who can send the request can still approve, and the audit log records a clean two-person release that never happened.

How it is kept here

The check runs on the request, in the API. If the approving user is the same person who tech-entered the most recent result, the route returns 403 and stops — before any write, not after a UI check. Four-eyes release is a property of the server, not of the screen.

api/results/route.ts:265-277 — 403 returned before any write

03 — Refusals

What we refuse to ship.

Every line below is something a competitor ships today, and something that would have been cheaper for us to ship too. Several of them are claims we have made ourselves, on our own product sites. This page is the standard. Where a product site does not meet it yet, the product site is what changes — not the standard.

  1. 01

    A number we cannot show you the source of

    Every figure on this site carries the file and line it was counted from. If we cannot cite it, we delete it rather than round it.

  2. 02

    A testimonial from someone who does not exist

    We publish no customer quotes, no logo wall and no star rating until there is a real customer who has agreed to be named. Placeholder people are not social proof; they are a lie with a headshot.

  3. 03

    A certification we have not been granted

    MedOS is ABDM-ready and sandbox-validated — it is not ABDM-certified, and we will not write that it is until the certificate exists. LabOS is built for NABL; NABL accredits laboratories, not software. We hold no ISO 27001 and have commissioned no external penetration test. Both facts are published.

  4. 04

    A guaranteed performance number

    No "+300% FPS", no "40% faster". BRUTAL will not print a performance figure it cannot measure on your machine, and it shows you the cases where it cannot help you at all.

  5. 05

    Software that holds your data hostage

    When a licence lapses, BRUTAL drops to free and leaves every optimization in place. When a MedOS subscription ends, your data stays exportable for 30 days. No kill switch, no ransom.

  6. 06

    A price you have to ask for

    Every price a self-serve customer pays is on the page — ₹699 for MedOS, ₹999 for LabOS, no setup fee, no qualification call. LabOS's top Enterprise tier is quoted rather than published; every tier beneath it is published, and we would rather say that here than pretend otherwise.

Six refusals. Between them they cost us a testimonial wall, a customer count, a certification badge, a performance percentage and a quote form. We think that is the whole of what we have to sell.

04 — House rules

The rules we hold ourselves to.

The refusals above say what we will not print. These say how we behave the rest of the time. They are boring on purpose. A standard that needs a slogan is not a standard.

Every illustrative figure is labelled as illustrative.
If a screenshot shows a sample number, the caption says it is a sample. A mock dashboard is captioned as a mock. This began as a BRUTAL house rule — "example readout, the app shows your machine's numbers" — and it now governs all three products.
Nothing is marketed as live until it is live.
Sandbox is not production. In progress is not certified. A feature on a roadmap does not get written in the present tense, and a certification we have applied for is not one we hold.
No countdown timers, no invented scarcity, no urgency.
No clock on a price, no seat counter, no notice that other people are looking at this page. If the offer is good on Tuesday, it is good on Thursday. Manufactured pressure is what you use when the product cannot carry the decision.
When a licence lapses, nothing is taken hostage.
BRUTAL drops back to free and every optimization already applied stays exactly where it is — nothing is reverted. When a MedOS subscription ends, the data stays exportable for 30 days. No kill switch, and no ransom for your own records.
We publish what we have not certified, next to what we have.
We hold no external security certification and have paid for no third-party audit. That sentence is not buried in an appendix; it is near the top of the trust page, above the things we do have. A vendor who only lists their strengths has told you nothing. Read what we have not certified

If we cannot show you where a number came from, we delete it.

That rule is the reason this site is shorter than our competitors' — and the reason you can check every line of it.

What we have not certified See the three products