Technical diligence
Check what a company’s documents say about its systems against what its other records show.
Input, workflow, and limits →A product by Assertion Labs · In development
CliqueMap is being built to bring documents, entities, and claims into one investigation. Explore how things relate, trace each conclusion to its sources, and see what is still uncertain.
CliqueMap is in development. There are no accounts or hosted access yet. Pilots are scoped by conversation.
Q1 · Can the report worker read customer records?
Source assertion The report worker reads only from billing-exports and has no access to customer-records.
The report worker runs as svc-report-worker. It reads only from the billing-exports queue and has no access to the customer-records store.
{ "Sid": "TemporaryBackfill", "Effect": "Allow", "Action": "store:Read", "Resource": "store/customer-records/*", "Condition": { "DateLessThan": { "now": "2026-06-30T00:00:00Z" } } }Add the documents and records you are permitted to review. Each version keeps its date and where every excerpt came from.
See the systems, organizations, and statements involved. Each connection is a claim, linked to the passages that support or contradict it.
Record interpretations with their review state, keep open items visible, and export a brief that cites its sources.
The goal is fewer unsupported conclusions and reasoning you can inspect. That is the intent of the design, not a measured result.
Check what a company’s documents say about its systems against what its other records show.
Input, workflow, and limits →Trace access boundaries, data flows, and model integrations to the documents that describe them.
Input, workflow, and limits →Keep track of which papers, results, and notes support a technical position, and which cut against it.
Input, workflow, and limits →This website and its synthetic walkthrough exist today. The capabilities below are being built, and each one stays marked as in development until there is evidence for it.
| Capability | What it is for | Public status |
|---|---|---|
| Versioned source records | Keep each source version, its date, and where excerpts came from. | In development |
| Entity resolution | Recognize when different sources refer to the same system, organization, or document. | In development |
| Claims with supporting and conflicting evidence | Link each claim to the exact passages that support it or cut against it. | In development |
| Time-aware relationships | Show when a relationship was stated, observed, or replaced. | In development |
| Permission-aware retrieval | Check access before retrieving, expanding, or exporting evidence. | In development |
| Investigations and briefs | Collect a question, its evidence, and its open items into a reviewable brief. | In development |
A capability is shown as available only when there is dated test evidence for it and an owner release approval. Passing tests do not change this table on their own.
A pilot is one scoped question over a corpus you are permitted to share. It ends with a brief and a list of its limitations. Architecture, security, and diligence advice from Assertion Labs is available on its own, separate from the software.
Get occasional product updates, release announcements, and invitations to try new features.