Invariant eQMS Roadmap

Attach supported evidence files to supported quality records where attachments are enabled. The workflow records a SHA-256 file fingerprint and checks the stored bytes on download against the recorded value. This detects a mismatch within the implemented verification path. It is not a promise of WORM storage, provider-enforced retention, or protection against a privileged rewrite of both stored evidence and its verification history. Supported record types, file formats and limits are defined by the current release. See: https://docs.elevatedsignals.ai/invariant/how-to/attach-evidence

Covered quality events are recorded in a per-organization, hash-chained audit trail. The verifier checks the hashed content and links of stored audit rows and identifies a mismatch when a check fails. Implemented scope: Attributed human, system and AI events within the supported event inventory Per-organization hash-chain verification Audit-history views and supported exports Verification establishes internal consistency at the time of the check. It does not prove that every possible action was recorded, or establish completeness against a privileged wholesale rewrite or tail deletion without an external anchor. This is tamper-evidence, not a compliance certification. Verification and its limits: https://docs.elevatedsignals.ai/invariant/compliance/audit-trail-tamper-evidence September 11, 2026 — Open a supported affected record directly from its audit event. Deleted, unavailable or unsupported records may not have a link; existing access restrictions still apply. Guide: https://docs.elevatedsignals.ai/invariant/compliance/audit-trail-tamper-evidence

Capture a named signer's identity, time, meaning, credential re-verification evidence, and content binding at supported approval and closure transitions. Signatures are linked to the record and audit provenance. Coverage depends on the implemented transition and the controls enabled for your organization. This is not a claim that every possible quality decision is covered. Built to support 21 CFR Part 11 and EU Annex 11 expectations. Customer intended-use validation and regulated-use decisions remain program specific; this is not Part 11 certification. See: https://docs.elevatedsignals.ai/invariant/how-to/electronic-signature