CDT
Conduit
Ingest and normalisation
What it does
Conduit is the entry point. It resolves heterogeneous formats, encodings and metadata schemas into one typed, addressable record, so every downstream module works against the same shape regardless of the source.
Partial submissions, inconsistent naming and duplicates across sources are detected at the point of entry, where they are a query, rather than downstream, where they are a correction.
What it accepts
- Submissions
- Files and their accompanying metadata, arriving singly or as mixed batches under one identifier. The specific formats supported in an engagement are named in the statement of work.
- Schemas
- A written schema per source describing how its records map to the typed record. New sources are added by configuration, not by rebuild.
What it emits
- Typed records
- One addressable record per submission, carrying the resolved fields, the source identity and the ingest history.
- Entry findings
- Structured findings for incomplete submissions, naming conflicts and cross-source duplicates, raised at the point of entry.
The configuration surface
Configuration belongs to the client. It encodes what your specialists already know, and it is versioned like code.
- Source schemas
- The mapping from each source to the typed record.
- Identity rules
- What makes two submissions the same submission.
- Completeness expectations
- What a whole submission contains, per source.
What it produces as evidence
- Ingest record
- A versioned record of what arrived, from where, when, and how it was resolved, for every submission.
What it is tested against
Conduit is tested against acceptance criteria agreed in the statement of work: named sources resolved to the typed record, defined completeness and duplicate cases detected, and the ingest record produced for every submission. If a criterion cannot be written for a source, that source is not in scope.