What identity information does DXT Creator define?

Creator defines the governed structures, formats, symbologies, job templates, versions, and approved data relationships that determine how each production identity is generated and used.

How does Creator manage versioned job templates?

Job templates are maintained with version history and approval records. Every change is attributable and reviewable, and each production run is executed against a defined, released version.

Which formats and symbologies can Creator support?

Creator supports the identity formats and symbologies configured for each deployment. Supported formats depend on the specific implementation; universal format or standards support is not implied.

Can Creator ingest identities from external sources?

Yes. Approved identities from external sources can be ingested and normalized into governed definitions without transferring custody, line-execution, or verification authority to Creator.

What proof records does Creator create?

Creator emits identity definition records, template version history, symbology and format rules, approval records, external ingestion records, and launch-readiness status.

DXT CreatorLevel 3 · Facility Control

CREATOR

Define identity before production begins

DXT Creator governs identity structures, symbology rules, formats, job templates, versions, and approved production intent before work reaches the line.

Define Identity Before Production Request a Demo

What Creator Proves

Versioned identity definitions
Governed symbology and format rules
Approved job templates

Creator / Identity Definition

Identity Origin

Secure origins for every production identity

Creator defines the governed structures, formats, rules, templates, and versions that determine how identity will be generated and used. Approved production intent remains attributable and reviewable before identities are allocated or executed.

Definition Control

Govern identity structures, formats, symbologies, job rules, and approved data relationships.

Version and Approval History

Preserve changes, approvals, and launch-ready definitions across programs and production environments.

Capabilities

Identity definition and rules origin

Capabilities vary by deployment — not every configuration includes every module.

Identity Structure

Governed identity structures and approved data relationships that define what each production identity represents before it is issued or applied.

Define identity once. Govern it everywhere.

See how DXT Creator establishes versioned production intent before the first unit runs.

Define Identity Before Production

Proof Artifacts · DXT CreatorLevel 3 · Facility Control

What Creator proves — and where it sits in the stack

Creator is the Level 3 origin of identity intent. It defines the structures, symbologies, rules, and approvals that flow downward into allocation, plant command, and line execution — emitting the audit-grade records below as proof.

Creator defines identity and production intent · Allocator governs custody and distribution · SiteCentral coordinates plant and job context · Tracker records line execution · Insight and Verify consume trusted downstream evidence.

Control stack

L4 · Enterprise Intelligence

DXT Insight · Verify

Observability + verification

definitions

L3 · Facility Control

DXT Creator

Identity definition + rules

Active

approvalsrelease

L3 · Facility Control

Allocator · SiteCentral

Custody + plant command

job context

L2 · Production Line Control

DXT Tracker

Execution + proof

Records emitted by Creator

Identity definition recordsCanonical structures for each product and program, ready for governed downstream use.Record
Template version historyEvery job-template change tracked with who, when, and why for full traceability.Record
Symbology and format rulesFormat, symbology, and validation logic enforced against every definition.Record
Approval recordsSign-off records that gate release of definitions into production.Record
External ingestion recordsExternally sourced identities ingested and normalized under governed workflows.Record
Launch-readiness statusRelease evidence confirming a definition is ready for allocation and execution.Record

View control architecture Define Identity Before Production

Integrated Ecosystem

Creator in the Delta-X Trust ecosystem

Rules become portable production intent, version control protects consistency, and external identities enter governed workflows.

Rules become portable production intent

Creator converts approved identity, format, and job requirements into versioned definitions that can be used consistently across authorized production environments.

DXT Allocator DXT SiteCentral

Version control protects consistency

Every approved change remains attributable, reviewable, and connected to the production definition it replaced.

Control Levels

External identities enter governed workflows

Approved identities from external sources can be ingested and normalized without transferring custody, line-execution, or verification authority to Creator.

DXT Tracker DXT Verify

Common questions about identity definition and rules origin with DXT Creator.