Sample deliverable · Delivery and governance
Sample architecture decision record (ADR)
How we record a significant technical decision: context, options considered, the decision and its consequences.
Sample / template. Fictional systems, names and dates that show the format and depth of what you receive. Not a client deliverable.
ADR-007 (fictional) · Status: Accepted · Deciders: customer platform lead, customer security lead, SRASH lead engineer · Stored in the customer's repository under /docs/adr/
Title
Use pgvector in the existing Aurora PostgreSQL cluster for the policy assistant's retrieval, rather than a dedicated vector database.
Context
The assistant needs to search about 400,000 document chunks with permission filters taken from the document management system. The team already runs Aurora PostgreSQL with backups, monitoring and access controls in place, and has no experience operating a separate vector store.
Decision drivers
- Permission filtering must happen in the same query as the similarity search
- Measured retrieval quality on the evaluation set
- Operational load on a small platform team
- Data must stay inside the existing AWS account
Options considered
| Option | For | Against |
|---|---|---|
| pgvector in Aurora PostgreSQL | Existing operations, backups and IAM; SQL filters with joins to permissions | Index tuning needed above a few million vectors |
| Managed vector database (SaaS) | Purpose-built, scales further | New vendor review, data leaves the account, separate permission sync |
| OpenSearch k-NN | Hybrid keyword and vector search built in | New cluster to run; team unfamiliar with it |
Decision
Use pgvector with an HNSW index in the existing cluster. Evaluation run on the 200-question set scored within two points of the managed option, with permission filtering in a single query.
Consequences
- No new vendor or security review is needed
- Revisit if the corpus grows past 5 million chunks or p95 query latency exceeds 300 ms (alert configured)
- Index build time added to the deployment runbook
More delivery and governance samples
Sample statement of work outline
The sections, acceptance criteria and change control in a typical fixed-fee statement of work. Fees are stated in each real SOW, not here.Sample deliverableSample weekly status report
The one-page report you receive every week: status, progress, risks, decisions needed and next steps.Sample deliverableSample RAID log: risks, assumptions, issues and dependencies
The register we keep from day one and review with you weekly, with owners, ratings and mitigations.Want to see how this would look for your project?
On the free 30-minute review a senior engineer will walk you through how we would plan, report and govern your work.