Skip to content

Names and ownership

Definition names describe their meaning. Target filters select variants. For example, a build can compose BuildSolarEngine with distinct Windows and Linux implementations selected by TargetOS, without encoding the platform into the operation's name.

Paths and identities

Project Id values are opaque identities; directory names do not infer dependencies. Catalog entries explicitly locate descriptors.

Declared build paths use forward slashes on every host. Native OS paths are normalized at their boundary. Arbitrary tool arguments and rendered contents retain their own syntax.

Executable filenames belong to the recipe or invoked compiler/tool. Nexus Forge and Nexus Build do not append .exe to commands.

Source layout

  • projects/: executable tools and their dialects, recipes, and tests.
  • packages/: independently owned shared libraries.
  • docs/: public documentation.
  • Sibling nexus-fpc, nexus-mobile, and nexus-lab: compiler, engine, and examples.
  • External worktree: generated source-build outputs.

Common Pascal unit prefixes include ob for object implementations, tp for shared types, ut for utilities, and ts for test suites. The repository's applicable source standards govern contributions; names alone do not establish architectural ownership.

See System boundaries for the current ownership map.