A document can arrive before the attachment that supplies its conditions or supporting table. Track the relationship and readiness explicitly so the assistant does not answer from an incomplete package as if all evidence were present.
Attachments are dependent resources
An attachment can contain essential evidence, optional detail, or unrelated material. Its identity, version, permissions, and processing state may differ from the main document. The connector needs to preserve those relationships.
For a proposed model, record parent reference, attachment identity, required-versus-optional role, version, audience, and import state. Define when the parent is eligible for definitive answers and how missing dependencies are disclosed.
Do not assume every attachment inherits the parent’s permissions or approval status. Apply the source’s documented policy and verify any derived relationship before retrieval.
Test a fictional service-policy package
The main policy says eligibility is defined in an attached table. The policy arrives at 09:00, but the table becomes available at 09:10. An answer generated in the gap must not invent the missing eligibility detail.
After the attachment imports, the evaluation checks that the table’s labels, units, and exceptions are preserved. A later replacement attachment should update the package without leaving both versions equally authoritative.
| Dependency condition | Expected behaviour |
|---|---|
| Required attachment absent | Incomplete-evidence status or qualified answer |
| Optional appendix absent | Continue only within supported scope |
| Attachment permission narrower | No unauthorised context expansion |
| Attachment version replaced | Current relationship and authority applied |
| Attachment parsing fails | Visible failure, not fabricated summary |
Replay the arrival sequence out of order and repeat events. Inspect active passages, package readiness, previews, and cached answers before and after completion.
Make later evidence trigger the right work
An attachment arrival may require re-evaluating the parent’s readiness, linked context, and previously unanswered questions. It does not necessarily require reprocessing every unchanged source in the collection.
Dependency tracking adds state and can delay availability. That tradeoff matters when the missing artifact changes the answer. Keep low-value optional attachments from blocking unrelated supported claims, while making material gaps visible to users and content owners.
This ingestion design is proposed. The voice integration case study describes related knowledge work without claiming this connector. Pair it with tables and explanations.
Late attachment FAQ
Should the parent always be hidden until every attachment arrives?
Use the approved dependency policy and the claims the available evidence can support.
Can parent access automatically authorise attachment access?
Only when the source’s actual permission semantics establish that relationship.
What should a test inspect?
Verify arrival order, readiness, permissions, version changes, extraction failure, and the meaning of answers produced during the gap.