Trust is a boundary, not a badge.
Atarla is early. The useful thing an early company can offer is not reassurance, it is a clear line between what has been observed, what the founder reports, what is designed, and what is merely intended.
The four categories.
- Observed: measured in a documented test, with the method and the failures published alongside the result.
- Founder-reported: stated by the founder and true as far as Atarla knows, but not independently verifiable by you.
- Designed: an architectural decision that has been made and written down, but not yet proven in use.
- Intended: a direction. It may change, and saying so is cheaper than quietly dropping it later.
What Atarla will not do.
- Name a customer without their permission.
- Publish a benchmark, saving, or outcome figure that has not been measured.
- Describe a planned capability in the present tense.
- Claim a certification, audit, grant, accelerator, or partnership that does not exist.
- Show an app store badge before a real listing exists.
- Present a concept render as production hardware.
How this is enforced.
High-risk facts live in a single claims registry in the repository rather than being retyped into each page. Every fact carries a status, the evidence behind it, when it was last verified, and whether it may be published at all.
The build then tests itself against that registry. A page that upgrades evidence, names an uncleared customer, or asserts availability that does not exist fails the test suite before it can ship.
What is not claimed.
This page describes a discipline, not an audit. No third party has reviewed Atarla's claims, and no certification or attestation exists.