What are the three pillars of the New Architecture?

WHAT THIS TESTS: A correct high-level map of the new architecture's components and how they relate, without conflating them.

A GOOD ANSWER COVERS: The new architecture rests on three pillars. JSI, the JavaScript Interface, is the foundation: a lightweight C++ layer that lets JavaScript hold references to native objects and call them directly and synchronously without JSON serialization, replacing the legacy bridge. Fabric is the new renderer, responsible for building and committing the UI; it constructs the shadow tree in C++, enables concurrent React features, and allows synchronous layout reads. TurboModules are the new model for native modules: they are accessed through JSI and load lazily on first use, improving startup time. A strong answer also mentions CodeGen, the tooling that generates type-safe interfaces between JS specs and native code, gluing the pillars together.

COMMON WRONG ANSWERS: Swapping the roles of Fabric and TurboModules; Fabric is rendering, TurboModules are native modules. Listing the bridge as a pillar. Calling JSI an optimized bridge instead of its replacement. Omitting JSI entirely as the underlying layer.

LIKELY FOLLOW-UPS: What CodeGen produces, how to enable the new architecture, how Fabric supports concurrent rendering, and what changes for library authors migrating native modules.

ONE CONCRETE EXAMPLE: An app enabling the new architecture sees its custom view rendered by Fabric, its battery and storage native modules become lazily loaded TurboModules called through JSI, and CodeGen produces the C++ and JS type-safe glue so a mismatched prop type fails at build time rather than crashing at runtime.