Assertion Labs / Products

CliqueMap An Assertion Labs product

In development

Evidence-backed intelligence for consequential technical questions. CliqueMap connects documents, entities, relationships, claims and source versions, so a conclusion can be traced to what supports it and what is still unknown.

CliqueMap is an Assertion Labs product. It is in development and is not yet available as a hosted service.

The problem

Conclusions outlive their evidence.

A diligence memo or architecture review rests on dozens of sources: design documents, configuration exports, vendor statements, earlier findings. They change, they disagree, and the link between a conclusion and its support is usually lost in a slide or a spreadsheet.

CliqueMap keeps those links explicit. Each claim records the source version it came from, the evidence that supports or contradicts it, and the limitations of that evidence. “Evidence-backed” means the support is exposed for inspection, not that a conclusion is guaranteed to be true.

How an investigation is organized

Sources → entities and claims → evidence → output.

  1. 01 Sources Documents, configuration and pages, each kept as a dated version.
  2. 02 Entities & claims The systems, people and statements they describe, and how they connect.
  3. 03 Evidence inspection What supports a claim, what contradicts it, and what remains unknown.
  4. 04 Investigation output A note that cites its sources and states its limitations.

Walkthrough

Inspect a claim.

Select a claim to see the sources behind it. This walkthrough uses a fictional system and fictional documents to show the evidence model; it is not the CliqueMap application.

Graphic: Assertion Labs advisory engagements inform the CliqueMap product, and CliqueMap supports repeatable investigations in later engagements.
Illustrative example · synthetic data Dataset v1.0.0

Can the support assistant read customer billing records?

Evidence for C1 · asserted in S3 (Vendor security FAQ)

  • contradicts assistant-svc: allow billing:ReadInvoice S2 · Service role policy, rev 14
  • supports The assistant reads ticket history only. S1 · Architecture overview, v3 · 2 Mar

Entities: Support assistant Billing API

Limitations. Policy revision 14 may differ from what is deployed. Deployed role bindings were not inspected.

Illustrative example with a fictional system and fictional documents. It shows the intended evidence model; it is not output from the CliqueMap software.

Initial use case

Technical diligence and AI/security architecture investigations.

The first workflow is the one Assertion Labs already performs in advisory work: assembling the evidence about one system, tracing each claim to its source and reporting the unknowns that matter for a decision.

Until the software is ready, that work is available as an advisory engagement.

Technical Risk & Evidence Diagnostic →

Current status & limitations

  • Release state: in development. No public sign-up, hosted beta or self-service access.
  • Pilots are discussed case by case. A conversation is not a commitment to provide access, a schedule or a price.
  • CliqueMap does not certify systems, prove claims true or replace expert review.
  • Do not send confidential material through the inquiry form.