Team collaborating at a table with laptop and notes — reviewing a handed-off system.

You received a RAG solution bundle: Lambda sources, scripts, maybe S3 or vector exports, and a reading order for docs. Before you promise a go-live date, walk through a short acceptance checklist. The tables below list typical questions to ask; rename regions, accounts, and services to match yours.

Acceptance walkthrough (activity)

Simplified activity: read docs and limitations, validate environment and data assumptions, then operational readiness before pilot.

Documentation and scope

Step Question
Read order Did you follow the package’s recommended doc sequence (architecture → environment → pipeline → limitations)?
Scope Is the bundle explicitly scoped (for example internal policy / handbook content only)?
Limitations doc Did you read the limitations / known issues file end to end?

Skipping the limitations page is the fastest path to surprise.

Environment and security

Step Question
Target account Was this system ever deployed in your AWS account, or only described? If not, plan IAM, VPC, and quotas from scratch.
Secrets Where do API keys and tokens live (Parameter Store, Secrets Manager)? Who can read them?
Data residency Do chunk text and prompts stay in approved regions and vendors?

Data and reproducibility

Step Question
Restore scripts If bulk download/upload scripts for object storage or vectors are included, were they validated in your environment? Treat unverified scripts as reference only.
Checksums / counts After any restore, do object counts and index stats look plausible?
Source mix Do you understand which folders map to which chunk prefixes (structured PDFs vs messy Office trees)?

Operational readiness

Step Question
Re-ingest Who runs embedding batches after policy updates, and how often?
Monitoring What logs and alarms exist for Lambdas, queues, and throttles?
Judge / quality data If an async judge exists, who reviews low scores and on what cadence?

Closing

A handoff package is a starting kit, not a remote control for production. Use a checklist to turn folders and scripts into owned infrastructure: documented, tested in your account, and aligned with internal risk rules.