Crypto Intelligence, Decoded.

The missing half of profit. Rows are immutable — a mistake is VOIDED with a reason, never edited — and totals are always derived. Profit stays unpublished until at least one cost is written down: revenue minus costs nobody recorded is revenue wearing a different label.

Rewards frozen by the fraud rules. Each row carries the sentence that froze it — verifiable against the tables it names. Approving pays the referrer; the customer's subscription was never touched either way.

Applicants already passed the fact gate (3 converted referrals, re-checked at filing). You are judging the person and their statement; approving pays a one-time 250-point bonus and puts the badge on every leaderboard.

Search by account, referrer, code or signup IP. Opening a referral shows its timeline and the risk arithmetic that explains a hold — including the rules that could not run. Granting or revoking a reward rides the same idempotent ledger ref the automatic path uses, so no combination of doors can pay twice; attaching an attribution records only and pays nothing.

Funnel, treasury runway, quest verification and where the points went — all derived, nothing stored. A rate with no denominator shows “—”, never 0%.

Two kinds land here and the row says which: tasks no machine can settle (a video is not verified by a page returning 200), and tasks whose network could not be reached — an outage must never reject somebody who did the work. Approving pays through the same idempotent ref the automatic path uses.

The score is the SUM of the weights of the rules that fired — every term is listed, because a reviewer cannot check arithmetic they cannot see. There is no learned model and no hidden term. The strongest thing these rules do on their own is freeze a reward for a human; they never ban, suspend, or touch the referred customer's subscription.

Bars a device, wallet, payment identity or address from EARNING — it raises the risk to critical so the reward freezes for review. It does not block access; suspending an account is a different control. Expiry is honoured when the list is read, so a lapsed block stops blocking the moment it lapses.

Where visitors come from, what they use, who pays from where, who arrives through a hosting network, and which countries the platform refuses service to. Every figure carries its basis; a missing geo database says so rather than showing an empty chart.

Everything here is measured, never assumed. A figure that cannot be taken says so and gives the reason instead of showing a zero.

Twelve of these run the platform — renewals, snapshots, indexing. A crash used to leave no trace anywhere a person would look.

Every scheduled run restores the dump into a scratch database and compares row counts. A dump nobody has restored is a hope, not a backup.

Every permission, and which role carries it. The point of the split is that support staff and treasury custody are not the same job — read the grid rather than guessing from job titles.

You cannot approve a withdrawal you raised yourself — that is the whole point of the second signature. Rejecting needs less privilege than approving, so raising the alarm is never the harder path.

Every privileged action, and every sensitive lookup. Reads are recorded too — opening a user's balance and full ledger is not nothing.

Who signed in, from where, and who failed. Before this table a password-spray across a hundred accounts left the same trace as a quiet Tuesday: none. Leave the box empty — a campaign is only visible as a campaign in the platform-wide stream.

Bars an address from signing in and registering. The per-account lockout cannot stop a spray — four failures against each of a hundred accounts never trips a five-failure threshold on any one of them.

Measured now, and the two that decide a host move are measured from OUTSIDE: the A record and its TTL through a public resolver (what the world sees, not this host's cache), and the certificate through a real handshake against the domain. Nothing here holds a registrar key or a server password — the console tells you what to type, it cannot take the platform off the internet by itself.

Four steps, in the order that keeps the site up: snapshot here, build the new host beside it, verify it by IP, flip DNS last. The old host stays paid for a couple of days — that is the rollback.

Search-readiness, measured from this deployment — the HTML on disk, the live route table, the middleware stack. The score is ours (weighted pass-rate over the checks below), not a Google metric: Google's own numbers need Search Console on a live domain, and a dashboard that invented them would be lying with precision.