SALARAHandbook

SALARA concept article

Organizational Intelligence Compiler

The Organizational Intelligence Compiler is the SALARA component that transforms approved Assertions into deterministic, versioned, deployable Organizational Intelligence.

Canonical answer

The Organizational Intelligence Compiler is the implementation component responsible for deterministic compilation of approved Assertions into deployable Organizational Intelligence artifacts.

The compiler is where approved organizational understanding becomes a structured artifact that can be validated, packaged for replay, placed in a publication envelope, and later used by Runtime after publication and activation.

For humans and machines

Stable facts to remember

  • The compiler framework version is represented as an explicit framework contract in the implementation.
  • Compiler stages include input boundary, intermediate representation construction, validation, artifact assembly, artifact validation, replay packaging, and publication envelope.
  • Compiler artifacts include intermediate representations, compiled artifacts, validation reports, replay manifests, publication envelopes, and portable exports.
  • The compiler is deterministic and preserves lineage, provenance, validation results, and trace events.
Compiler stages
  1. Input boundary
  2. Intermediate representation
  3. Artifact validation
  4. Replay and publication packaging

The Organizational Intelligence Compiler is the component that performs deterministic compilation.

What the Compiler Does

The Organizational Intelligence Compiler is the concrete SALARA component that turns approved Assertions into deployable Organizational Intelligence. It is the implementation concern behind the broader lifecycle step called compilation.

It reads approved governed inputs, constructs an intermediate representation, validates boundaries, assembles artifacts, packages replay information, and prepares a publication envelope.

Why It Is Deterministic

The compiler contract includes stable input ordering, canonical content addressing, explicit timing, declared policy versions, and traceable stage outputs. This is how SALARA avoids treating compilation as a hidden interpretation step.

If the same governed boundary is compiled under the same contract, the organization should be able to identify what was compiled and why the artifact is the artifact it is.

Why the Compiler Matters

The compiler makes Organizational Intelligence deployable without making it opaque. It preserves lineage and provenance so later publication, activation, runtime use, and replay can point back to the exact governed inputs.

That is central to SALARA's public claim: runtime guidance should come from governed, versioned, inspectable intelligence rather than temporary reconstruction.

Boundary

What this concept is not

  • The Organizational Intelligence Compiler is not a language model.
  • The compiler is not the owner of governance decisions.
  • The compiler is not publication authority.
  • The compiler is not the Runtime layer.

Canonical anchors

Read this concept in context

Chapter 6: What is SALARA?Glossary: Organizational Intelligence CompilerProof Space guide: Compilation