For the complete documentation index, see llms.txt. This page is also available as Markdown.

6. Platform Integrity

6.1 The measured result

Snapshot: 19 October 2026, 09:01 UTC.

Accounts
Share

Registered

1,257,124

100%

Classified as automated

1,011,789

80.5%

Not classified as automated

245,335

19.5%

"Not classified as automated" means an account has not tripped the classifier. It does not mean the account has been verified as a unique person. Classification is recomputed daily, so an account's status can change in either direction. The team's internal estimate is that between 1.3% and 5.4% of accounts classified as automated may be operated by people rather than automation.

6.2 How accounts are classified

Each account receives a risk score, recomputed once a day, from six signal families. No single signal flags an account.

Family
What it detects

Network fan-out

Many accounts operating behind one network fingerprint

Balance clustering

Improbably many accounts holding the same reward balance

Registration timing

First reward arriving implausibly soon after sign-up

No health activity

Reward activity with no health journal entries

Content templating

Meal descriptions that cluster into a small set of generated phrases

Chat loop pattern

Repetitive automated chat behaviour

Thresholds and weights are withheld from public materials and are available to counsel and audit counterparties on request. The classification script is maintained outside the application repository.

6.3 Controls on issuance and use

Control
Effect

Write restriction (since 4 September 2026)

Accounts classified as automated cannot record activity or earn HP. A person wrongly classified can lift the restriction for 1 day by completing a Cloudflare Turnstile check (7 days until 22 September 2026). Accounts that paid the sign-up fee are not restricted. The restriction does not change classification.

Cadence gate

Rejects survey answers arriving at machine-regular intervals

Referral controls

Daily settlement cap and cohort suspension (Section 5.6)

AI cost containment

Accounts classified as automated do not reach the language model, except through meal-log edits (Section 6.4)

Rejection messages

A request rejected by the write restriction returns bot_limited with a link to the verification page. Only rate-limit rejections do not state which rule was tripped.

6.4 Known limitations

  • Passes. Turnstile checks can be solved at scale. As of 14 September 2026, under the earlier 7-day rule, 88,354 accounts held an active pass, of which 92.1% were classified as automated, and in one sampled hour 39.2% of HP issued went to pass-holding accounts classified as automated. Since 22 September 2026 a pass lasts 1 day. [TBD: whether passes should allow HP issuance.]

  • Referral concentration. Individual accounts not classified as automated hold large balances derived almost entirely from referrals (for example, one account held 1,652,040 HP on 7 September 2026, 97.5% from referrals). Whether such balances are adjusted is [TBD].

  • Fee-paid accounts. Accounts that paid the sign-up fee are not restricted even if classified as automated.

  • Referral settlement suspends an inviter only on the share of invited accounts classified as automated; it does not check the inviter's own classification.

  • Meal-log edits are not subject to the write restriction, and an edit can call the language model to re-estimate nutrition.

  • Service reliability. The Platform experiences recurring periods of server errors under load, including on survey-answer and goal-commitment endpoints. Some actions during those periods may not be recorded as the member intended.

  • HP balances alone are therefore not a reliable measure of participation by accounts not classified as automated.

Last updated

Was this helpful?