Skip to content
Quantscope

Architecture

How the four modules fit together, where they run, where data sits in each topology, and how a deployed instance is configured and versioned.

1.0Modules

How the modules fit together

Conduit resolves incoming submissions into typed records. Assay checks them, routing what it cannot settle to a review queue where a qualified person decides. Concordance retrieves and ranks across the checked records. Baseline sits underneath the other three as the measurement plane: it holds the frozen evaluation corpus and scores every proposed change before release, and it never touches a production record.

imagesdocumentsmetadataMIXED SUBMISSIONSConduitCDTAssayASYtyped recordsReview queuea qualified person decidescannot settledecision, recordedConcordanceCNCchecked recordsBaselineBSLfixed corpus, one scoring methodmeasures
The pipeline and its measurement plane. Baseline measures the other modules rather than running inside the flow.
2.0Topologies

Deployment topologies

The preferred deployment runs every module inside the client environment. A hosted deployment exists as a negotiated exception, with its terms fixed in the agreement before any data moves.

Where data sits in each deployment topology
TopologyWhere the modules runWho holds the dataWhat crosses the boundary
Client environmentInside your environment, against your storage, under your identity providerYou. Quantscope holds no client data and no encryption keyNothing inbound. Software releases enter through your change control
Hosted (negotiated exception)In an environment operated for the engagementDefined in the agreement: region, retention and deletion are set before any data movesSubmissions in, records and findings out, as the data processing agreement defines
3.0Versioning

Configuration and versioning

Configuration as record
Schemas, rule sets, thresholds and routing rules are versioned artefacts. A deployed instance is the sum of named versions, so what ran is a written answer.
Release record
Every release names the module versions, model identities and configuration versions it contains, with the Baseline scores that qualified it.
Change control
Changes enter a deployed instance through the change control agreed in the statement of work, with re-qualification triggered by the thresholds written there.
Separation of instances
A validated instance is separated from development. Nothing reaches it except through a release, and the audit trail records what arrived and when.