Control CenterServicesStudiosRegistryArchitectureTargetsHealthIntelligenceCapabilitiesWorkflowsExecutionAsset InspectionProvidersCommercialCreditsSubscriptionsLicensingMeteringMarketplaceAdministrationFeature FlagsFuture Ready
OverviewProvidersModelsCapabilitiesRouterJobsUsageHealth
ATJ OS

Intelligence Center

Scaffolded

ATJ owns the workflow; external providers are replaceable execution suppliers. No provider is connected — adapters are scaffolded and reject execution with a typed error until a credential and a live integration exist.

6

Providers registered

17

Models registered

20

Capabilities

6

Safety policies

Execution chain
Studios never reach a provider directly. Every request passes through the kernel.
Mandatory
Studio→ATJ OS→Intelligence Layer→Provider Router→Provider Adapter→External Provider→Normalized Result→Asset / Project
Routing strategies
Deterministic comparators over the model registry. No autonomous router exists.
6 strategies

AUTO

Balanced default chosen by ATJ OS.

QUALITY

Highest quality class first, cost ignored.

BALANCED

Weighs quality against latency.

ECONOMY

Lowest ATJ internal cost first.

FASTEST

Lowest latency class first.

MANUAL

Operator names the exact model.

Safety gate
Every execution passes ATJ policy before and after the provider call.
6 policies
Minor Protection
Mandatory
both

Prohibits uploading or using identifiable images or video of minors in any workflow where ATJ policy disallows it. Cannot be disabled.

Identity & Likeness
Mandatory
pre

Requires consent evidence before a real person's likeness or voice is synthesised.

Commercial Licence Check
Configurable
pre

Blocks models whose licence prohibits commercial output when the project is commercial.

Sensitive Model Review
Configurable
pre

Routes work through review when the selected model is classified sensitive.

Provider Moderation Relay
Mandatory
post

Surfaces provider-side moderation verdicts as ATJ safety outcomes.

Output Provenance
Mandatory
post

Records which provider and model produced every artefact stored in the Asset Studio.

Environment separation
Each environment reads its own credential name. A development key never becomes a production credential.
3 environments

Development

Internal work. Only development credentials are ever read here.

suffix · _DEV

Staging

Pre-release verification with its own isolated credentials.

suffix · _STAGING

Production

Customer-facing execution. Activation requires deliberate approval.

suffix · (none)