What Assertions Do
Assertions give SALARA a stable unit of intelligence governance. Instead of asking whether a whole document is trusted, SALARA asks whether a specific piece of understanding is acceptable for a defined organizational purpose.
That boundary matters because organizations often agree with one part of a source, reject another, and need clarification on a third. Assertions let governance operate at the level where actual organizational understanding changes.
How Assertions Work in SALARA
Source material can produce Candidate Assertions. Governance decides whether those candidates are approved, rejected, clarified, superseded, or preserved for later review. Approved Assertions can then be compiled into versioned Organizational Intelligence.
The implementation model records the Assertion kind, plane, normalized content, source references, source coordinates, evidence, provenance, applicability, relationships, owner, trust state, lifecycle state, knowledge standing, version, temporal validity, and lineage.
Why Assertions Matter
Assertions are what make Organizational Intelligence inspectable. A runtime answer can point back to the governed units it used rather than asking a reader to trust a generated explanation after the fact.
They also make change safer. A policy update can supersede one Assertion without pretending the entire prior knowledge base vanished or remained fully current.