Helium and Trombetta.SaaS naming
Last updated:
Helium and Trombetta.SaaS refer to the same framework at different naming layers.
Canonical terms
| Term | Use |
|---|---|
| Helium | Project code name and documentation product name. |
Trombetta.SaaS |
Stable technical root for package IDs, assemblies, namespaces, and public identifiers. |
| Consuming application | The consumer-owned SaaS application that references Helium artifacts. |
| Reference application | The official application shape generated by the future project template. |
Technical identifiers
Public technical identifiers must use Trombetta.SaaS, not Helium.
Examples include:
Trombetta.SaaS;Trombetta.SaaS.Contracts;Trombetta.SaaS.Testing;Trombetta.SaaS.Templates;Trombetta.SaaS.Hosting.AspNetCore;Trombetta.SaaS.Persistence.PostgreSql.
Namespaces may include capability segments such as Trombetta.SaaS.Identity or Trombetta.SaaS.Organizations. The existence of a namespace does not imply a corresponding public package or supported extension contract.
Documentation usage
Use Helium when discussing the product, architecture, capability model, or documentation site. Use exact Trombetta.SaaS identifiers when referring to packages, assemblies, namespaces, types, configuration symbols, or commands.
Do not invent identifiers such as:
Helium.Core
Helium.Runtime
Helium.Templates
Compatibility
The Trombetta.SaaS technical root is compatibility-sensitive after publication. Renaming it would require an explicit architectural decision and a consumer migration strategy.
The commercial product name may change independently. Such a change does not automatically rename technical artifacts.