SALARAHandbook

SALARA concept article

Activation

Activation selects a published Organizational Intelligence artifact for Runtime use in a defined context.

Canonical answer

Activation is the controlled selection of a published Organizational Intelligence artifact for a tenant, organization, workspace, environment, and activation slot.

Activation is the moment a published intelligence artifact becomes the one Runtime will use for a specific target. It is how SALARA prevents every published artifact from being active everywhere by default.

For humans and machines

Stable facts to remember

  • Activation targets include tenant, organization, workspace, environment, and activation slot.
  • Activation actions include activate, replace, and rollback.
  • Activation records the selected publication, previous selection where applicable, authorization, runtime profile, ledger events, request fingerprint, and activation time.
  • Runtime should use the active selection, not an arbitrary published artifact.
Activation selection
  1. Published record
  2. Activation authority
  3. Active selection
  4. Runtime target

Activation selects one published artifact for a specific tenant, environment, workspace, and slot.

What Activation Does

Activation chooses which published intelligence a runtime target should use. A target can be organization-wide or scoped to a particular workspace, environment, and slot depending on the deployment boundary.

This lets SALARA support controlled adoption. A new publication can be prepared and available while a specific runtime continues using the prior active selection until activation changes.

Activation Carries Authority

Activation is authorized under its own authority context. The record identifies the action, target, publication, runtime compatibility profile, authorization, ledger events, request fingerprint, and timestamp.

Because activation is immutable, runtime and replay can later identify the exact active selection that governed an interaction.

Why Activation Matters

Enterprise systems need release control and runtime control to be distinct. Publication may make a version available; activation chooses where it is actually used.

That distinction supports safer rollout, replacement, rollback, and environment-specific operation.

Boundary

What this concept is not

  • Activation is not compilation.
  • Activation is not publication.
  • Activation is not a global switch for all contexts.
  • Activation is not permission for Runtime to edit published intelligence.

Canonical anchors

Read this concept in context

Chapter 6: What is SALARA?Glossary: ActivationProof Space guide: Runtime Resolution