Project and library catalog
The live Nx graph is the canonical catalog. Project names often include their layer and capability and do not always match the final directory segment.
Discover exact projects
Section titled “Discover exact projects”pnpm nx show projectspnpm nx show project trinity --jsonpnpm nx graph --printThe documentation source validator reads every project.json, compares it with Nx discovery, and sorts names, roots, tags, and targets for deterministic checking.
Project families
Section titled “Project families”| Family | Examples | Responsibility |
|---|---|---|
| Applications | trinity, trinity-desktop, trinity-android, trinity-ios | Composition and platform delivery |
| Application | application-runtime, application-workspace, application-appearance | Cross-capability coordination |
| Data access | data-access-accounts, data-access-matrix-client, data-access-room-library, data-access-timeline, data-access-trust | Capability state and commands |
| Features | feature-auth, feature-crypto, feature-rooms, feature-settings | Product workflows and pages |
| Components | components-controls, components-foundations, components-navigation-layout, components-overlay | Public reusable UI |
| Runtime and utility | runtime-host, runtime-preferences, runtime-projection, util-matrix, util-ui, native-capacitor-push | Shared kernels and adapters |
| E2E | trinity-e2e-browser, trinity-e2e-components, trinity-e2e-protocol, host suites | User, protocol, and host journeys |
| Documentation | docs-users, docs-developers, docs-site | Public sites and their validation |
Use project tags to determine role, capability, type, and scope. Read dependency boundaries before adding an edge.