Insights
Technical writing on the physical constraints shaping AI infrastructure. Each published piece will state its evidence, name its sources and identify what remains unresolved.
Editorial standard
Three rules govern everything published here, and they are published so readers can hold CoralDC to them.
Every quantitative claim is traceable to its source and, where a primary source exists, linked to it. Every piece states what it does not know. No piece is published that CoralDC would not defend in front of an engineer from a competitor.
Twelve planned pieces, released after editorial and evidence review.
The programme is listed for transparency. Each article remains forthcoming until its evidence review is complete.
| # | Title | Type | Author |
|---|---|---|---|
| 1 |  | Technical analysis | Vikas Chauhan |
| 2 |  | Pillar | Aditya Kaul |
| 3 |  | Analysis | Venkatesh Prabhu |
| 4 |  | Technical | Vikas Chauhan |
| 5 |  | Pillar | Venkatesh Prabhu |
| 6 |  | Analysis | Aditya Kaul |
| 7 |  | Methodology | Vikas Chauhan |
| 8 |  | Reference architecture | Vikas Chauhan |
| 9 |  | Technical | Vikas Chauhan |
| 10 |  | Research | Venkatesh Prabhu |
| 11 |  | Research | Venkatesh Prabhu |
| 12 |  | Radar update | Vikas Chauhan |
Whitepapers and the Knowledge Hub
CoralDC's long-form technical writing is published here as dated, maintained pieces rather than as gated downloads. The Resources and Knowledge Hub sections remain the home for reference material, case studies and the lexicon.
Request an Architecture Review
Every piece in this section describes a constraint that shows up in a real building. An architecture review applies them to yours.