GOVERNATLAS / PRODUCT DOSSIER

Vijil

Vijil describes Discover for agent identity, Diamond for evaluation and Dome for runtime controls; its current site identifies Darwin as in development.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate the named module and its operating role. Agent identification, evaluation and runtime limits solve different problems and may have different dependencies. The current site marks Darwin as in development; do not let the full trust-loop illustration imply an available self-improving service or a verified security guarantee.

What this record does not establish

Darwin is not represented as generally available. Vendor trust scores and published improvements are not adopted as independent security or compliance findings.

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

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗

A test worth running

In an authorized synthetic agent workflow, connect one discovered identity to an evaluation case and an observed runtime decision. Change one policy version and repeat the adversarial and benign tasks. Retain the module configuration and separate observed results from vendor-published trust scores.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

A selected-module availability and responsibility map.
An identity-to-case-to-action trace with an explicit retest boundary.

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.

vendor asserted

Vijil describes Discover for agent identity, Diamond for evaluation and Dome for runtime controls; its current site identifies Darwin as in development. Scope: primary documentation only; no independent product test or compliance determination.

Source, dates & preserved provenance

Vijil — current primary product documentation ↗

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

Artifact SHA-256: 3257731724c8e650353ea60f4da80f9284490d6b4b2c09fba2a11e435c7e5524

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

Source register

Vijil — current primary product documentation ↗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.

Can you provide a selected-module availability and responsibility map for the selected configuration?

Can you provide an identity-to-case-to-action trace with an explicit retest boundary for the selected configuration?

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 ↗