SYSTEMS / OPEN CHANNEL
ARCHITECTUREIS FAIR GAME.
Local inference, compact compute, networking, orchestration, deployment, cooling, or the awkward boundary between software and hardware. Bring the whole system.
The architecture matters most where the layers collide.
GregRietta AI is not being treated as one isolated model. The surrounding compute, runtime, networking, storage, orchestration, and physical infrastructure all shape what the AI can eventually become.
That makes ugly real-world constraints useful. Latency, heat, cables, resource limits, reliability, serviceability, and operational complexity are not side notes. They are part of the design.
WHAT TO BRING / 02
Enough detail to make it interesting.
Show the shape of the system.
Nodes, networks, runtimes, services, accelerators, and where workloads are supposed to move. A rough diagram is completely fine.
Name what is fighting back.
Thermals, bandwidth, latency, memory, cost, power, deployment friction, or any other limit that is forcing a design decision.
Bring the decision that has no clean answer.
Local versus cloud, one node versus many, simple versus flexible, or fast now versus scalable later. Those are the useful conversations.
DIRECT LINE / 03