Naming control plane
Govern every name your organization creates.
Bring requests, approved terminology, collision checks, evidence, lineage, and change history into one controlled naming workflow.
Hard gates, lineage rules, evidence requirements, and audit events remain enforceable.
Illustrative workflow
X 042Y 118
Illustrative records demonstrating the naming governance workflow.
The organizational problem
Naming breaks at organizational scale.
The failure is rarely a shortage of ideas. It is the absence of a controlled record connecting who requested a name, what evidence supported it, what conflicts were checked, and what decision became authoritative.
Requests begin in disconnected channels.
Context, ownership, and naming intent can separate before review begins.
Decisions lose their evidence.
Without a governed record, the rationale behind a name becomes difficult to recover or defend.
Renames overwrite institutional memory.
Teams see the latest label but not the lineage, exceptions, dependencies, or prior decisions behind it.
One governed source of naming truth
REQUEST → DECISION → REGISTRY
Control plane overview
Sample naming operations
Open requests12
Gate reviews05
Registry records84
RecordStateOwnerUpdated
Sample: Project AtlasReviewActor 0409:42
Sample: Feature NorthRegisteredActor 0708:15
Sample: Product MeridianCollisionActor 02Yesterday
Separate requests from authority.
A name can be proposed without becoming an approved organizational term.
Keep gates visible.
Decision requirements stay attached to the record rather than disappearing into informal approval.
Preserve the full record.
Registry and change history give teams a durable reference for what changed and why.
Governance workflow
Move from request to governed record.
Each request moves through evidence, collision review, decision controls, and registration while preserving the responsible actor and tenant context.
Capture the naming request
Establish a record, responsible actor, tenant context, and the evidence required for review.
Attach the supporting record
Keep the material used in the decision connected to the naming request.
Review collision state
Surface potential conflicts within the verified scope of the Collision Detector. Collision detection is not IP review and does not substitute for independent clearance.
Record the decision
Capture the outcome, responsible actor, and any remaining gate status.
Register the authoritative record
Preserve lineage and subsequent changes without erasing the prior naming history.
Term Vault
Control the vocabulary already in use.
Give teams a governed place to reference approved terms, statuses, and related records rather than relying on personal documents or memory.
Keep term status visible at the point of use.
Connect terminology to the request and registry context that produced it.
Store definitions, architectonic anchors, pronunciation, syllable count, caution ratings, and lifecycle status.
Illustrative interface
Term Vault
Sample term: AtlasTERM-0081 · Product family
ApprovedSample term: MeridianTERM-0082 · Internal project
RestrictedSample term: NorthTERM-0083 · Feature label
In reviewRegistry and change log
Preserve authority without erasing history.
A current name is only part of the record. Registry and change history preserve the chain of decisions that made it current.
Keep authoritative records distinct from proposals.
Track changes as events rather than silent replacements.
Retain lineage across related naming objects.
Illustrative interface
Registry lineage
Record createdREG-0312 · 2026-07-08 10:24
Decision evidence attachedEVD-0091 · 2026-07-09 14:08
Status changedCHG-0044 · 2026-07-10 09:37
Related record linkedLIN-0021 · 2026-07-10 11:16
Collision Detector
Surface conflicts before a decision hardens.
Use the Collision Detector only within its verified technical scope. It does not perform IP review, regulatory checks, domain verification, or guarantee uniqueness.
Show the collision state beside the request.
Keep unresolved conflicts visible through the workflow.
Publish precise limitations before launch.
Illustrative interface
Collision review
CandidateSample: Atlas
ScopeSample registry
StateReview required
IP or regulatory checkNot in scope
Naming Brain
Candidate generation is part of the naming workflow.
Naming Brain generates and scores candidate terms from the product designation, buyer, dominant function, target markets, assigned semantic bucket, and selected term types. Generation is not available while Engine v2 is offline.
Generate real nouns, coined words, and alphanumeric candidates.
Review definitions, pronunciation, quality scores, and caution ratings.
Move selected candidates directly into the Term Vault for governed review.
Candidate generation
Naming Brain
InputsDesignation, buyer, function, markets
Term typesReal noun, coined, alphanumeric
OutputsRanked candidates with quality data
Next stepAdd selected terms to the Vault
Portfolio lineage
See how related names inherit context.
Connect naming records across a portfolio so teams can understand relationships, dependencies, and change history without flattening every name into an isolated entry.
Portfolio rootSample: Atlas System
ProductAtlas Core
FeatureAtlas Signal
ProjectAtlas North
Prior recordProject Meridian
Change eventRenamed 2026
Governance architecture
Authority belongs to the system, not the loudest stakeholder.
Authenticated tenant context scopes every tenant-owned query, while server-side permissions revalidate governance commands and role access.
Integrity
Hard gates, lineage rules, evidence requirements, and audit events cannot be waived by deadlines, preferences, roles, or subscriptions.
TenantsOrganizational context is selected at the control plane level.
ActorsActions are associated with a selected actor context.
RolesServer-side permissions control access to tenant actions and governance operations.
IntegrityHard governance rules remain superior to convenience or urgency.
Audit eventsRequired events remain part of the governed record.
ConfigurationAdministrative controls manage governance settings, actors, roles, markets, and naming rules.
Illustrative use cases
Where governed naming creates operational value.
Use the governed record wherever product portfolios, cross-functional approvals, or controlled terminology need durable ownership and history.
Product portfolio governance
Coordinate names across products, features, and related portfolio records while retaining lineage.
Cross-functional naming decisions
Keep requests, evidence, collision states, decisions, and responsible actors in one review record.
Terminology and change control
Maintain an authoritative reference for approved terms and the events that changed them.
TenantSample organization
Active requestProject Atlas · Gate review
Evidence3 sample records attached
CollisionReview required
ActorSample owner
LineageREQ-0248 → DEC-0074 → REG-0312
Product tour
Follow the complete naming record.
Move from a tenant-scoped request through evidence and collision review to an actor-owned decision, registry entry, and retained lineage record.
The interface illustration uses sample records; the workflow and product areas reflect the deployed platform.
Security and data handling
Identity, tenancy, and audit controls stay server-enforced.
Brand supports standalone email or Google authentication and authenticated NxtGen Space handoff, with tenant-scoped data access and signed audit records.
AuthenticationEmail/password, Google authentication, and NxtGen Space SSO handoff are supported.Active
Tenant scopeAuthenticated tenant identity constrains tenant-owned server queries.Enforced
Role permissionsGovernance commands are revalidated against server-side permissions.Enforced
Session handoffNxtGen Space uses a single-use, five-minute product entitlement token.Signed
Change historyAppend-only Change Log events are protected with HMAC integrity checks.Signed
Backup restoreFull tenant exports include a checksum and server signature for verified restoration.Verified
Frequently asked questions
Clear boundaries build trust.
What is NxtGen Brand?
It is a naming control plane with Dashboard, Term Vault, Naming Requests, Portfolio, Registry, Change Log, Collision Detector, Naming Brain, Integrity, tenant controls, actor controls, and Admin & Configuration.
Does Collision Detector perform IP or regulatory checks?
No. Collision detection operates within its verified technical scope. It does not perform IP review, regulatory checks, or domain verification.
Is Naming Brain generation currently available?
Naming Brain generates and scores real-noun, coined, and alphanumeric candidates from a structured brief and lets users add selected terms to the Term Vault. Generation is not available while Engine v2 is offline.
Can an approver bypass a hard gate?
The stated governance principle says deadlines, preferences, roles, and subscriptions cannot waive hard gates, lineage rules, evidence requirements, or audit events.
How are tenants, actors, and permissions handled?
Users work within an authenticated tenant. Server-side permissions control governance operations, and actions retain the selected actor and tenant context.
Can I use Brand directly or through NxtGen Space?
Both. Brand supports standalone sign-in and account creation, Google authentication, and authenticated launch from an entitled NxtGen Space workspace.
Plans
Three tiers, one-time purchase.
Choose the scope that matches your project. Pricing and features are served from the server registry.
Loading plans…
Build institutional naming memory
Put every naming decision on the record.
Create a workspace to start governing requests, candidate terms, decisions, registry records, and naming history in one system.