> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elevatedsignals.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Welcome to Invariant

> Meet Elevated Signals Invariant: connected quality workflows, clear ownership, and a hash-chained, tamper-evident audit trail.

**Elevated Signals Invariant** is an electronic Quality Management System (eQMS) for regulated
manufacturing. It brings **deviations, CAPAs, complaints, change control, documents, training, and
quality tasks** into one quality workspace, with electronic signatures at supported decision points
and a **hash-chained, tamper-evident audit trail**.

The aim is practical: spend less time moving between spreadsheets, shared folders, and email,
and more time resolving quality issues. Keep the record, its owner, the work it requires, and its
supporting evidence connected.

<Note>
  Invariant is in active development and beta review. Availability depends on the deployed release
  and the capabilities enabled for your organization. A roadmap item or a build announcement is not
  confirmation that a workflow is available in your account.
</Note>

## Start with the work your team needs to do

| Your workflow                                                            | Where to start                                                                                                              |
| ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- |
| Record an issue, investigate it, and follow through on corrective action | [Deviations](/invariant/reference/deviations) and [CAPAs](/invariant/reference/capas)                                       |
| Classify a product complaint and link the required follow-up             | [Complaints](/invariant/reference/complaints)                                                                               |
| Give a quality request or action a clear owner, due date, and status     | [Quality tasks](/invariant/reference/quality-tasks)                                                                         |
| Review controlled documents and record approved changes                  | [Documents](/invariant/reference/documents) and [Change control](/invariant/reference/change-controls)                      |
| Assign training and connect a CAPA to signed retraining evidence         | [Training](/invariant/reference/training-management) and [the CAPA retraining loop](/invariant/how-to/capa-retraining-loop) |
| Review trends, export evidence, and inspect recorded history             | [Reports](/invariant/reference/reports) and [Audit trail verification](/invariant/compliance/audit-trail-tamper-evidence)   |

Configured CAPA retraining actions issue assignments when the action is completed. Where that loop
is enabled, the CAPA cannot finish until the required signed, passing training evidence exists.
This is not a general promise that every SOP change automatically retrains everyone.

## For quality teams and implementation partners

Start with one site's real workflow and its SOPs. Walk through an issue, assign the follow-up work,
review the evidence, and check who must approve it. Use that exercise to identify setup and training
needs before expanding the rollout.

The [Quickstart](/invariant/quickstart) explains account access and the core quality loop.
The [first-deviation walkthrough](/invariant/tutorials/first-deviation-to-closure) provides a practical
starting point for a guided session. In-app page guides and the Help Center support day-to-day use
where enabled; they complement your organization's procedures and role-specific training.

For a trial or partner-led rollout, agree the first site, users, sample workflow, and success criteria
with Elevated Signals. A self-serve signup, a cross-client consultant workspace, and automatic access
to all facilities are not assumed parts of that arrangement.

## What is on the roadmap

The [live product roadmap](https://elevatedsignals.canny.io/) shows planned work, work in progress,
and completed items. Read each item's scope and availability notes, then add feedback about the
workflow you need. Planned items are direction, not delivery-date commitments.

Three distinctions are especially useful when evaluating Invariant:

* **Complaint records are not automated complaint intake.** Controlled complaint capture and
  classification are implemented for enabled organizations. Email/web intake and complaint-specific
  AI extraction or triage are not available workflows.
* **Quality work is not yet connected to live ES production data.** Batch/lot annotations have a
  limited manual workflow. Live batch context, automatic deviation drafts from production events,
  and quality status flowing back to operations remain integration roadmap work.
* **One organization's sites are not a consultant's separate clients.** The broader multi-site
  quality program is still being developed. Cross-client oversight and access need separate scoping;
  the roadmap is not a claim that they are supported today.

AI assistance, where available, produces provisional suggestions for human review. It does not
replace a quality decision, electronic signature, or intended-use validation.

See the [Changelog](/invariant/changelog) for dated build updates and
[Compliance & Validation](/invariant/compliance/overview) for the evidence and its boundaries.

## About the name

Quality is not about standing still; it is about improving without losing the thread of truth.
Processes evolve, people learn, and records need corrections. The name expresses the value of
preserving an honest history of those changes, with clear responsibility.

The technical mechanism is the hash-chained, tamper-evident audit trail. Verification checks the
content and links of covered audit records. A passing result demonstrates internal consistency at
that point in time; it does not prove completeness against a privileged wholesale rewrite or tail
deletion without an external anchor. See [how verification works](/invariant/compliance/audit-trail-tamper-evidence).

<Note>
  Invariant was previously named QualityCore. It is the same product, the same team, and the same
  roadmap. Existing `/qualitycore/...` documentation links redirect here automatically.
</Note>

## Who this documentation is for

<CardGroup cols={2}>
  <Card title="QA Specialists" icon="clipboard-check">
    Day-to-day operators raising deviations, driving CAPAs, and signing records.
  </Card>

  <Card title="Quality Managers" icon="chart-line">
    Program owners tracking closure SLAs, trends, and audit readiness.
  </Card>

  <Card title="Quality & Implementation Partners" icon="handshake">
    Consultants mapping client SOPs to workflows, guiding setup, and identifying gaps during a trial.
  </Card>

  <Card title="Technical Administrators" icon="gear">
    Client-side IT configuring users, roles, authentication, and security.
  </Card>

  <Card title="Auditors & Validators" icon="shield-check">
    External consumers of the [Compliance & Validation](/invariant/compliance/overview) evidence.
  </Card>
</CardGroup>

## What makes Invariant different

* **Connected follow-through.** Link quality records, assigned work, training, and evidence within
  the supported workflows.
* **Verifiable history.** Check the stored organization audit chain within the boundaries described above.
* **Built to support 21 CFR Part 11 and EU Annex 11 expectations**, with controls designed to support your
  intended-use validation.
* **Clear, guided workflows** — designed to make routine quality work easier to understand.

<Note>
  Invariant includes controls designed to support customer validation and regulated use. It is not
  represented as GMP compliant, Part 11 certified, or fully validated on your behalf — intended-use
  validation remains program specific. See [Compliance & Validation](/invariant/compliance/overview).
</Note>