Appendix D Repository and Module Map

The CNA tag also records sharp-runtime 625476d5b5fff5fa89f392c3c9af8638ff237692 as the revision used for release verification. That is release evidence, not a dependency lock: CNA’s CMake consumes a caller- supplied SHARP_RUNTIME_ROOT and does not enforce the recorded SHA. The older f827a6c5 pin in the table is retained as this book’s bounded sharp-runtime technical audit source; alpha.1 claims that depend on sharp-runtime were checked against the release record separately.

The dependency arrows are not all equivalent:

cna ---> sharp-runtime
 |----> easy-gl ---> meta-gl          (selected GL family)
 ‘----> free-direct ---> free-api     (selected FREEDIRECT family)

xna4-spec, cna-samples, cna-examples          evidence/catalog peers
cna-template, cna-craft, cna-extended         downstream consumers

Renderer-specific third parties fetched or discovered by CNA are not promoted to sibling repositories in this diagram. They remain dependencies of their owning renderer module, with their platform and acquisition gates recorded in Part IV.

The root modules/CMakeLists.txt composes fifteen framework/extension modules when Net is enabled, plus the renderer tree; the experimental C adapter is a separate optional module. Directory location is source ownership: production code belongs under the owner’s src/, public and public-internal contracts under its include/, and its tests/examples alongside them. A configure-time validator rejects translation units outside a declared module tree.

The interface target CNA composes the framework modules, extension umbrellas, shared build flags, sharp-runtime closure, and the selected renderer target set. In a singular build the set has one family; CNA_GRAPHICS_RENDERERS can compose several compatible families and a configured default. Individual module aliases support narrower link-closure probes. CNA::CnaExt composes graphics-ext and devices-ext; it is distinct from the empty CNAEXT declaration marker and from the CNA_CNAEXT build option that enables selected extension products.

modules/renderers/ contains one common-contract area plus 46 implementation families. Only EasyGL maps multiple public identities to one family.

The physical tree alone does not establish a public selector, platform admissibility, resource factory, or semantic parity. Appendix B joins directory families to all 50 public identities and their narrow implementation behavior.

For a later edition, pin every repository before counting it; derive module and renderer sets from CMake/source rather than an organization README; distinguish direct dependency, transitive dependency, evidence peer and downstream consumer; and record the command/query behind every count. A local worktree of cna is not a sibling project, and an organization repository with no dependency or evidence edge is outside this bounded map.