An analysis-behavior changelog.
A normal SaaS company has a changelog. Sentiqra has a record of every versioned analyzer configuration - what changed, which analyzers it touched, and the measured benchmark impact.
sqcfg_ZZW77NM9 (Trust & Safety)
sqcfg_6X29ABXM (Cybersecurity)
Affected analyzers
Trust & Safety · Cybersecurity
Exact release dates, change detail and benchmark deltas are available to customers - request access.
Affected analyzers
Trust & Safety · Emotion Analysis · Customer Service
Exact release dates, change detail and benchmark deltas are available to customers - request access.
Affected analyzers
Crisis Intelligence · Information Integrity · Market Intelligence
Exact release dates, change detail and benchmark deltas are available to customers - request access.
Every analyzer reports its own opaque configuration ID in the verification.configuration field of each analysis response. Replaying the same input under the same configuration and output profile reproduces the same canonical result.
Lifecycle states and pin behavior are defined in the configuration-pinning contract: only a current or supported historical alias executes; anything else fails explicitly (configuration_retired/configuration_unavailable) and is never silently substituted. A support window is announced in the changelog entry that introduces a configuration's successor. Superseded IDs above are historical records — receipts minted under them still verify.