GOVERNATLAS / PRODUCT DOSSIER

SolasAI

SolasAI describes software for analyzing algorithmic disparities, comparing model alternatives and producing supporting documentation.

THE DOCUMENTED SCOPE

What the current evidence describes.

Source-attributed capabilities and limits. Inspect the full record before drawing a conclusion.

vendor asserted

The vendor describes generating model alternatives and documentation to support a reviewer’s choice; their validity and fairness are not independently established here.

Inspect the evidence ↘
vendor asserted

It describes Illumination as monitoring drift, quality changes and emerging fairness risks.

Inspect the evidence ↘
vendor asserted

SolasAI describes Beacon as its offering for identifying model disparities and exploring model refinements.

Inspect the evidence ↘

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Treat disparity analysis, alternative-model search and ongoing monitoring as separate jobs. Current material names Beacon and Illumination; confirm which offering is included in the trial. A lower reported disparity needs a defined comparison population and outcome, while a proposed alternative needs its own feasibility and performance review.

What this record does not establish

The platform description does not establish fairness, causal drivers, viable alternatives in every setting or reduced legal risk. Beacon and Illumination entitlements and deployment responsibilities require confirmation.

1 current source · 4 published assertions
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

Using fictional queue-routing records, define a population and metric before comparing the original and proposed model. Retain missing labels and sparse cohorts, then inspect a monitoring change separately from the offline comparison. Ask a reviewer to explain why one alternative was rejected.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. A named-offering population/metric/model-version record.
  2. A rejected alternative and a separate monitoring observation with unresolved limits.

THE OPERATING DETAIL

Follow a disparity from measurement to an owned decision.

GovernAtlas analysis: practical review considerations, not findings from a product test.

Preserve the population definition

Use a synthetic dataset with documented groups, labels and missing-value treatment. Fix the comparison population before reviewing a disparity measure. Then vary one label or grouping choice and retain both results. The point is to expose how an interpretation depends on the data definition, not to manufacture a favorable metric.

Examine the alternative

Ask for a proposed alternative and a baseline evaluated on the same held-out cases. Review group outcomes and predictive performance separately, including any group that worsens. Require an explanation of which model or decision rule changed. A generated alternative needs a responsible reviewer and operational constraints before adoption.

Make drift actionable

Choose an observation that should prompt investigation after deployment. Name the monitoring owner, expected review time and evidence needed to distinguish a population change from a data-quality issue. Keep the original accepted limitation in view; an alert or a quieter dashboard does not by itself establish that a fairness concern is resolved.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
vendor asserted

The vendor describes generating model alternatives and documentation to support a reviewer’s choice; their validity and fairness are not independently established here.

Source, dates & preserved provenanceSolasAI — primary scope and current identity ↗

Authority: vendor owned
Observed 2026-10-16 · Reviewed 2026-10-16 · current until 2026-11-15

Artifact SHA-256: a884814538e33c400f768a6f508a16e1939d7763c5d99988d52dca4b1fcb90dd

The hash identifies the preserved capture. The live source may have changed.

02
vendor asserted

It describes Illumination as monitoring drift, quality changes and emerging fairness risks.

Source, dates & preserved provenanceSolasAI — primary scope and current identity ↗

Authority: vendor owned
Observed 2026-10-16 · Reviewed 2026-10-16 · current until 2026-11-15

Artifact SHA-256: a884814538e33c400f768a6f508a16e1939d7763c5d99988d52dca4b1fcb90dd

The hash identifies the preserved capture. The live source may have changed.

03
vendor asserted

SolasAI describes Beacon as its offering for identifying model disparities and exploring model refinements.

Source, dates & preserved provenanceSolasAI — primary scope and current identity ↗

Authority: vendor owned
Observed 2026-10-16 · Reviewed 2026-10-16 · current until 2026-11-15

Artifact SHA-256: a884814538e33c400f768a6f508a16e1939d7763c5d99988d52dca4b1fcb90dd

The hash identifies the preserved capture. The live source may have changed.

04
vendor asserted

SolasAI describes software for analyzing algorithmic disparities, comparing model alternatives and producing supporting documentation. Scope: primary documentation only; no independent model test, fairness determination, causal finding or compliance approval.

Source, dates & preserved provenanceSolasAI — primary scope and current identity ↗

Authority: vendor owned
Observed 2026-10-16 · Reviewed 2026-10-16 · current until 2026-11-15

Artifact SHA-256: a884814538e33c400f768a6f508a16e1939d7763c5d99988d52dca4b1fcb90dd

The hash identifies the preserved capture. The live source may have changed.

Source register

SolasAI — primary scope and current identity ↗vendor owned · captured 2026-10-16
Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

Can you provide a named-offering population/metric/model-version record for the selected configuration?

02

Can you provide a rejected alternative and a separate monitoring observation with unresolved limits for the selected configuration?

03

Which exact version, entitlements, data paths and responsible roles apply?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗