One dashboard for everyone is fragmentation pretending to be unity. Six templates for six functions is specialisation pretending to be nothing. The Red Team already has individual + team dashboards. The Digital Army needed templates — share-able, replicable, role-shaped. This document tells you which template fits which operator, and where the tier-locks sit.
| Tier | Template | Colour | Function | Lives at |
|---|---|---|---|---|
| R | Node Operator | Red | Holds territory · recruits sub-nodes · runs the postcode | Card 1 |
| V | Verifier | Green | 18→8→6 checkpoint · batch evidence · trust signal | Card 2 |
| G | Gateway Operator | Gold | Owns a gateway · logs deposits · volume + bonus | Card 3 |
| A | AML Partner | Blue | Non-plastic materials · ESG reports · per-tonne fee | Card 4 |
| B | Builder | Grey/White/Gold | Builds pages · ships tools · keeps the system shipping | Card 5 |
| S | Sourcer (NEW) | Purple | Works the Carrot Hit-List · brings tonnes through the door | Card 6 |
Use this column to keep your assignment pencil straight. Names are illustrative — replace with whoever you've onboarded this week. Do not publish this column. It's yours.
| Pattern | Template | Why this template |
|---|---|---|
| Has postcode + people under them | R · Node Operator | Territory + override pay = node behaviour |
| Stands at the checkpoint with a phone | V · Verifier | Owns evidence trail · per-batch pay |
| Owns a bin / unit / collection point | G · Gateway | Volume-based · sensor-watching |
| Has expertise in compost · soil · textile · food | A · AML | Material is not plastic — different ledger |
| Ships pages, scripts, integrations | B · Builder | Per-task pay · shipping is the metric |
| Phones suppliers · works the hit-list | S · Sourcer | Carrot is their daily board · MD-256 their manual |
Digital Armour and Digital Army are the same people, the same documents, the same system. The trilogy holds:
This document (MD-257) is the navigation layer on top of that trilogy: how to issue a dashboard to a registered operator without rewriting the doctrine.
An operator graduates by hitting a measurable. The path is fixed but the timing is theirs.
Promotion is automatic when triggers are met. The operator does not ask. The system flags them. The Architect confirms or holds. No politicking, no requests, no inboxes. The ledger does the noticing.
| From | Trigger | To |
|---|---|---|
| Verifier | 10 batches sealed clean | Gateway or Sourcer (their choice) |
| Gateway | 1,000 deposits/wk for 4 wks | Node Operator |
| Sourcer | 3 suppliers gone Official | Node Operator (their territory) |
| Node Operator | 2 sub-nodes hit Verifier-clean | Red Team candidacy (Architect's call) |
| Builder | 5 shipped pages on the public dashboard | Toolora bench / Dev cell |
| AML Partner | 50 tonnes verified across ≥2 streams | AML Cell lead (Material Ledger custodian) |
Six templates. One ledger. Everyone earns by doing. No one sees what they haven't earned. The Architect assigns. The Agent ships. The Covenant fires first. 👑