GOVERNATLAS / PRODUCT DOSSIER

Progress Agentic RAG

Progress describes Agentic RAG for ingesting and indexing enterprise information and providing retrieval-augmented AI answers.

THE DOCUMENTED SCOPE

What the current evidence describes.

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

vendor asserted

The product page describes source citations and REMi evaluation metrics for answers; citations and scores alone do not establish factual accuracy.

Inspect the evidence ↘
vendor asserted

Its retrieval scope includes hybrid search, chunking and metadata filtering configured per use case.

Inspect the evidence ↘
vendor asserted

Progress describes a shared ingestion and indexing layer for enterprise content, including documents, spreadsheets, audio and video.

Inspect the evidence ↘

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Inspect retrieval permissions before judging the generated answer. A cited response can be grounded in a document the requesting user should not have received. Define the connector, index, identity propagation and delivery surface, and distinguish the retrieved content from a separately computed quality score or a product-level governance statement.

What this record does not establish

The former Nuclia domain redirects to Progress Agentic RAG; one current identity is recorded. Source citations and built-in evaluation do not establish authorization, factual correctness or entitlement parity across delivery surfaces.

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

Index fictional public and restricted documents in an authorized test tenant. Compare the same query under two test identities, then revoke access at the source and inspect the next retrieval. Retain returned chunks, citations and the actual identity context, including a stale permission observation if one occurs.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. A connector/index/principal/delivery-surface permission map.
  2. A source-revocation trial with returned chunks, citations and unresolved synchronization limits.

THE OPERATING DETAIL

Follow the source all the way to the answer.

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

Introduce an outdated document

Use fictional policies with two versions and an explicit owner. Ask the same question before and after updating the indexed source. Retain the retrieved passages and answer citations. A current-looking answer is insufficient if a reviewer cannot determine which version supplied the supporting context.

Challenge the retrieval boundary

Create a restricted test document and two authorized test roles. Ask both roles an identical question and inspect the retrieved context as well as the final answer. Document metadata filters and identity propagation. An access-control statement needs validation for the actual integration path and configuration.

Inspect the scored answer

Choose a relevant answer with a citation that does not support its central statement. Compare the evaluation metric with a human reading of the source passage. Preserve the disagreement and the configured retrieval settings. A citation or quality score should help investigation, not replace verification of the answer’s evidence.

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 product page describes source citations and REMi evaluation metrics for answers; citations and scores alone do not establish factual accuracy.

Source, dates & preserved provenanceProgress Agentic RAG — primary scope and current identity ↗

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

Artifact SHA-256: 0ea9ae8ba867541408e0ae3c4f1b94322c2199962d952938f2634539ed795804

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

02
vendor asserted

Its retrieval scope includes hybrid search, chunking and metadata filtering configured per use case.

Source, dates & preserved provenanceProgress Agentic RAG — primary scope and current identity ↗

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

Artifact SHA-256: 0ea9ae8ba867541408e0ae3c4f1b94322c2199962d952938f2634539ed795804

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

03
vendor asserted

Progress describes a shared ingestion and indexing layer for enterprise content, including documents, spreadsheets, audio and video.

Source, dates & preserved provenanceProgress Agentic RAG — primary scope and current identity ↗

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

Artifact SHA-256: 0ea9ae8ba867541408e0ae3c4f1b94322c2199962d952938f2634539ed795804

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

04
vendor asserted

Progress describes Agentic RAG for ingesting and indexing enterprise information and providing retrieval-augmented AI answers. Scope: primary documentation only; no independent model test, fairness determination, causal finding or compliance approval.

Source, dates & preserved provenanceProgress Agentic RAG — primary scope and current identity ↗

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

Artifact SHA-256: 0ea9ae8ba867541408e0ae3c4f1b94322c2199962d952938f2634539ed795804

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

Source register

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 connector/index/principal/delivery-surface permission map for the selected configuration?

02

Can you provide a source-revocation trial with returned chunks, citations and unresolved synchronization 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 ↗