KAT — the cargo-heal network

The fix-rule corpora the healer draws on, and how they grow by day. One square per day, two channels: hue = which corpus grew most that day, shade = the day's volume in four buckets — quartiles of the year's active days, so one bulk import cannot flatten every other day. Hover a square for the per-domain breakdown; the first recorded day is the baseline, and an empty square is a day with no recorded change. Snapshot as of 2026-09-09.

The ledger's own daily snapshot, recorded on its maintenance schedule. One square per day — shade = the KAT burned that day (heal demand), bucketed by quartile against the year's other active days; rings mark the mining pipeline (yellow) and minted payouts (blue) — green when a day did both; hover a square for the day's totals. Click a chip to hide a layer.

Who runs the healer, and what the miners contribute. Free = claimed the grant, never contributed (cargo heal); mining = pushed a redacted batch (cargo heal --mine). The tiers are the machines' own signed declarations (--mine / --unmine); an opted-out machine stops contributing but its last declaration stays on record.

--mine logs you in automatically — zero config, local key ops only. Logging in creates (or claims) your account and its free 100,000,000 KAT grant. The explicit command is the repair path: re-run cargo heal login to repair, or import an existing key on a new machine with cargo heal login --import-key.

No — the healer ships as checksum-verified prebuilt binaries only, landing in ~/.cargo/bin. It runs as cargo heal inside any Rust crate: a Rust toolchain is needed to use it, not to install it.

Every heal run records HOW the healer behaved — which rules fired, which were declined, what merged. Those redacted verdicts (never your source, never your paths) are the corpus the network learns from. Miners who contribute them are paid from 70% of every KAT the network burns, at each epoch settle. The healing already runs on your machine — mining turns that work into network credit.

cargo heal — the dry run, private, no account: reviews the current directory (or the paths you name), prints what it would fix, writes and sends nothing. --fix writes — still local, still nothing uploaded.

cargo heal --mine — contribute & earn: opts in, logs you in, syncs. Only sync uploads, and only a redacted batch — rule verdicts and counters, never your source, never your paths — signed with your account key. Miners are paid from 70% of every KAT the network burns, at each epoch settle. Your burn reports automatically after each run — account accounting, not a consent gate — and offline runs stack locally and report with the next run.

Run neither flag and nothing has been uploaded yet — but the unset state is not a refusal: running sync is itself the consent. cargo heal account shows your balance, burn and grant at any tier.

cargo heal --unmine — opt out, stay local: sync stops pushing — no batch built, none signed, none sent. The lease pull half still runs (a read is not a contribution). Healing is untouched; trajectories keep recording locally. Anything queued under .heal/outbox is yours to delete — --unmine neither submits nor deletes your files; --mine turns it back on.