Client Delivery › C5 spec: Integration config
C5 spec: Integration config
C5 / L5 Integration: which systems connect, under what contract, on what rhythm.
REQ-I-00, cataloged by default: no connection exists outside the source catalog. Every integration is expressed as parameters; a requirement that cannot be parametrized goes back to discovery, and dead-letter handling is always on.
REQ-I-00, cataloged by default: no connection exists outside the source catalog. Every integration is expressed as parameters; a requirement that cannot be parametrized goes back to discovery, and dead-letter handling is always on.
The ground rules and artifact-placement conventions on the C1 specification apply to every band: values enter once in the binding, everything downstream is generated, nothing is hand-edited. Columns: discovery section, binding key, the exact artifact the value materializes into, when it takes effect, and the check that verifies it.
The configuration map
| ID | Client input | Disc. | Binding key | Materializes as | Takes effect | Verified by |
|---|---|---|---|---|---|---|
| I-01 | Source system selection from the connector library | D | integration.sources[] | Connector instances registered in the source catalog + south tool-server enablement per source | On deploy | Catalog completeness against the discovery D inventory; no reachable source is uncataloged |
| I-02 | Credentials and OAuth grants | D, E | integration.credentials{} | Vault references only, in client-<name>/connectors/; scoped per tenant | On deploy | Secret-literal scan; per-tenant credential scoping test |
| I-03 | Data contracts: what each source promises, and what happens when it does not deliver | D | integration.contracts[] | Contract files contracts/<source>.yaml (fields, freshness, failure behavior) enforced in the sync path | On deploy | Contract violations dead-letter and alert; proven by a violation drill |
| I-04 | Field mappings: client schema to platform taxonomy | D | integration.mappings[] | Schema-map files consumed by the mapping toolkit | Next sync | Mapping coverage against contract fields; drift caught by the contract check, not in outputs |
| I-05 | Sync pattern and schedule per source: ETL batch, integration hub, API, real-time, near-real-time | D | integration.sync{} | Sync engine config per source, from the parametrized requirement sheets (playbook Track 3) | Next sync | Change-feed conformance; manual or periodic sync flags are rejected outside POC mode |
Acceptance
- Every source the roadmap's capabilities need is connected through the catalog, with contract and mapping in place.
- One end-to-end sync proven per pattern in use, including a dead-letter drill.
- The secret scan and tenant-scoping tests are green.