Solutions
Three routes, each one question at a time
Each route starts from a specific review question and ends with a brief you can check. Pilots are scoped by conversation while the product is in development.
Technical diligence
Check what a company’s documents say about its systems against what its other records show.
- Input
- A permitted set of architecture documents, configuration excerpts, change records, and written answers from the target.
- Question
- Does the evidence support what the target says about how its product is built and operated?
- Workflow
- Map the systems and claims, link each claim to its passages, and flag where documents disagree or have gaps.
- Deliverable
- An evidence register and a brief that separates supported, conflicting, and unverified claims.
- Limitation
- The work covers only the material provided. It does not replace legal, financial, or security audit opinions.
AI and security architecture review
Trace access boundaries, data flows, and model integrations to the documents that describe them.
- Input
- Design documents, access policies, integration descriptions, and change history you are permitted to share.
- Question
- Where do stated boundaries match the recorded configuration, and where do they diverge?
- Workflow
- Link components, identities, and data stores. Then compare stated boundaries with configuration and change records over time.
- Deliverable
- A reviewable brief with cited passages, conflicts, and the evidence still needed to close each item.
- Limitation
- Document-based review is not penetration testing, runtime verification, or certification.
Research and R&D evidence analysis
Keep track of which papers, results, and notes support a technical position, and which cut against it.
- Input
- Papers, internal notes, experiment records, and specifications you have rights to use.
- Question
- What supports this technical direction, what contradicts it, and what changed between versions?
- Workflow
- Extract claims with their sources and versions, and keep reviewed interpretations separate from source statements.
- Deliverable
- A claim map and a brief with citations, conflicts, and open questions.
- Limitation
- Being cited does not make a result correct. Reproducing results is outside the scope.
Internal application: Trace
Assertion Labs runs a private, internal tool called Trace for finding opportunities and keeping track of professional relationships. Trace is planned to be the first internal application to use CliqueMap’s evidence capabilities. That integration has not been verified yet. Trace is not a public product and is not a customer case study.