Users should see the route cost before connecting. Suppliers should see how payout is calculated before selling capacity.

Ops must publish launch prices before advertising

A simple policy for failed capacity, duplicate payments, expired instructions, and fraud exclusions.

Manual review until live treasury automation is drilled

Torna should collect the minimum data needed to authenticate users, operate sessions, settle money, prevent abuse, and debug reliability.

Needs final legal review before launch

The service is for lawful access, verified supply, and local payment. Abuse can suspend accounts, routes, withdrawals, and servers.

Needs final jurisdiction review

Security reports need a clear inbox, a safe disclosure path, and honest status about keys and launch readiness.

PGP publication pending before launch

Users need to know whether login, top-up, route generation, suppliers, probes, and settlement are healthy.

Live checks and incident template available; staffed owner pending

Torna needs to protect users, suppliers, cardholders, and the network from activity that can get capacity blocked or people harmed.

Needs live moderation drill

A go-to-market product needs explicit limits for jurisdictions, sanctioned entities, payments, and operator responsibilities.

Legal review required before paid advertising

Support must be easy for Persian users when money, login, route access, supplier abuse, or security risk is involved.

Needs staffed launch rota