SALARAHandbook

SALARA concept article

Knowledge CI/CD

Knowledge CI/CD is the governed path by which knowledge enters SALARA before it can become runtime-authoritative.

Canonical answer

Knowledge CI/CD is the governed intake and processing lifecycle that moves source material toward candidate Assertions, review, compilation, publication, activation, and runtime use.

Knowledge CI/CD is how SALARA avoids automatic memorization. New knowledge can enter, but it must pass through governed stages before it can influence Runtime.

For humans and machines

Stable facts to remember

  • Knowledge CI/CD begins with source material entering a governed intake boundary.
  • The public implementation records source addition, compile job creation, compile start, compile completion, and Candidate Assertion creation in the Operational Ledger.
  • Automatic processing supports selected content types, but unsupported content is skipped rather than treated as authoritative.
  • Knowledge CI/CD feeds governance; it does not replace governance.
Knowledge CI/CD intake
Knowledge AccumulationA forest-green knowledge core is surrounded by ivory source pills, showing accumulated organizational memory.KnowledgePoliciesDocumentsExpertsApprovalsPrior decisionsCustomer historySystem recordsKnowledge accumulation
Knowledge gathers as records, experience, policy, precedent, and memory before any single interaction asks for it.
  1. Source added
  2. Compile job
  3. Candidate Assertions
  4. Governed review

Knowledge CI/CD moves acquired source material toward Candidate Assertions while preserving the governance boundary.

What Knowledge CI/CD Does

Knowledge CI/CD gives knowledge intake an operational lifecycle. It helps SALARA register sources, process material, create Candidate Assertions, and record events before anything becomes runtime-authoritative.

The phrase deliberately borrows the discipline of controlled change from software delivery, but applies it to organizational knowledge. Knowledge entering the system is not the same as knowledge approved for use.

How It Appears in SALARA

The implementation includes source registration, compile job creation, extraction, Candidate Assertion admission, source status updates, job status updates, and Operational Ledger events. Supported automatic processing can handle formats such as PDF, HTML, Markdown, and plain text.

When candidates are created, they enter the governed review boundary. From there, governance determines what the organization is prepared to approve.

Why Knowledge CI/CD Matters

Organizations change continuously. Policies, procedures, exceptions, products, and customer conditions do not stay still. Knowledge CI/CD gives SALARA a way to absorb change without letting every new artifact immediately rewrite Organizational Intelligence.

That makes continuous Organizational Intelligence evolution possible while preserving review, evidence, and accountability.

Boundary

What this concept is not

  • Knowledge CI/CD is not automatic knowledge ingestion without review.
  • Knowledge CI/CD is not the same as Intelligence CI/CD.
  • Knowledge CI/CD is not a vector-index refresh.
  • Knowledge CI/CD is not runtime authority by itself.

Canonical anchors

Read this concept in context

Chapter 6: What is SALARA?Glossary: Operational LedgerProof Space

Related SALARA concepts

Acquisition ProvidersAcquisition Providers are the bounded interfaces SALARA uses to bring source material into the governed intake lifecycle.AssertionsAssertions are the atomic governed units of Organizational Intelligence in SALARA.GovernanceGovernance is how SALARA decides what organizational knowledge may become trusted Organizational Intelligence.CompilationCompilation is the controlled transformation of approved Assertions into deterministic, deployable Organizational Intelligence.