miners: build, host and follow a full system through the round, and promote certified systems with the champion marked

[BANADDA]

The miner guide only described training a model. This makes it, and the tooling behind it, cover the whole system a miner builds and hosts.

docs/system_miner.md

• New opening: full system arenas against classic arenas.
• Section 1 corrected to the live arenas (invoice on mt-4g and text2sql on mt-16g at 50% each, ceilings per task) and the real eight position payout ladder. It replaces a stale code-track table and a 180 ms TTFT figure.
• Section 12 is now Building a full system:
  • the four parts, the artifact layout, and a system.json v2 example with how to compute its digests;
  • the harness package format and its rules, and the router format with every permitted feature;
  • train_router.py, and choosing and running an allowlisted escalation model;
  • simulate, ship, and mt miner host through the round;
  • what validators check, how systems are ranked, and what happens after the round;
  • the classic cascade, and the common misreadings.

mt miner host --escalation-url URL [--gpu-layers] keeps the packaged full system online through the dial out agent under the miner's hotkey, answering validators' live tasks with signed traces, until the round settles.

mt archive promote --round N --records DIR publishes every certified full system of a settled round from the private archive to the public one:

• files, certificate.json, and a card naming the four parts, the rank and the licence;
• rank 1 is tagged champion, the system the arena serves as its model;
• a record that doesn't match its certificate is skipped. Systems that weren't certified stay private.

Checked: a dry run promoted a certified system and wrote a champion card listing all four parts.

🤖 Generated with Claude Code