Documentation

Reference documentation for the four modules and the architecture they share. Ungated: no sign-up, no email wall. It is meant to be read before anyone has contacted anyone.

1.0Reference

What this documentation covers

Architecture

How the pieces fit

How the four modules fit together, the deployment topologies supported, and which party holds the data in each.

Upstream sources vary in format, encoding, and structure, and change without warning. Conduit absorbs that variation so nothing downstream has to handle it. Every input becomes the same typed output regardless of where it came from.

Signal

SGL

Analyse and score

Signal runs close to the source so issues surface before anything downstream takes a dependency on them. Checks are written as code, with a review queue for anything the checks cannot settle.

Trace

TRC

Retrieve and link

Retrieval across everything the pipeline has processed, structured and semantic. Whether you are running a search or comparing outputs for consistency, every result names why it ranked where it did.

Gauge

GAU

Evaluation harness

The measurement plane: changing a model, a prompt or a threshold should produce a number comparable to the last number rather than an impression.

These pages describe the module surfaces as delivered: what each module does, what it accepts and emits, the configuration surface the client controls, and what each is tested against.

2.0On request

Available under NDA

Deeper material is supplied on request under NDA, within two business days: completed security questionnaires with gaps marked rather than left blank, technical deliverables, architecture and data flow documents for a specific deployment, and the change control procedure.