AnonymousSign in
Every rule below is a promise about what money cannot do here, paired with the mechanism that enforces it and the current result of the automated check that proves it. If a check fails, this page says so.
Status: Enforced
Every rule below is currently enforced by a passing automated check.
Checks last run .
The modules that read and order buyer-facing content are forbidden from importing the billing and API-subscription modules at all. This is checked as a one-way dependency at the import-graph level, so a violation fails the build rather than surviving review.
content-access modules do not import billing (firewall) — passingbilling modules never implement a placement/ranking concept (code, not comments) — passingpublic content-reader modules do not import apiAuth or billing (firewall) — passingFiles: src/lib/billing/billing.firewall.test.tssrc/lib/apiAuth/apiAuth.firewall.test.ts
Ordering is name-only by construction. The single exception is a 'Sort by: Transparency score' control a buyer must actively choose, which is off by default and is deliberately absent from the public API — a machine consumer has no concept of opting in. No paid concept (sponsored, featured, promoted, boosted) exists anywhere in the content path.
no content module implements a paid-placement concept — passingthe public API exposes no caller-controlled ordering — passingFiles: src/lib/publicApi/server.tssrc/lib/trust/neutrality.firewall.test.ts
The score is a weighted composite of verification state, security posture, buyer feedback and profile completeness. The weights are published below, read live from the same configuration the running computation uses, so the documented methodology cannot drift from the real one.
This rule is not proved by a test. It is proved by publishing the live value below, read from the same configuration the running system uses.
Read from the same configuration the running computation uses, so the documented methodology cannot drift from the real one (never changed from defaults).
Files: src/lib/trust/transparencyScore.ts
Disclosure is a per-vendor, buyer-initiated record with its own revocation state — not a profile setting and not a default. No aggregate buyer dataset is built, exported or offered, and no buyer-derived data appears in the public API.
the public API exposes no buyer-derived data — passing1 buyer-initiated disclosure to a named vendor, ever. There is no aggregate buyer dataset behind this number — it is a count of individual, revocable actions buyers chose to take.
Files: prisma/schema.prismasrc/lib/publicApi/server.ts
A claim to neutrality that only appears in marketing copy is worth nothing, because the platforms this one exists as an alternative to make the same claim. The difference we can actually offer is that ours is checkable: the rules above are enforced by tests in the codebase, and the results are published here with a timestamp, including when they fail.
The machine-readable version of this page is at https://0-doubt.example.com/api/neutrality. See also how 0-Doubt labels trust.