An inbox for evidence, and validations that read it

Drop a file in and Cyberwiz suggests what it proves; a catalog of reusable validations judges whether it holds.

EvidenceCompliance

Two halves of the same idea. The evidence inbox is a triage queue: drop files in, get AI mapping suggestions, accept or delete in bulk. An empty inbox is one large drop zone, pending instances of the same document combine into one, and a no-match reason is kept rather than discarded.

Validations became a catalog rather than bespoke code: 36 reusable validations as the base, with typed parameters per evaluator key. New document evaluators read the file itself: text-detect, date-extract, classification verify-fit, alert-review SLA and log-retention.

Improvements
  • Threshold, rate, coverage-diff and attribute-complete archetypes, so a new validation is configuration rather than a deployment.
  • Per-organization module access, gating what each customer sees.
  • The vendors table was redesigned, and a vendor auto-created from a connected integration carries that provider's logo and an Auto-added badge.
  • Framework logos, a readiness ring, an applicability drawer and bulk owner and applicability actions.
  • An AI copilot for writing questions, and CSV/XLSX import for systems, processes and data repositories.
  • Hebrew across vendor management: list, detail, tabs, dialogs and the data-table's sort, filter and export surfaces.
Fixes
  • Common controls always open their page, never a blank drawer.
  • asset_coverage is a pure union, not a diff.
  • Every compliance read refreshes after an evidence run, instead of showing the number from before it.