Skip to content
WorkspaceLet's simulate→
← Resource library
PRIVATE CONNECTOR FIELD GUIDE / 6 min

Connect the source.
Keep the boundary.

A source-onboarding checklist for custody, fields, budgets and recovery.

6 practical chaptersWorked exampleReview checklist
CORTEXSIM / VISUAL FIELD NOTESSELECT A COMPONENT
CUSTOMER DATA / CREDENTIAL CUSTODYREVIEWED INPUTCONNECTOR-INITIATED CHANNEL01Private source02Connector03Review boundary04Pinned input05Business twin
Private source

Start with the exact approved view, stream, endpoint or journal.

GUIDE / CORTEXSIM

Source-local custody and controlled ingestion. Select a component to explore its role in the evaluation.

CHAPTER 01

Define the source purpose

Specify the exact source, owner, data classification and intended business workflow. A generic connector is not permission to scan arbitrary tables or endpoints.

Start with a concrete use: which business question needs which fields from which source? Record the owner, approved destination, data classification and retention assumptions. Choose the smallest source scope that supports the question. Credentials are an access mechanism, not permission to expand collection beyond that purpose.

DESIGN TAKEAWAYS
  • Choose a supported adapter and explicit destination.
  • Use the minimum permitted fields and row scope.
  • Keep source credentials in the customer data plane.
CHAPTER 02

Review the ingestion boundary

Agree pseudonymization, allowed addresses, field mappings and deadlines before enabling collection. Record the source schema and view fingerprints so drift becomes visible.

Review the shape and meaning of the data as well as its transport. Identify business time, entity identifiers, ordering and any missing values. A syntactically valid batch can still map the wrong business semantics. Keep schema and mapping identities so later changes can be detected and reviewed.

EXPLORE THE METHOD

Source-local custody and controlled ingestion

Private source

Start with the exact approved view, stream, endpoint or journal.

DESIGN TAKEAWAYS
  • Preserve source identity and business time.
  • Bound rows, bytes, pages and request duration.
  • Review source changes rather than silently broadening collection.
CHAPTER 03

Rehearse interrupted delivery

A source connection needs reliable acknowledgment and recovery behavior. Test lost acknowledgment, restarts and changed source generations against the declared connector profile.

A connector may deliver a batch successfully but lose the acknowledgment. Recovery needs to distinguish that case from a batch that never arrived. Rehearse interruption using the exact supported profile, retaining its input identity, receipt and checkpoint behavior rather than assuming every source has the same replay semantics.

ILLUSTRATIVE WORKED EXAMPLE

What should a reviewed claims source contribute to a model?

REHEARSE

Select the permitted case identifiers, status transitions and business timestamps from an approved source view. Record mappings and input references, then test an interrupted batch against the profile contract.

REVIEW

Review whether the admitted records support the intended workflow. A successful read does not prove complete claim coverage or native claims-platform integration.

Synthetic evaluation illustration. No customer result or benchmark is claimed.
DESIGN TAKEAWAYS
  • Inspect outbox and checkpoint behavior.
  • Verify the acknowledged input digest.
  • Retain receipt and source snapshot provenance.
CHAPTER 04

Choose a profile, then qualify the source

The implemented source profile catalog includes event journals, SQLite views, PostgreSQL views, PostgreSQL CDC, Redis streams, bounded REST reads and organizational MCP reads. Each profile has its own operating contract.

PostgreSQL CDC is an isolated lab profile. A generic adapter does not establish native compatibility with a vendor application, customer networking or production change capture. Qualify the exact source, credentials, schema and deployment before broadening its use.

Review the boundary before collection

BoundaryQuestion to resolveEvidence to retain
Source scopeWhich exact records and fields are permitted?Reviewed source purpose and mapping.
Credential custodyWhere are credentials held and who rotates them?Owner and custody references, without secrets.
Interrupted deliveryHow does this profile recognize an already admitted batch?Input identity, receipt and checkpoint evidence.
DESIGN TAKEAWAYS
  • Record the adapter and source versions.
  • Keep credentials out of prompts and model output.
  • Separate a successful lab connection from production acceptance.
CHAPTER 05

Keep lineage through change

Data becomes useful evidence when a reviewer can identify where it came from and how it entered the model. Retain source references, snapshot identity, reviewed mappings and the relevant collection limits alongside the model.

Treat a changed source generation, schema or destination as a review event. Do not silently reinterpret old records through a new mapping. Preserve earlier evidence so a later discrepancy can be traced to the source, mapping or model rather than guessed at.

WHAT TRAVELS WITH THE RESULT
01Input references
02Model + scenario
03Complete outcomes
04Review + limits

Keep the evidence and its conditions together. A later success does not erase an earlier failure or broaden the original scope.

DESIGN TAKEAWAYS
  • Retain source and mapping identities.
  • Explain gaps, duplicates and ordering assumptions.
  • Review collection changes with the accountable owner.
CHAPTER 06

Prepare a source onboarding brief

Bring the source owner and platform team together around the smallest useful connection. Agree the permitted data, purpose, profile, failure behavior and evidence to retain before connecting a sensitive source.

Use synthetic or appropriately approved inputs to rehearse the contract. Keep the acceptance decision separate from the checklist: selecting an item here does not register a connector or grant access to a system.

Review preparation

0 / 6 prepared
Selections stay in this page session. They do not approve an evaluation, grant permissions or establish production readiness.
DESIGN TAKEAWAYS
  • Name the source and credential owner.
  • Define collection and recovery limits.
  • Record the remaining customer qualification work.
TURN THE GUIDE INTO A PLAN

Bring the question.
Build the evidence.

Define one meaningful decision, the conditions it depends on and the evidence your reviewers need.

Create your evaluation brief ↗