Skip to content

Platform architecture

From a registry filing to a claim counsel will sign

Eight stages, two engines and one contract between them. Each stage is inspectable, and each output carries the origin of everything it was built from.

  1. 01

    Ingest

    Radar

    Four layers stream in continuously. Every item is stored with its origin, its retrieval time and a content hash before anything reads it.

  2. 02

    Entity resolution

    Radar

    Names, agents, officers and addresses resolve into one graph. A subsidiary that files under a trade name in one state and a legal name in another becomes one node, not two.

  3. 03

    Clustering

    Radar

    Observations that describe the same underlying event group together. The cluster records which layers contributed and whether those layers are independent of each other.

  4. 04

    Noise control

    Radar

    Coordinated claim sets, promoted material and interested-party documents are identified and weighted. A cluster that fails independence stands down with its reasoning retained.

  5. 05

    Governed handoff

    Contract

    A cluster becomes a case only when it is escalated, corroborated by two or more layers, above the independence floor, and assigned to a named analyst.

  6. 06

    Reconstruction

    Case Builder

    The case rebuilds the financial picture from primary records and states the difference against the reported figure, with the method note attached to the number.

  7. 07

    Hypothesis challenge

    Case Builder

    Each claim carries the alternative explanations that were tested, how they were tested and what the test returned. A claim with no tested alternative does not reach counsel.

  8. 08

    Gates

    Case Builder

    Evidence sufficiency, originality, jurisdiction, privilege and counsel review each hold the case. A blocked gate stops the work that depends on it and nothing else.

Orchestration contract

The manifest is the product, not a document about the product

Every engine, input, output, escalation rule, gate and prohibition is declared in one machine-readable manifest that the platform reads at run time. A reviewer can diff it between releases.

verity.engine.manifest/1.2
{
  "schema": "verity.engine.manifest/1.2",
  "engines": [
    {
      "id": "loffco.radar",
      "version": "4.3.1",
      "function": "discovery",
      "licensor": "LOFFCO Risk Management LLC"
    },
    {
      "id": "verity.casebuilder",
      "version": "2.6.0",
      "function": "investigation",
      "licensor": "VERITY"
    }
  ],
  "handoff": {
    "from": "loffco.radar",
    "to": "verity.casebuilder",
    "preconditions": [
      "cluster.status == escalated",
      "cluster.independence >= 0.65",
      "cluster.layers.length >= 2",
      "analyst_of_record assigned"
    ],
    "effect": "Creates a case file with the cluster attached as intake evidence. No claim inherits the cluster narrative. Every claim is rebuilt from primary sources inside the case."
  },
  "prohibitions": [
    "no-autonomous-submission",
    "no-public-accusation",
    "no-trading-recommendation",
    "no-unlawful-collection"
  ]
}

Build state

What is live in this environment, and what is the next layer

This build is the production interface and the orchestration contract, running against fictional demonstration data. The backend layer below is specified and scheduled, not shipped.

Live in this build

  • Dual-engine control center and desk lenses
  • Four-layer signal discovery and cross-source clustering
  • Noise, coordination and source-independence controls
  • Forensic case workspaces with reconstruction and pattern analysis
  • Hypothesis challenge and alternative-explanation testing
  • Evidence vault, claims matrix and source library
  • Five-gate governance with counsel disposition
  • Machine-readable engine manifest served at run time

Next backend layer

  • Live EDGAR ingest with acceptance-time indexing
  • State regulator and registry monitors
  • Model workers for reconstruction and pattern analysis
  • Persistent watchlist storage with per-tenant isolation
  • Evidence storage with write-once custody and hash chaining
  • Scheduled engine execution with run reproducibility

Stating the build state plainly is part of the diligence posture. A platform that claims live regulatory feeds it does not have fails the first technical review.

Access

See the radar run against your own credit book

A scoped pilot runs your obligor list through the four discovery layers for one quarter, with a named analyst and counsel review on every escalation.