Skip to content
KAIScopeBY KATHAROS
Research and practical guidance

Understand the evidence

Guides for reading an assessment, comparing revisions and knowing where automated analysis ends.

Try a comparison

The label depends
on the coverage.

Change the example conditions to understand how report comparison should be interpreted. These counts are illustrative.

Example comparison conditions

An absent finding can be labeled not reported within comparable checked coverage. That is not proof of remediation.

COMPARISON LABIllustrative counts
Persisting
4
Introduced
2
Not reported
3
Comparable coverage

No comparison label establishes that the project is secure.

01 / Assessment guide

Read the coverage before the count

A complete assessment means the implemented checks finished. It does not mean a project is secure. Review compiler compatibility, excluded files, unsupported analysis and the boundary of each rule.

  1. Check the source fingerprint and report provenance.
  2. Read coverage, diagnostics and unsupported behavior.
  3. Inspect severity, confidence, evidence and remediation.
  4. Retest the changed code; a triage status is not verification.
02 / Revision guide

Compare without assuming a fix

In the private console, open an assessment, expand “Compare with another assessment”, select a baseline and confirm both describe the same project. You need two reports in one workspace.

PersistingMatching finding identity remains
Not reportedAbsent within comparable checked coverage
Not assessedMissing coverage or incompatible settings

Renamed files, changed expressions and engine differences can affect matching. No comparison label proves remediation.

03 / Investigation and analytics design

Context with a traceable source

Planned case views will connect assets, technical findings, event timelines and review decisions. Relationships must distinguish observed blockchain events, customer ledger records, analyst annotations and externally supplied attribution.

Planned dashboards will add filters, saved views, charts and exportable summaries. Security data stays private by default. An address relationship alone does not prove common ownership, and an alert alone does not establish fraud.

The delivery path

Built in the right order

Hosting is deferred. Foundation and offline workflows come before live transaction controls.

  1. 01Asset inventory & member permissionsNext foundation
  2. 02Versioned baselines & offline testingPlanned
  3. 03Event replay & investigation casesPlanned
  4. 04Read-only live connectorsPlanned
  5. 05Shadow decisions & test holdsPlanned
  6. 06Opt-in production enforcementPlanned
A clear next step

Start with the evidence you have

Use the existing assessment workflow while the next platform foundations are built.

Open private console ↗