/tender-nfr — tender / NFR response drafting

Request: $ARGUMENTS

Draft answers from the tender libraries (no commands — approach + measurable evidence):

• db → reference/Database-Tender-NFR-Responses.md (ISO 25010)
• k8s → reference/Kubernetes-Platform-Tender-Response.md (component catalogue, DevSecOps, SSO matrix, standards, Requirement Traceability Matrix)

Use the three-move pattern for every requirement: ① restate it → ② state the concrete mechanism → ③ state the measurable target + evidence artefact. Rules: keep availability honest (99.9–99.99 %, never reflexive five-nines); scope SLAs precisely; include the open-licence column for k8s bids (Vault→OpenBao, MinIO→SeaweedFS, Redis→Valkey); lead with the Requirement Traceability Matrix for World Bank grade; and flag that a World Bank IS bid is ~half non-technical (methodology, CVs, SLA, financials).