SALARAHandbook

SALARA concept article

Acquisition Providers

Acquisition Providers are the bounded interfaces SALARA uses to bring source material into the governed intake lifecycle.

Canonical answer

Acquisition Providers are source and storage adapters that acquire material, detect content, persist managed assets, and hand source records into Knowledge CI/CD without granting intelligence authority.

Acquisition Providers help SALARA bring source material in. They do not decide that the material is true, approved, compiled, published, active, or runtime-authoritative.

For humans and machines

Stable facts to remember

  • The implementation supports acquisition methods such as URL and upload.
  • Acquisition records method, status, duplicate state, source, origin, material, asset, content type, byte size, content hash, references, and timestamps.
  • Managed Asset Providers expose storage operations and health checks for durable acquired content.
  • Acquisition can fail safely with explicit failure codes such as unsupported protocol, blocked destination, timeout, unsupported content type, upload too large, duplicate conflict, and persistence failure.
Acquisition boundary
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. URL or upload
  2. Managed asset
  3. Source record
  4. Knowledge CI/CD

Acquisition Providers bring source material in without granting it Organizational Intelligence authority.

What Acquisition Providers Do

Acquisition Providers bring source material into SALARA's governed intake boundary. They may fetch a URL, accept an uploaded document, detect content type, hash bytes, store a managed asset, and create or update source records.

That work is foundational because Organizational Intelligence needs source evidence. But acquisition is deliberately separated from governance so source possession does not become organizational authority.

How Acquisition Stays Bounded

The implementation tracks explicit acquisition statuses such as queued, acquiring, acquired, stored, ready for extraction, unsupported, and retryable or non-retryable failure. It also records duplicate state so repeated material can be recognized without pretending duplicate source references mean new intelligence.

Failure is part of the contract. Unsupported protocols, blocked destinations, timeouts, oversized responses, unsupported content types, empty uploads, invalid files, storage failures, duplicate conflicts, persistence failures, and missing operational context are represented explicitly.

Why Acquisition Providers Matter

Enterprise knowledge comes from many places: documents, URLs, repositories, uploads, managed assets, and additional connectors. Acquisition Providers let SALARA expand the source boundary without weakening the governance boundary.

That is especially important for Demo Phase 2: Enterprise Acquisition. The demonstration can show knowledge entering SALARA while preserving the distinction between acquiring material and approving Organizational Intelligence.

Boundary

What this concept is not

  • An Acquisition Provider is not governance.
  • An Acquisition Provider is not evidence approval.
  • An Acquisition Provider is not a Runtime source of authority.
  • An Acquisition Provider is not a guarantee that acquired material will produce accepted Assertions.

Canonical anchors

Read this concept in context

Chapter 6: What is SALARA?Proof SpaceResearch Library

Related SALARA concepts

Knowledge CI/CDKnowledge CI/CD is the governed path by which knowledge enters SALARA before it can become runtime-authoritative.AssertionsAssertions are the atomic governed units of Organizational Intelligence in SALARA.GovernanceGovernance is how SALARA decides what organizational knowledge may become trusted Organizational Intelligence.PublicationPublication is the controlled step that makes compiled Organizational Intelligence available for activation.