·1 min de leitura
Mage: web and terminal, same progress
I unified /estudo and the edge-mage TUI into three courses — Fundamentals, Systems, Edge ML — with shared room credit.
I had two surfaces for studying systems and Edge ML: the web hub at /estudo and the TUI in edge-mage. Both worked, but the curriculum and progress didn’t speak the same language. I’d finish a room on one side and the other had no idea.
Mage is one product now, with two doors.
What it is now
Three courses, not N loose tracks:
| Course | Focus |
|---|---|
| Fundamentals | CTF labs, runes, craft — unlocks Mago base |
| Systems | Machine → IR → CS math (+ the ML/signals compilers need) |
| Edge ML | On-device inference; heavy labs in the terminal |
In the browser: edevs.com.br/estudo. In the terminal: clone edge-mage and follow #install.
Why unify
Progress is credited by room_id. If a room is shared between Systems and Edge, I don’t redo the same lesson on both sides. I pick the surface — web for reading and KaTeX, TUI for harness and flags — and the credit is the same.
That matters because systems and Edge cross: ABI, quantization, latency, memory. Splitting “compilers course” and “edge course” as if they were separate worlds made me duplicate foundations and miss the point.
Content direction
Labs point at primary docs and papers (LangRef, AAPCS, CMSIS-NN, quant papers), not SEO blogs. The path to Mago Supremo asks for craft artifacts — IR before/after, on-device evidence with latency/RAM — not XP alone.
Parity still has gaps (Edge web exports a sample and points to the TUI for code harness rooms; the Systems TUI catalog still syncs in pieces). The core I wanted is there: same curriculum, same credit, two UIs.
Next step
Open /estudo or install the TUI. Repo only: github.com/edevPedro/edge-mage.