A document connector is ready when its supported lifecycle behaviour is verified, not merely when it imports one file. Acceptance should cover identity, fidelity, access, updates, removals, and recovery under the intended deployment.
Acceptance is a scoped evidence decision
A connector acceptance checklist records requirements and test evidence for a defined source system, account configuration, resource set, and version. It should distinguish supported behaviour from untested assumptions and known limitations.
For a proposed checklist, include authentication scope, stable resource identity, pagination or changes contract, text and structure extraction, permissions, authority metadata, deletion, rename, throttling, and checkpoint recovery.
Do not turn the checklist into a series of unchecked yes boxes. Each consequential requirement needs a fixture, observable result, owner, and disposition. Exceptions should explain the affected scope and containment.
Run a fictional acceptance trace
Create a general guide, a restricted policy, a table document, and a resource with an attachment. Import them, edit one, rename another, revoke access, remove a source, interrupt a page fetch, and restore the connector.
The final active corpus should match the approved current state. Restricted markers must not enter unauthorised context, deleted passages must not reappear, and unchanged resources should preserve their identities.
| Acceptance area | Concrete evidence |
|---|---|
| Source scope | Correct account, collections, and credentials |
| Content fidelity | Reviewed text and structural fixtures |
| Resource lifecycle | Edit, rename, move, and delete trace |
| Access | Positive, negative, and revocation tests |
| Recovery | Checkpoint, retry, outage, and reconciliation results |
Inspect search, previews, citations, caches, and logs where the connector affects them. A correct index row alone cannot establish the whole user-facing path.
Record the decision and maintenance boundary
The acceptance note should state what is approved, what remains limited, who owns operation, and which changes require retesting. Keep the deployable configuration and relevant documentation references with the evidence.
A comprehensive checklist takes time, so start with material invariants and realistic fixtures. Reuse the trace for connector upgrades and new accounts, while validating local permissions and source settings. Prior acceptance does not automatically transfer to every client configuration.
This acceptance design is proposed. The voice integration case study describes related retrieval and backend work without claiming this connector suite. Pair it with connector-update testing.
Have the receiving operator execute a representative recovery task using the acceptance artifacts alone. Missing access or unclear ownership should become an explicit readiness issue.
Connector acceptance FAQ
Does importing one sample prove readiness?
No. It establishes only that one path worked under one condition.
Can exceptions be accepted?
Use the accountable decision process with concrete limitations, containment, and owners rather than silently marking them passed.
What should trigger re-acceptance?
Material changes to source APIs, credentials, scopes, parsing, permissions, indexing, storage, or recovery behaviour.