Handle document changes, ACL revocation and deletion across a retrieval pipeline.
AI, machine-learning and data practitioners.
Your approach: Use prose or diagrams to explain data and model behavior, evaluation evidence and lifecycle controls requested in the question.
Design an internal question-answering product over enterprise documents. Focus on the lifecycle from ingestion to a cited answer, especially when permission or source content changes. Explain a useful degraded response when freshness or authorization cannot be established.
Declare the p95 delay from an accepted source update to retrieval reflecting it under normal operation.
Required target: ≤ 300 seconds
Declare the maximum intended stale-access window and specify where authorization is rechecked.
Required target: ≤ 60 seconds
Track removal across source cache, chunk store, embeddings and answer caches; describe backup retention separately.
Source text cannot override system instructions or authorization; unsupported answers need an explicit abstention or uncertainty path.
Show ingestion, versioned chunks/indexes, retrieval, authorization checks and cited answer assembly.
Trace an ACL revoke and a deleted document during an in-flight question; explain cache invalidation and reconciliation.
Define test slices, relevance/grounding/leakage measures, a baseline and launch thresholds.
Size ingest/query load, estimate per-answer cost assumptions and choose a degraded behavior when dependencies fail.