@raishin/vanguard-frontier-agentic 3.19.0 → 3.20.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (459) hide show
  1. package/.claude-plugin/marketplace.json +2 -2
  2. package/.claude-plugin/plugin.json +8 -1
  3. package/.cursor-plugin/plugin.json +8 -1
  4. package/.github/plugin/marketplace.json +1 -1
  5. package/README.md +21 -21
  6. package/agents/AGENTS.md +4 -4
  7. package/agents/README.md +7 -7
  8. package/agents/alibaba/alibaba-tablestore-architect-agent/AGENT.md +54 -0
  9. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/claude-code.agent.md +37 -0
  10. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/codex.toml +11 -0
  11. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/copilot.agent.md +43 -0
  12. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/cursor.agent.md +38 -0
  13. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/gemini.agent.md +39 -0
  14. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-cli.agent.json +5 -0
  15. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-ide.agent.md +37 -0
  16. package/agents/alibaba/alibaba-tablestore-architect-agent/metadata.json +39 -0
  17. package/agents/aws/aws-dynamodb-patterns-agent/AGENT.md +53 -0
  18. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/claude-code.agent.md +36 -0
  19. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/codex.toml +23 -0
  20. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/copilot.agent.md +42 -0
  21. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/cursor.agent.md +38 -0
  22. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/gemini.agent.md +38 -0
  23. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-cli.agent.json +5 -0
  24. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-ide.agent.md +36 -0
  25. package/agents/aws/aws-dynamodb-patterns-agent/metadata.json +39 -0
  26. package/agents/azure/azure-cosmosdb-application-developer-agent/metadata.json +4 -0
  27. package/agents/azure/azure-cosmosdb-pattern-agent/AGENT.md +53 -0
  28. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/claude-code.agent.md +36 -0
  29. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/codex.toml +23 -0
  30. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/copilot.agent.md +42 -0
  31. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/cursor.agent.md +37 -0
  32. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/gemini.agent.md +38 -0
  33. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
  34. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
  35. package/agents/azure/azure-cosmosdb-pattern-agent/metadata.json +38 -0
  36. package/agents/gcp/gcp-bigtable-architect-agent/AGENT.md +54 -0
  37. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/claude-code.agent.md +37 -0
  38. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/codex.toml +11 -0
  39. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/copilot.agent.md +43 -0
  40. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/cursor.agent.md +38 -0
  41. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/gemini.agent.md +39 -0
  42. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-cli.agent.json +5 -0
  43. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-ide.agent.md +37 -0
  44. package/agents/gcp/gcp-bigtable-architect-agent/metadata.json +39 -0
  45. package/agents/huawei/huawei-geminidb-architect-agent/AGENT.md +54 -0
  46. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/claude-code.agent.md +37 -0
  47. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/codex.toml +11 -0
  48. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/copilot.agent.md +43 -0
  49. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/cursor.agent.md +38 -0
  50. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/gemini.agent.md +39 -0
  51. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-cli.agent.json +5 -0
  52. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-ide.agent.md +37 -0
  53. package/agents/huawei/huawei-geminidb-architect-agent/metadata.json +38 -0
  54. package/agents/oci/oci-nosql-database-architect-agent/AGENT.md +54 -0
  55. package/agents/oci/oci-nosql-database-architect-agent/harnesses/claude-code.agent.md +37 -0
  56. package/agents/oci/oci-nosql-database-architect-agent/harnesses/codex.toml +11 -0
  57. package/agents/oci/oci-nosql-database-architect-agent/harnesses/copilot.agent.md +43 -0
  58. package/agents/oci/oci-nosql-database-architect-agent/harnesses/cursor.agent.md +39 -0
  59. package/agents/oci/oci-nosql-database-architect-agent/harnesses/gemini.agent.md +39 -0
  60. package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-cli.agent.json +5 -0
  61. package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-ide.agent.md +37 -0
  62. package/agents/oci/oci-nosql-database-architect-agent/metadata.json +39 -0
  63. package/agents/oci/oci-nosql-pattern-agent/AGENT.md +53 -0
  64. package/agents/oci/oci-nosql-pattern-agent/harnesses/claude-code.agent.md +36 -0
  65. package/agents/oci/oci-nosql-pattern-agent/harnesses/codex.toml +23 -0
  66. package/agents/oci/oci-nosql-pattern-agent/harnesses/copilot.agent.md +42 -0
  67. package/agents/oci/oci-nosql-pattern-agent/harnesses/cursor.agent.md +38 -0
  68. package/agents/oci/oci-nosql-pattern-agent/harnesses/gemini.agent.md +38 -0
  69. package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
  70. package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
  71. package/agents/oci/oci-nosql-pattern-agent/metadata.json +38 -0
  72. package/catalog/agents.json +204 -1
  73. package/catalog/asset-integrity.json +601 -61
  74. package/catalog/install-roles.json +19 -1
  75. package/catalog/model-assignments.json +231 -0
  76. package/catalog/skill-manifest.json +1603 -56
  77. package/catalog/skills.json +314 -14
  78. package/package.json +7 -2
  79. package/plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json +1 -1
  80. package/powers/vanguard-alibaba/POWER.md +1 -1
  81. package/powers/vanguard-aws/POWER.md +1 -1
  82. package/powers/vanguard-azure/POWER.md +1 -1
  83. package/powers/vanguard-gcp/POWER.md +1 -1
  84. package/powers/vanguard-huawei/POWER.md +1 -1
  85. package/powers/vanguard-oci/POWER.md +1 -1
  86. package/skills/alibaba/README.md +2 -1
  87. package/skills/alibaba/alibaba-maestro/SKILL.md +2 -1
  88. package/skills/alibaba/alibaba-tablestore-architect/SKILL.md +69 -0
  89. package/skills/alibaba/alibaba-tablestore-architect/metadata.json +28 -0
  90. package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/live.md +110 -0
  91. package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/offline.md +119 -0
  92. package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit.md +22 -0
  93. package/skills/alibaba/alibaba-tablestore-architect/references/evidence-ledger.md +87 -0
  94. package/skills/alibaba/alibaba-tablestore-architect/references/operations.md +190 -0
  95. package/skills/alibaba/alibaba-tablestore-architect/references/tablestore-design-guide.md +159 -0
  96. package/skills/aws/aws-documentdb-architect/SKILL.md +43 -0
  97. package/skills/aws/aws-documentdb-architect/metadata.json +26 -0
  98. package/skills/aws/aws-documentdb-architect/references/commands/audit/live.md +135 -0
  99. package/skills/aws/aws-documentdb-architect/references/commands/audit/offline.md +127 -0
  100. package/skills/aws/aws-documentdb-architect/references/commands/audit.md +23 -0
  101. package/skills/aws/aws-documentdb-architect/references/evidence-ledger.md +52 -0
  102. package/skills/aws/aws-documentdb-architect/references/official-sources.md +15 -0
  103. package/skills/aws/aws-documentdb-architect/references/operations.md +165 -0
  104. package/skills/aws/aws-documentdb-architect/references/safety-checklist.md +22 -0
  105. package/skills/aws/aws-documentdb-architect/references/workflow-and-output.md +22 -0
  106. package/skills/aws/aws-dynamodb-data-modeling-performance-review/SKILL.md +5 -3
  107. package/skills/aws/aws-dynamodb-data-modeling-performance-review/metadata.json +7 -3
  108. package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/consistency-indexing-replication.md +103 -0
  109. package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/evidence-ledger.md +38 -0
  110. package/skills/aws/aws-dynamodb-patterns/CHANGELOG.md +87 -0
  111. package/skills/aws/aws-dynamodb-patterns/README.md +132 -0
  112. package/skills/aws/aws-dynamodb-patterns/SKILL.md +82 -0
  113. package/skills/aws/aws-dynamodb-patterns/assets/bedrock-embedding-input.json +6 -0
  114. package/skills/aws/aws-dynamodb-patterns/assets/content-review.json +6 -0
  115. package/skills/aws/aws-dynamodb-patterns/assets/create-table-with-lsi.json +41 -0
  116. package/skills/aws/aws-dynamodb-patterns/assets/create-table.json +27 -0
  117. package/skills/aws/aws-dynamodb-patterns/assets/create-table.sh +37 -0
  118. package/skills/aws/aws-dynamodb-patterns/assets/embedding-flow.py +89 -0
  119. package/skills/aws/aws-dynamodb-patterns/assets/query-input.json +13 -0
  120. package/skills/aws/aws-dynamodb-patterns/assets/query-pages.mjs +54 -0
  121. package/skills/aws/aws-dynamodb-patterns/assets/stream-read-policy.json +11 -0
  122. package/skills/aws/aws-dynamodb-patterns/assets/table-index-read-policy.json +20 -0
  123. package/skills/aws/aws-dynamodb-patterns/assets/table-resource-policy.json +22 -0
  124. package/skills/aws/aws-dynamodb-patterns/assets/table.cfn.yaml +55 -0
  125. package/skills/aws/aws-dynamodb-patterns/assets/typed-vector-item.json +15 -0
  126. package/skills/aws/aws-dynamodb-patterns/assets/vector-create-table.json +23 -0
  127. package/skills/aws/aws-dynamodb-patterns/assets/vector-search-policy.json +11 -0
  128. package/skills/aws/aws-dynamodb-patterns/assets/vector-search.json +10 -0
  129. package/skills/aws/aws-dynamodb-patterns/assets/vector-table.cfn.yaml +41 -0
  130. package/skills/aws/aws-dynamodb-patterns/evals/audit.test.py +87 -0
  131. package/skills/aws/aws-dynamodb-patterns/evals/backup-restore.test.py +163 -0
  132. package/skills/aws/aws-dynamodb-patterns/evals/commands.test.py +185 -0
  133. package/skills/aws/aws-dynamodb-patterns/evals/create-table.test.py +99 -0
  134. package/skills/aws/aws-dynamodb-patterns/evals/data-vectors-maintenance.test.py +201 -0
  135. package/skills/aws/aws-dynamodb-patterns/evals/embedding-commands.test.py +162 -0
  136. package/skills/aws/aws-dynamodb-patterns/evals/embedding-flow.test.py +167 -0
  137. package/skills/aws/aws-dynamodb-patterns/evals/eval.md +328 -0
  138. package/skills/aws/aws-dynamodb-patterns/evals/evals.json +185 -0
  139. package/skills/aws/aws-dynamodb-patterns/evals/modes.test.py +195 -0
  140. package/skills/aws/aws-dynamodb-patterns/evals/operations.test.py +288 -0
  141. package/skills/aws/aws-dynamodb-patterns/evals/query-pages.test.mjs +156 -0
  142. package/skills/aws/aws-dynamodb-patterns/evals/readme-and-loading.test.py +69 -0
  143. package/skills/aws/aws-dynamodb-patterns/evals/verify.py +166 -0
  144. package/skills/aws/aws-dynamodb-patterns/metadata.json +28 -0
  145. package/skills/aws/aws-dynamodb-patterns/references/commands/README.md +32 -0
  146. package/skills/aws/aws-dynamodb-patterns/references/commands/audit/live.md +64 -0
  147. package/skills/aws/aws-dynamodb-patterns/references/commands/audit/offline.md +28 -0
  148. package/skills/aws/aws-dynamodb-patterns/references/commands/audit.md +65 -0
  149. package/skills/aws/aws-dynamodb-patterns/references/commands/aws-cli.md +206 -0
  150. package/skills/aws/aws-dynamodb-patterns/references/commands/backup/on-demand.md +36 -0
  151. package/skills/aws/aws-dynamodb-patterns/references/commands/backup/pitr.md +41 -0
  152. package/skills/aws/aws-dynamodb-patterns/references/commands/backup.md +27 -0
  153. package/skills/aws/aws-dynamodb-patterns/references/commands/design.md +47 -0
  154. package/skills/aws/aws-dynamodb-patterns/references/commands/embedding.md +200 -0
  155. package/skills/aws/aws-dynamodb-patterns/references/commands/feature-plan.md +56 -0
  156. package/skills/aws/aws-dynamodb-patterns/references/commands/help.md +28 -0
  157. package/skills/aws/aws-dynamodb-patterns/references/commands/performance-test.md +95 -0
  158. package/skills/aws/aws-dynamodb-patterns/references/commands/recovery-target.md +47 -0
  159. package/skills/aws/aws-dynamodb-patterns/references/commands/refactor.md +82 -0
  160. package/skills/aws/aws-dynamodb-patterns/references/commands/restore/on-demand.md +32 -0
  161. package/skills/aws/aws-dynamodb-patterns/references/commands/restore/pitr.md +42 -0
  162. package/skills/aws/aws-dynamodb-patterns/references/commands/restore.md +76 -0
  163. package/skills/aws/aws-dynamodb-patterns/references/commands/select.md +22 -0
  164. package/skills/aws/aws-dynamodb-patterns/references/data-types-and-vectors.md +175 -0
  165. package/skills/aws/aws-dynamodb-patterns/references/embedding-integrations.md +237 -0
  166. package/skills/aws/aws-dynamodb-patterns/references/encryption.md +156 -0
  167. package/skills/aws/aws-dynamodb-patterns/references/evidence-index.md +116 -0
  168. package/skills/aws/aws-dynamodb-patterns/references/evidence-ledger.md +373 -0
  169. package/skills/aws/aws-dynamodb-patterns/references/iam-and-access.md +173 -0
  170. package/skills/aws/aws-dynamodb-patterns/references/language-adapters.md +251 -0
  171. package/skills/aws/aws-dynamodb-patterns/references/lsi-vs-gsi.md +116 -0
  172. package/skills/aws/aws-dynamodb-patterns/references/maintenance.md +56 -0
  173. package/skills/aws/aws-dynamodb-patterns/references/modeling.md +131 -0
  174. package/skills/aws/aws-dynamodb-patterns/references/monitoring.md +137 -0
  175. package/skills/aws/aws-dynamodb-patterns/references/official-sources.md +34 -0
  176. package/skills/aws/aws-dynamodb-patterns/references/operations.md +130 -0
  177. package/skills/aws/aws-dynamodb-patterns/references/provisioning.md +110 -0
  178. package/skills/aws/aws-dynamodb-patterns/references/recovery-and-replicas.md +148 -0
  179. package/skills/aws/aws-dynamodb-patterns/references/runtime-contract.md +140 -0
  180. package/skills/aws/aws-dynamodb-patterns/references/safety-checklist.md +35 -0
  181. package/skills/aws/aws-dynamodb-patterns/references/sources.md +170 -0
  182. package/skills/aws/aws-dynamodb-patterns/references/streams-and-dax.md +160 -0
  183. package/skills/aws/aws-dynamodb-patterns/references/workflow-and-output.md +34 -0
  184. package/skills/aws/aws-dynamodb-patterns/references/workflow.md +133 -0
  185. package/skills/aws/aws-dynamodb-patterns/scripts/review_due.py +61 -0
  186. package/skills/aws/aws-dynamodb-patterns/scripts/select_mode.py +127 -0
  187. package/skills/aws/aws-keyspaces-architect/SKILL.md +43 -0
  188. package/skills/aws/aws-keyspaces-architect/metadata.json +26 -0
  189. package/skills/aws/aws-keyspaces-architect/references/commands/audit/live.md +118 -0
  190. package/skills/aws/aws-keyspaces-architect/references/commands/audit/offline.md +125 -0
  191. package/skills/aws/aws-keyspaces-architect/references/commands/audit.md +22 -0
  192. package/skills/aws/aws-keyspaces-architect/references/evidence-ledger.md +49 -0
  193. package/skills/aws/aws-keyspaces-architect/references/official-sources.md +15 -0
  194. package/skills/aws/aws-keyspaces-architect/references/operations.md +154 -0
  195. package/skills/aws/aws-keyspaces-architect/references/safety-checklist.md +22 -0
  196. package/skills/aws/aws-keyspaces-architect/references/workflow-and-output.md +22 -0
  197. package/skills/aws/aws-maestro/SKILL.md +1 -1
  198. package/skills/aws/aws-maestro/metadata.json +1 -1
  199. package/skills/aws/aws-maestro/references/workflow-and-output.md +1 -0
  200. package/skills/azure/azure-cosmosdb-application-developer/SKILL.md +4 -2
  201. package/skills/azure/azure-cosmosdb-application-developer/metadata.json +1 -1
  202. package/skills/azure/azure-cosmosdb-pattern/CHANGELOG.md +10 -0
  203. package/skills/azure/azure-cosmosdb-pattern/README.md +102 -0
  204. package/skills/azure/azure-cosmosdb-pattern/SKILL.md +69 -0
  205. package/skills/azure/azure-cosmosdb-pattern/assets/account.arm.json +59 -0
  206. package/skills/azure/azure-cosmosdb-pattern/assets/content-review.json +9 -0
  207. package/skills/azure/azure-cosmosdb-pattern/assets/indexing-policy.json +7 -0
  208. package/skills/azure/azure-cosmosdb-pattern/assets/order.json +10 -0
  209. package/skills/azure/azure-cosmosdb-pattern/assets/provision.sh +32 -0
  210. package/skills/azure/azure-cosmosdb-pattern/assets/runtime.mjs +99 -0
  211. package/skills/azure/azure-cosmosdb-pattern/assets/vector-indexing-policy.json +7 -0
  212. package/skills/azure/azure-cosmosdb-pattern/assets/vector-policy.json +3 -0
  213. package/skills/azure/azure-cosmosdb-pattern/evals/eval.md +32 -0
  214. package/skills/azure/azure-cosmosdb-pattern/evals/fixtures/recovery-continuous.json +28 -0
  215. package/skills/azure/azure-cosmosdb-pattern/evals/prompts.json +24 -0
  216. package/skills/azure/azure-cosmosdb-pattern/evals/report.md +54 -0
  217. package/skills/azure/azure-cosmosdb-pattern/evals/runtime.test.mjs +146 -0
  218. package/skills/azure/azure-cosmosdb-pattern/evals/source-evidence.json +28 -0
  219. package/skills/azure/azure-cosmosdb-pattern/evals/test_package.py +355 -0
  220. package/skills/azure/azure-cosmosdb-pattern/metadata.json +25 -0
  221. package/skills/azure/azure-cosmosdb-pattern/references/access-control.md +42 -0
  222. package/skills/azure/azure-cosmosdb-pattern/references/change-feed-and-integrations.md +31 -0
  223. package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/live.md +17 -0
  224. package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/offline.md +15 -0
  225. package/skills/azure/azure-cosmosdb-pattern/references/commands/audit.md +8 -0
  226. package/skills/azure/azure-cosmosdb-pattern/references/commands/azure-cli.md +39 -0
  227. package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/continuous.md +30 -0
  228. package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/periodic.md +28 -0
  229. package/skills/azure/azure-cosmosdb-pattern/references/commands/backup.md +11 -0
  230. package/skills/azure/azure-cosmosdb-pattern/references/commands/design.md +13 -0
  231. package/skills/azure/azure-cosmosdb-pattern/references/commands/feature-plan.md +18 -0
  232. package/skills/azure/azure-cosmosdb-pattern/references/commands/help.md +13 -0
  233. package/skills/azure/azure-cosmosdb-pattern/references/commands/performance-test.md +24 -0
  234. package/skills/azure/azure-cosmosdb-pattern/references/commands/recovery-target.md +30 -0
  235. package/skills/azure/azure-cosmosdb-pattern/references/commands/refactor.md +14 -0
  236. package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-deleted-resource.md +55 -0
  237. package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-new-account.md +50 -0
  238. package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/periodic-support.md +27 -0
  239. package/skills/azure/azure-cosmosdb-pattern/references/commands/restore.md +13 -0
  240. package/skills/azure/azure-cosmosdb-pattern/references/commands/select.md +11 -0
  241. package/skills/azure/azure-cosmosdb-pattern/references/data-types-and-vectors.md +51 -0
  242. package/skills/azure/azure-cosmosdb-pattern/references/embedding-integrations.md +56 -0
  243. package/skills/azure/azure-cosmosdb-pattern/references/encryption.md +53 -0
  244. package/skills/azure/azure-cosmosdb-pattern/references/evidence-index.md +72 -0
  245. package/skills/azure/azure-cosmosdb-pattern/references/evidence-ledger.md +174 -0
  246. package/skills/azure/azure-cosmosdb-pattern/references/indexing-and-capacity.md +37 -0
  247. package/skills/azure/azure-cosmosdb-pattern/references/language-adapters.md +112 -0
  248. package/skills/azure/azure-cosmosdb-pattern/references/maintenance.md +19 -0
  249. package/skills/azure/azure-cosmosdb-pattern/references/modeling.md +44 -0
  250. package/skills/azure/azure-cosmosdb-pattern/references/monitoring.md +23 -0
  251. package/skills/azure/azure-cosmosdb-pattern/references/provisioning.md +61 -0
  252. package/skills/azure/azure-cosmosdb-pattern/references/recovery.md +31 -0
  253. package/skills/azure/azure-cosmosdb-pattern/references/replication.md +22 -0
  254. package/skills/azure/azure-cosmosdb-pattern/references/runtime-contract.md +43 -0
  255. package/skills/azure/azure-cosmosdb-pattern/references/sources.md +61 -0
  256. package/skills/azure/azure-cosmosdb-pattern/references/workflow.md +18 -0
  257. package/skills/azure/azure-cosmosdb-pattern/scripts/recovery_guard.py +96 -0
  258. package/skills/azure/azure-cosmosdb-pattern/scripts/review_due.py +26 -0
  259. package/skills/azure/azure-cosmosdb-pattern/scripts/select_mode.py +108 -0
  260. package/skills/azure/azure-cosmosdb-pattern/scripts/validate_assets.py +53 -0
  261. package/skills/azure/azure-cosmosdb-platform-operator/SKILL.md +6 -2
  262. package/skills/azure/azure-cosmosdb-platform-operator/metadata.json +6 -3
  263. package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/live.md +180 -0
  264. package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/offline.md +160 -0
  265. package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit.md +26 -0
  266. package/skills/azure/azure-cosmosdb-platform-operator/references/consistency-capacity-security.md +136 -0
  267. package/skills/azure/azure-cosmosdb-platform-operator/references/cosmosdb-platform-operations.md +1 -1
  268. package/skills/azure/azure-cosmosdb-platform-operator/references/evidence-ledger.md +242 -0
  269. package/skills/azure/azure-cosmosdb-platform-operator/references/operations-cassandra.md +178 -0
  270. package/skills/azure/azure-cosmosdb-platform-operator/references/operations-mongodb.md +202 -0
  271. package/skills/azure/azure-cosmosdb-platform-operator/references/operations.md +126 -0
  272. package/skills/azure/azure-maestro/SKILL.md +1 -0
  273. package/skills/gcp/README.md +2 -1
  274. package/skills/gcp/gcp-bigtable-architect/SKILL.md +71 -0
  275. package/skills/gcp/gcp-bigtable-architect/metadata.json +28 -0
  276. package/skills/gcp/gcp-bigtable-architect/references/bigtable-design-guide.md +156 -0
  277. package/skills/gcp/gcp-bigtable-architect/references/commands/audit/live.md +122 -0
  278. package/skills/gcp/gcp-bigtable-architect/references/commands/audit/offline.md +140 -0
  279. package/skills/gcp/gcp-bigtable-architect/references/commands/audit.md +21 -0
  280. package/skills/gcp/gcp-bigtable-architect/references/evidence-ledger.md +83 -0
  281. package/skills/gcp/gcp-bigtable-architect/references/operations.md +111 -0
  282. package/skills/gcp/gcp-firebase-developer/SKILL.md +6 -3
  283. package/skills/gcp/gcp-firebase-developer/metadata.json +14 -4
  284. package/skills/gcp/gcp-firebase-developer/references/commands/audit/live.md +124 -0
  285. package/skills/gcp/gcp-firebase-developer/references/commands/audit/offline.md +146 -0
  286. package/skills/gcp/gcp-firebase-developer/references/commands/audit.md +27 -0
  287. package/skills/gcp/gcp-firebase-developer/references/evidence-ledger.md +190 -0
  288. package/skills/gcp/gcp-firebase-developer/references/firestore-mongodb-operations.md +189 -0
  289. package/skills/gcp/gcp-firebase-developer/references/firestore-operations.md +202 -0
  290. package/skills/gcp/gcp-firebase-developer/references/firestore.md +122 -0
  291. package/skills/gcp/gcp-maestro/SKILL.md +2 -1
  292. package/skills/huawei/README.md +2 -1
  293. package/skills/huawei/huawei-gaussdb-rds-dba/SKILL.md +7 -4
  294. package/skills/huawei/huawei-gaussdb-rds-dba/metadata.json +12 -4
  295. package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/live.md +68 -0
  296. package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/offline.md +106 -0
  297. package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit.md +23 -0
  298. package/skills/huawei/huawei-gaussdb-rds-dba/references/dds-operations.md +135 -0
  299. package/skills/huawei/huawei-gaussdb-rds-dba/references/evidence-ledger.md +87 -0
  300. package/skills/huawei/huawei-geminidb-architect/SKILL.md +68 -0
  301. package/skills/huawei/huawei-geminidb-architect/metadata.json +26 -0
  302. package/skills/huawei/huawei-geminidb-architect/references/commands/audit/live.md +68 -0
  303. package/skills/huawei/huawei-geminidb-architect/references/commands/audit/offline.md +108 -0
  304. package/skills/huawei/huawei-geminidb-architect/references/commands/audit.md +23 -0
  305. package/skills/huawei/huawei-geminidb-architect/references/evidence-ledger.md +83 -0
  306. package/skills/huawei/huawei-geminidb-architect/references/geminidb-design-guide.md +114 -0
  307. package/skills/huawei/huawei-geminidb-architect/references/operations.md +135 -0
  308. package/skills/huawei/huawei-maestro/SKILL.md +2 -1
  309. package/skills/ionos/ionos-live-database-lifecycle-guard/SKILL.md +2 -0
  310. package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/live.md +87 -0
  311. package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/offline.md +109 -0
  312. package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit.md +27 -0
  313. package/skills/ionos/ionos-live-database-lifecycle-guard/references/evidence-ledger.md +69 -0
  314. package/skills/ionos/ionos-live-database-lifecycle-guard/references/mongodb-operations.md +220 -0
  315. package/skills/oci/README.md +6 -1
  316. package/skills/oci/oci-nosql-database-architect/SKILL.md +73 -0
  317. package/skills/oci/oci-nosql-database-architect/metadata.json +28 -0
  318. package/skills/oci/oci-nosql-database-architect/references/commands/audit/live.md +136 -0
  319. package/skills/oci/oci-nosql-database-architect/references/commands/audit/offline.md +150 -0
  320. package/skills/oci/oci-nosql-database-architect/references/commands/audit.md +28 -0
  321. package/skills/oci/oci-nosql-database-architect/references/evidence-ledger.md +96 -0
  322. package/skills/oci/oci-nosql-database-architect/references/nosql-design-guide.md +194 -0
  323. package/skills/oci/oci-nosql-database-architect/references/operations.md +194 -0
  324. package/skills/oci/oci-nosql-database-architect/references/sdk-matrix.md +43 -0
  325. package/skills/oci/oci-nosql-pattern/CHANGELOG.md +8 -0
  326. package/skills/oci/oci-nosql-pattern/README.md +81 -0
  327. package/skills/oci/oci-nosql-pattern/SKILL.md +62 -0
  328. package/skills/oci/oci-nosql-pattern/assets/content-review.json +10 -0
  329. package/skills/oci/oci-nosql-pattern/assets/create-table.sh +32 -0
  330. package/skills/oci/oci-nosql-pattern/assets/index-keys.json +11 -0
  331. package/skills/oci/oci-nosql-pattern/assets/migrator-export.json +22 -0
  332. package/skills/oci/oci-nosql-pattern/assets/migrator-import.json +29 -0
  333. package/skills/oci/oci-nosql-pattern/assets/orders.ddl +9 -0
  334. package/skills/oci/oci-nosql-pattern/assets/orders.tf +46 -0
  335. package/skills/oci/oci-nosql-pattern/assets/query-pages.mjs +33 -0
  336. package/skills/oci/oci-nosql-pattern/assets/query.json +13 -0
  337. package/skills/oci/oci-nosql-pattern/assets/query.sql +1 -0
  338. package/skills/oci/oci-nosql-pattern/assets/recovery-manifest.example.json +35 -0
  339. package/skills/oci/oci-nosql-pattern/assets/row.json +10 -0
  340. package/skills/oci/oci-nosql-pattern/assets/table-limits.json +6 -0
  341. package/skills/oci/oci-nosql-pattern/evals/cli-shapes.json +222 -0
  342. package/skills/oci/oci-nosql-pattern/evals/eval.md +26 -0
  343. package/skills/oci/oci-nosql-pattern/evals/prompts.json +89 -0
  344. package/skills/oci/oci-nosql-pattern/evals/report.md +41 -0
  345. package/skills/oci/oci-nosql-pattern/evals/test_package.py +350 -0
  346. package/skills/oci/oci-nosql-pattern/evals/test_runtime.mjs +77 -0
  347. package/skills/oci/oci-nosql-pattern/metadata.json +25 -0
  348. package/skills/oci/oci-nosql-pattern/references/access.md +29 -0
  349. package/skills/oci/oci-nosql-pattern/references/commands/audit/live.md +10 -0
  350. package/skills/oci/oci-nosql-pattern/references/commands/audit/offline.md +8 -0
  351. package/skills/oci/oci-nosql-pattern/references/commands/audit.md +6 -0
  352. package/skills/oci/oci-nosql-pattern/references/commands/backup/migrator.md +12 -0
  353. package/skills/oci/oci-nosql-pattern/references/commands/backup/sdk.md +10 -0
  354. package/skills/oci/oci-nosql-pattern/references/commands/backup.md +7 -0
  355. package/skills/oci/oci-nosql-pattern/references/commands/design.md +10 -0
  356. package/skills/oci/oci-nosql-pattern/references/commands/feature-plan.md +10 -0
  357. package/skills/oci/oci-nosql-pattern/references/commands/help.md +8 -0
  358. package/skills/oci/oci-nosql-pattern/references/commands/performance-test.md +12 -0
  359. package/skills/oci/oci-nosql-pattern/references/commands/refactor.md +9 -0
  360. package/skills/oci/oci-nosql-pattern/references/commands/restore/migrator.md +13 -0
  361. package/skills/oci/oci-nosql-pattern/references/commands/restore/sdk.md +11 -0
  362. package/skills/oci/oci-nosql-pattern/references/commands/restore.md +8 -0
  363. package/skills/oci/oci-nosql-pattern/references/commands/select.md +8 -0
  364. package/skills/oci/oci-nosql-pattern/references/embedding-integrations.md +25 -0
  365. package/skills/oci/oci-nosql-pattern/references/encryption.md +18 -0
  366. package/skills/oci/oci-nosql-pattern/references/evidence-index.md +44 -0
  367. package/skills/oci/oci-nosql-pattern/references/evidence-ledger.md +73 -0
  368. package/skills/oci/oci-nosql-pattern/references/indexes.md +19 -0
  369. package/skills/oci/oci-nosql-pattern/references/language-adapters.md +160 -0
  370. package/skills/oci/oci-nosql-pattern/references/maintenance.md +15 -0
  371. package/skills/oci/oci-nosql-pattern/references/modeling.md +26 -0
  372. package/skills/oci/oci-nosql-pattern/references/monitoring.md +21 -0
  373. package/skills/oci/oci-nosql-pattern/references/provisioning.md +44 -0
  374. package/skills/oci/oci-nosql-pattern/references/recovery-boundary.md +32 -0
  375. package/skills/oci/oci-nosql-pattern/references/replicas.md +18 -0
  376. package/skills/oci/oci-nosql-pattern/references/runtime-contract.md +23 -0
  377. package/skills/oci/oci-nosql-pattern/references/sources.md +57 -0
  378. package/skills/oci/oci-nosql-pattern/references/ttl.md +19 -0
  379. package/skills/oci/oci-nosql-pattern/references/types-and-vectors.md +27 -0
  380. package/skills/oci/oci-nosql-pattern/scripts/check_recovery.py +52 -0
  381. package/skills/oci/oci-nosql-pattern/scripts/review_due.py +32 -0
  382. package/skills/oci/oci-nosql-pattern/scripts/select_mode.py +96 -0
  383. package/skills/ovhcloud/ovhcloud-mongodb-architect/SKILL.md +43 -0
  384. package/skills/ovhcloud/ovhcloud-mongodb-architect/metadata.json +25 -0
  385. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/live.md +90 -0
  386. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/offline.md +112 -0
  387. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit.md +24 -0
  388. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/evidence-ledger.md +93 -0
  389. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/official-sources.md +15 -0
  390. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/operations.md +216 -0
  391. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/safety-checklist.md +22 -0
  392. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/workflow-and-output.md +22 -0
  393. package/skills/scaleway/scaleway-managed-mongodb-architect/SKILL.md +43 -0
  394. package/skills/scaleway/scaleway-managed-mongodb-architect/metadata.json +24 -0
  395. package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/live.md +99 -0
  396. package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/offline.md +114 -0
  397. package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit.md +24 -0
  398. package/skills/scaleway/scaleway-managed-mongodb-architect/references/evidence-ledger.md +43 -0
  399. package/skills/scaleway/scaleway-managed-mongodb-architect/references/official-sources.md +14 -0
  400. package/skills/scaleway/scaleway-managed-mongodb-architect/references/operations.md +114 -0
  401. package/skills/scaleway/scaleway-managed-mongodb-architect/references/safety-checklist.md +22 -0
  402. package/skills/scaleway/scaleway-managed-mongodb-architect/references/workflow-and-output.md +22 -0
  403. package/templates/nosql-audit-template.md +127 -0
  404. package/templates/nosql-operations-template.md +60 -0
  405. package/tests/_generate_maestro_routing_fixtures.py +11 -0
  406. package/tests/fixtures/README.md +2 -2
  407. package/tests/fixtures/alibaba-maestro-routing/expected/050-happy-tablestore-partition-key.json +6 -0
  408. package/tests/fixtures/alibaba-maestro-routing/expected/adv-tablestore-not-polardb.json +6 -0
  409. package/tests/fixtures/alibaba-maestro-routing/inputs/050-happy-tablestore-partition-key.json +7 -0
  410. package/tests/fixtures/alibaba-maestro-routing/inputs/adv-tablestore-not-polardb.json +7 -0
  411. package/tests/fixtures/alibaba-maestro-routing/taxonomy.json +13 -0
  412. package/tests/fixtures/aws-maestro-routing/expected/042-happy-dynamodb-patterns.json +6 -0
  413. package/tests/fixtures/aws-maestro-routing/expected/043-happy-dynamodb-vector-index.json +6 -0
  414. package/tests/fixtures/aws-maestro-routing/inputs/042-happy-dynamodb-patterns.json +7 -0
  415. package/tests/fixtures/aws-maestro-routing/inputs/043-happy-dynamodb-vector-index.json +7 -0
  416. package/tests/fixtures/aws-maestro-routing/taxonomy.json +15 -1
  417. package/tests/fixtures/azure-maestro-routing/expected/028-happy-cosmosdb-pattern-feature-plan.json +6 -0
  418. package/tests/fixtures/azure-maestro-routing/expected/029-happy-cosmosdb-pattern-refactor.json +6 -0
  419. package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-hot-partition-not-key-vault.json +6 -0
  420. package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-partition-key-not-key-vault.json +6 -0
  421. package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-throttling-investigation.json +6 -0
  422. package/tests/fixtures/azure-maestro-routing/inputs/028-happy-cosmosdb-pattern-feature-plan.json +7 -0
  423. package/tests/fixtures/azure-maestro-routing/inputs/029-happy-cosmosdb-pattern-refactor.json +7 -0
  424. package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-hot-partition-not-key-vault.json +7 -0
  425. package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-partition-key-not-key-vault.json +7 -0
  426. package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-throttling-investigation.json +7 -0
  427. package/tests/fixtures/azure-maestro-routing/taxonomy.json +21 -2
  428. package/tests/fixtures/gcp-maestro-routing/expected/049-happy-bigtable-row-key.json +6 -0
  429. package/tests/fixtures/gcp-maestro-routing/expected/adv-bigtable-not-firestore.json +8 -0
  430. package/tests/fixtures/gcp-maestro-routing/inputs/049-happy-bigtable-row-key.json +7 -0
  431. package/tests/fixtures/gcp-maestro-routing/inputs/adv-bigtable-not-firestore.json +7 -0
  432. package/tests/fixtures/gcp-maestro-routing/taxonomy.json +15 -0
  433. package/tests/fixtures/huawei-maestro-routing/expected/050-happy-geminidb-cassandra-partition.json +6 -0
  434. package/tests/fixtures/huawei-maestro-routing/expected/adv-geminidb-mongo-routes-dds.json +7 -0
  435. package/tests/fixtures/huawei-maestro-routing/inputs/050-happy-geminidb-cassandra-partition.json +7 -0
  436. package/tests/fixtures/huawei-maestro-routing/inputs/adv-geminidb-mongo-routes-dds.json +7 -0
  437. package/tests/fixtures/huawei-maestro-routing/taxonomy.json +15 -0
  438. package/tests/fixtures/nosql-scenarios/scenarios.json +472 -0
  439. package/tests/fixtures/oci-maestro-routing/expected/031-happy-nosql-database-architect.json +6 -0
  440. package/tests/fixtures/oci-maestro-routing/expected/032-happy-nosql-global-active-table.json +6 -0
  441. package/tests/fixtures/oci-maestro-routing/expected/033-happy-nosql-pattern-recovery.json +6 -0
  442. package/tests/fixtures/oci-maestro-routing/expected/034-happy-nosql-pattern-refactor.json +6 -0
  443. package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-live-mutation.json +6 -0
  444. package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-not-autonomous.json +7 -0
  445. package/tests/fixtures/oci-maestro-routing/inputs/031-happy-nosql-database-architect.json +7 -0
  446. package/tests/fixtures/oci-maestro-routing/inputs/032-happy-nosql-global-active-table.json +7 -0
  447. package/tests/fixtures/oci-maestro-routing/inputs/033-happy-nosql-pattern-recovery.json +7 -0
  448. package/tests/fixtures/oci-maestro-routing/inputs/034-happy-nosql-pattern-refactor.json +7 -0
  449. package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-live-mutation.json +7 -0
  450. package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-not-autonomous.json +7 -0
  451. package/tests/fixtures/oci-maestro-routing/taxonomy.json +27 -0
  452. package/tests/requirements-ci.txt +8 -0
  453. package/tests/validate-aws-skill-quality.py +7 -0
  454. package/tests/validate-nosql-audit.py +741 -0
  455. package/tests/validate-nosql-operations.py +136 -0
  456. package/tests/validate-nosql-pattern-evals.py +96 -0
  457. package/tests/validate-nosql-scenarios.py +94 -0
  458. package/tests/validate-skill-manifest.py +6 -1
  459. package/tests/validate-skill-references.py +225 -0
@@ -0,0 +1,124 @@
1
+ # audit --mode live
2
+
3
+ Commands are examples for an operator holding read-only authorization; the skill
4
+ does not run them. They read Firestore control-plane metadata only and never read
5
+ documents or collections. Expectations come from
6
+ [Native operations](../../firestore-operations.md) or
7
+ [MongoDB operations](../../firestore-mongodb-operations.md). The Firestore Admin API
8
+ commands below take a database ID; whether every field applies to an Enterprise
9
+ (MongoDB-compatible) database is unverified, so read the `databaseEdition` field in
10
+ the output before applying a Native-mode expectation.
11
+
12
+ ## Before any command
13
+
14
+ - Confirm the approved principal, project, database ID, location and mode. Stop on any
15
+ mismatch; never switch target to make a command work.
16
+ - Use a read-only role. Write output to a private directory (`umask 077`). Never
17
+ print keys, connection strings, SCRAM credentials or customer data.
18
+
19
+ Identity check, using the active account and the active configuration [FS-E901] [FS-E902]:
20
+
21
+ ```bash
22
+ set -euo pipefail
23
+ : "${GCP_PROJECT:?Approved project ID}" "${FS_DATABASE:?Approved database ID}" \
24
+ "${FS_LOCATION:?Approved database location}" "${EXPECTED_ACCOUNT:?Approved principal}"
25
+ umask 077
26
+ audit_dir=$(mktemp -d)
27
+ gcloud auth list --filter=status:ACTIVE --format="value(account)" > "$audit_dir/account.txt"
28
+ gcloud config list --format=json > "$audit_dir/config.json"
29
+ grep -qxF "$EXPECTED_ACCOUNT" "$audit_dir/account.txt" || { echo "Principal mismatch; stop" >&2; exit 1; }
30
+ jq -e --arg p "$GCP_PROJECT" '.core.project == $p' "$audit_dir/config.json" >/dev/null \
31
+ || { echo "Project mismatch; stop" >&2; exit 1; } # core/project property [FS-E902]
32
+ # Impersonation or an access-token file makes requests run as another identity [FS-E912] [FS-E913]
33
+ jq -e '(.auth.impersonate_service_account // "") == "" and (.auth.access_token_file // "") == ""' \
34
+ "$audit_dir/config.json" >/dev/null || { echo "Credential override set; stop" >&2; exit 1; }
35
+ ```
36
+
37
+ The blocks below assume the variables and `audit_dir` from this block.
38
+
39
+ ## Backup and restore
40
+
41
+ - Native mode: schedules, backups and the PITR setting in the database metadata.
42
+ - MongoDB compatibility: the same commands; confirm in the output that they apply.
43
+
44
+ Sources [FS-E903] [FS-E904] [FS-E905]:
45
+
46
+ ```bash
47
+ gcloud firestore databases describe --database="$FS_DATABASE" --project="$GCP_PROJECT" --format=json > "$audit_dir/database.json"
48
+ gcloud firestore backups schedules list --database="$FS_DATABASE" --project="$GCP_PROJECT" --format=json > "$audit_dir/schedules.json"
49
+ gcloud firestore backups list --location="$FS_LOCATION" --project="$GCP_PROJECT" --format=json > "$audit_dir/backups.json"
50
+ ```
51
+
52
+ ## Disaster recovery and replication
53
+
54
+ Location and type of the database come from the metadata read above; the same file
55
+ serves both modes [FS-E903]:
56
+
57
+ ```bash
58
+ gcloud firestore databases describe --database="$FS_DATABASE" --project="$GCP_PROJECT" --format=json > "$audit_dir/database-location.json"
59
+ ```
60
+
61
+ ## Cost
62
+
63
+ **No live command:** spend lives in Cloud Billing reports and the billing export, not
64
+ in the Firestore resource API. Searched the gcloud Firestore reference; no cost
65
+ command exists. Usage metrics need an approved Monitoring read.
66
+
67
+ ## Monitoring
68
+
69
+ Alerting policies in the project; filter for Firestore metrics in the output [FS-E909]:
70
+
71
+ ```bash
72
+ gcloud monitoring policies list --project="$GCP_PROJECT" --format=json > "$audit_dir/alert-policies.json"
73
+ ```
74
+
75
+ ## Performance
76
+
77
+ **No live command:** latency, contention and hotspot signals come from Cloud
78
+ Monitoring metrics and client error codes, not from a gcloud Firestore command.
79
+ Searched the gcloud Firestore reference; none returns them.
80
+
81
+ ## IAM
82
+
83
+ Project-level policy; look for the `roles/datastore.*` roles and Conditions [FS-E906].
84
+ No gcloud command that reads a database-level IAM policy was retrieved in this pass,
85
+ so database-scoped bindings are UNVERIFIED by this audit:
86
+
87
+ ```bash
88
+ gcloud projects get-iam-policy "$GCP_PROJECT" --format=json > "$audit_dir/project-iam.json"
89
+ ```
90
+
91
+ ## Tagging
92
+
93
+ Tag bindings on the database; set the parent to the database's full resource name
94
+ from the approved scope [FS-E908]:
95
+
96
+ ```bash
97
+ : "${DATABASE_FULL_RESOURCE_NAME:?Approved full resource name of the database}"
98
+ gcloud resource-manager tags bindings list --parent="$DATABASE_FULL_RESOURCE_NAME" --effective --format=json > "$audit_dir/tag-bindings.json"
99
+ ```
100
+
101
+ ## Encryption
102
+
103
+ The database metadata carries the CMEK configuration (`cmekConfig`) when CMEK is
104
+ enabled, for both modes [FS-E903] [FS-E910]:
105
+
106
+ ```bash
107
+ gcloud firestore databases describe --database="$FS_DATABASE" --project="$GCP_PROJECT" --format=json > "$audit_dir/database-encryption.json"
108
+ ```
109
+
110
+ ## Network isolation
111
+
112
+ **No live command:** VPC Service Controls perimeters and Private Google Access
113
+ belong to the Access Context Manager and VPC APIs, whose reference pages were not
114
+ retrieved in this pass. No documented Firestore command lists a database's network
115
+ settings.
116
+
117
+ ## Audit logging
118
+
119
+ Recent audit log entries for the Firestore service name; the format keeps only time,
120
+ method and caller, not request payloads [FS-E907]:
121
+
122
+ ```bash
123
+ gcloud logging read 'protoPayload.serviceName="firestore.googleapis.com"' --project="$GCP_PROJECT" --freshness=7d --limit=50 --format="value(timestamp,protoPayload.methodName,protoPayload.authenticationInfo.principalEmail)" > "$audit_dir/audit-log.txt" # [FS-E914]
124
+ ```
@@ -0,0 +1,146 @@
1
+ # audit --mode offline
2
+
3
+ Inputs are the repository (IaC, Firebase config, security rules, client code) and
4
+ sanitized exports supplied by the user. Use local tools only: no cloud CLI, network
5
+ call, credential or customer data. Field names follow the Firestore Admin API
6
+ Database and BackupSchedule resources [FS-E910] [FS-E911]. An absent setting in the
7
+ repository does not prove the live setting; record it as UNVERIFIED. Expectations
8
+ come from [Native operations](../../firestore-operations.md) and
9
+ [MongoDB operations](../../firestore-mongodb-operations.md); audit only the mode in use.
10
+
11
+ ## Backup and restore
12
+
13
+ - Native mode: check for point-in-time recovery (`pointInTimeRecoveryEnablement`) and
14
+ for backup schedules (`dailyRecurrence`, `weeklyRecurrence`, `retention`) [FS-E910]
15
+ [FS-E911]; compare retention with the recovery objective.
16
+ - MongoDB compatibility: same fields; also check the restore runbook for the TTL
17
+ policies a backup does not carry (MongoDB operations, Backup and restore).
18
+ - Both: a restore always creates a new database, so check that runbooks and client
19
+ config can point at a new database ID.
20
+ - Check `deleteProtectionState` on production databases [FS-E910].
21
+
22
+ ```bash
23
+ rg -n -i 'point.?in.?time.?recovery|pitr|daily.?recurrence|weekly.?recurrence|backup.?schedule|delete.?protection' \
24
+ --glob '*.tf' --glob '*.json' --glob '*.yaml' --glob '*.yml' --glob '*.md'
25
+ ```
26
+
27
+ ## Disaster recovery and replication
28
+
29
+ - Both modes: check `locationId` for regional versus multi-region against the
30
+ availability target; the location cannot be changed after creation [FS-E910].
31
+ - Check runbooks do not promise an RTO or RPO for zone or region outages, which the
32
+ operations references do not document.
33
+ - Check that the cross-database copy or export plan, if any, uses the PITR-clone or
34
+ backup-restore path described in the operations reference.
35
+
36
+ ```bash
37
+ rg -n -i 'location.?id|multi.?region|nam5|eur3|nam7|database.?edition' \
38
+ --glob '*.tf' --glob '*.json' --glob '*.yaml' --glob '*.md'
39
+ ```
40
+
41
+ ## Cost
42
+
43
+ - Native mode: check query shapes that scan many index entries or read whole
44
+ collections, and index exemptions that cut storage (Native operations, Cost).
45
+ - MongoDB compatibility: billing is in read, write and event units; check change
46
+ streams and index counts (MongoDB operations, Cost).
47
+ - Both: check TTL policies, retention of backups and PITR (no free tier).
48
+
49
+ ```bash
50
+ rg -n -i 'ttl|index.?exemption|fieldOverrides|change.?stream|\.count\(|limit\(' \
51
+ --glob '*.tf' --glob '*.json' --glob '*.ts' --glob '*.js' --glob '*.py'
52
+ ```
53
+
54
+ ## Monitoring
55
+
56
+ - Both modes: check for alerting policies on request latency and error rate in IaC.
57
+ - Native mode: check for `api/request_count` and the document operation metrics.
58
+ - MongoDB compatibility: check for `api/billable_read_units` and the other billing
59
+ metrics named in the MongoDB operations reference.
60
+ - Check that monitoring is defined in code, not only in the console.
61
+
62
+ ```bash
63
+ rg -n -i 'firestore\.googleapis\.com|request_latencies|request_count|billable_(read|write)_units|alert.?policy' \
64
+ --glob '*.tf' --glob '*.json' --glob '*.yaml'
65
+ ```
66
+
67
+ ## Performance
68
+
69
+ - Native mode: check bulk loaders against the 500/50/5 ramp rule, and monotonic
70
+ indexed values (timestamps, counters) that hotspot (Native operations, Performance).
71
+ - MongoDB compatibility: check driver settings for TLS and disabled retryable writes;
72
+ do not apply the 500/50/5 rule (MongoDB operations, Performance).
73
+ - Both: check transaction code against the 270-second limit and contention retries.
74
+
75
+ ```bash
76
+ rg -n -o -i 'retry.?writes|tls=|ssl=|serverTimeout|runTransaction|BulkWriter|batch.?write' \
77
+ --glob '*.ts' --glob '*.js' --glob '*.py' --glob '*.java' --glob '*.go' --glob '*.env*'
78
+ ```
79
+
80
+ ## IAM
81
+
82
+ - Both modes: check bindings of `roles/datastore.user`, `roles/datastore.owner`,
83
+ `roles/datastore.backupsAdmin` and `roles/datastore.restoreAdmin`; prefer the
84
+ narrowest role on the specific database, with IAM Conditions.
85
+ - Native mode: check Firebase Security Rules files for open `allow read, write: if true`
86
+ patterns; server client libraries bypass rules.
87
+ - MongoDB compatibility: check which SCRAM users exist in code and that each has a role.
88
+ - Check for service-account key files committed to the repository.
89
+
90
+ ```bash
91
+ rg -n -i 'roles/datastore\.|allow (read|write)[^;]*: *if true|allUsers|scram|firestore\.rules' \
92
+ --glob '*.tf' --glob '*.json' --glob '*.rules' --glob '*.yaml'
93
+ ```
94
+
95
+ ## Tagging
96
+
97
+ - Both modes: check that databases carry resource tags (`tags`) where conditional
98
+ IAM depends on them, set at creation [FS-E910].
99
+ - Check that tag keys and values are not secrets or customer data.
100
+
101
+ ```bash
102
+ rg -n -i '\btags\b|tag.?binding|tag.?value' --glob '*.tf' --glob '*.json' --glob '*.yaml'
103
+ ```
104
+
105
+ ## Encryption
106
+
107
+ - Both modes: CMEK is set only at database creation and the key location must match
108
+ the database; check `cmekConfig` and `kmsKeyName` [FS-E910].
109
+ - MongoDB compatibility: the CMEK quota is allowlisted; check access was requested.
110
+ - Both: check client config for plaintext transport (non-TLS connection strings).
111
+ The second command lists files only; never print the matching line, which can
112
+ hold a connection string with credentials.
113
+
114
+ ```bash
115
+ rg -n -o -i 'cmek.?config|kms.?key.?name' \
116
+ --glob '*.tf' --glob '*.json' --glob '*.yaml' --glob '*.env*' --glob '*.ts' --glob '*.py'
117
+ rg -l -i 'mongodb://|tls=false|ssl=false' \
118
+ --glob '*.tf' --glob '*.json' --glob '*.yaml' --glob '*.env*' --glob '*.ts' --glob '*.py'
119
+ ```
120
+
121
+ ## Network isolation
122
+
123
+ - Both modes: check for VPC Service Controls perimeters that include
124
+ `firestore.googleapis.com` (operations references, Network isolation).
125
+ - MongoDB compatibility: check for Private Google Access and the private DNS zone for
126
+ the restricted VIP; do not assume Native mode has the same path.
127
+ - Check client config for hard-coded public endpoints.
128
+
129
+ ```bash
130
+ rg -n -i 'firestore\.googleapis\.com|service.?perimeter|private.?google.?access|restricted\..*goog' \
131
+ --glob '*.tf' --glob '*.json' --glob '*.yaml'
132
+ ```
133
+
134
+ ## Audit logging
135
+
136
+ - Both modes: check that Data Access audit logs are configured for
137
+ `datastore.googleapis.com` (it covers `firestore.googleapis.com`) as well as the
138
+ default Admin Activity logs.
139
+ - Check log sinks, retention and exempted principals.
140
+ - Check that bulk import, bulk delete and TTL activity is not assumed to be audited
141
+ per write (Native operations, Audit logging).
142
+
143
+ ```bash
144
+ rg -n -i 'audit.?config|datastore\.googleapis\.com|DATA_READ|DATA_WRITE|ADMIN_READ|exempted.?members' \
145
+ --glob '*.tf' --glob '*.json' --glob '*.yaml'
146
+ ```
@@ -0,0 +1,27 @@
1
+ # audit
2
+
3
+ Load only for an audit request. Offline is the default. After reading this file,
4
+ load **only** the selected variant: [offline](audit/offline.md) or
5
+ [live](audit/live.md). Do not read both.
6
+
7
+ ## Scope
8
+
9
+ - This skill covers all of Firebase, but the audit covers **Firestore only**:
10
+ Native mode ([Native operations](../firestore-operations.md)) and Firestore with
11
+ MongoDB compatibility ([MongoDB operations](../firestore-mongodb-operations.md)).
12
+ Authentication, Hosting, Functions, Realtime Database and Storage are out of scope.
13
+ - Name the project, database ID, location, the mode (Native or MongoDB compatibility)
14
+ and the selected sections of the matching operations reference. The two modes are
15
+ separate: do not carry a Native-mode expectation into a MongoDB-compatible database.
16
+ Unselected sections are out of scope.
17
+ - An audit is a technical risk review, not a compliance attestation.
18
+
19
+ ## Findings
20
+
21
+ For each finding give: severity, section, mode, evidence (file:line, or sanitized
22
+ command output with its retrieval time), the expectation from the operations
23
+ reference with its evidence ID, impact, the smallest proposed fix and how to verify it.
24
+
25
+ - PASS only for a check actually performed. Missing evidence is UNVERIFIED.
26
+ - An absent repository setting does not prove the live setting is off.
27
+ - Propose fixes; never apply them as part of the audit.
@@ -0,0 +1,190 @@
1
+ # Evidence ledger — Cloud Firestore
2
+
3
+ Every material claim in [firestore.md](firestore.md) cites one row below as
4
+ `[FS-Exx]`. `tests/validate-skill-references.py` fails the build if a citation
5
+ has no row, a row is never cited, or a source is not an allow-listed Google
6
+ documentation host.
7
+
8
+ Scope: **Cloud Firestore**, Standard edition and Native mode unless a row says
9
+ Enterprise edition or MongoDB compatibility. Not Firebase Realtime Database,
10
+ not Datastore mode. `VERIFIED` = the section was retrieved on the retrieval
11
+ date and supports the claim as worded; it is documentation verification, not a
12
+ behavioral test. Limits change: re-fetch before relying on a number.
13
+
14
+ | ID | Claim | Source | Section | Retrieved | Status |
15
+ | --- | --- | --- | --- | --- | --- |
16
+ | FS-E01 | Limits: a document is at most 1 MiB; subcollections nest at most 100 deep; a document has at most 40,000 index entries (single-field plus composite); an API request is at most 10 MiB. | <https://firebase.google.com/docs/firestore/quotas> | Collections, documents, and fields; Indexes; Writes and transactions | 2026-11-08 | VERIFIED |
17
+ | FS-E02 | A database has at most 200 composite indexes without billing enabled and 1,000 with billing enabled. | <https://firebase.google.com/docs/firestore/quotas> | Indexes | 2026-11-08 | VERIFIED |
18
+ | FS-E03 | A transaction has a 270-second time limit with a 60-second idle expiration. | <https://firebase.google.com/docs/firestore/quotas> | Writes and transactions | 2026-11-08 | VERIFIED |
19
+ | FS-E04 | Ramp traffic to a new collection with the "500/50/5" rule: start at most 500 operations per second, then increase by 50% every 5 minutes. | <https://firebase.google.com/docs/firestore/best-practices> | Ramping up traffic | 2026-11-08 | VERIFIED |
20
+ | FS-E05 | Automatic document IDs use a scatter algorithm and should not hotspot on writes; the maximum update rate of a single document depends highly on the workload (no fixed figure is given). | <https://firebase.google.com/docs/firestore/best-practices> | Hotspots | 2026-11-08 | VERIFIED |
21
+ | FS-E06 | Firestore guarantees serializable isolation of transactions, serialized by commit time. | <https://firebase.google.com/docs/firestore/transaction-data-contention> | Serializable isolation | 2026-11-08 | VERIFIED |
22
+ | FS-E07 | Mobile/web SDKs always use optimistic concurrency; server client libraries follow the database setting, which defaults to PESSIMISTIC on Standard edition (transactions lock the documents they read) and OPTIMISTIC on Enterprise edition. | <https://firebase.google.com/docs/firestore/transaction-data-contention> | Concurrency controls; Concurrency mode defaults | 2026-11-08 | VERIFIED |
23
+ | FS-E08 | Server client libraries exist for C#, Go, Java, Node.js, PHP, Python and Ruby; their requests are not evaluated against Firebase security rules and are secured with IAM, whereas mobile/web SDKs rely on security rules and Firebase Auth. | <https://firebase.google.com/docs/firestore/client/libraries> | Server client libraries; Mobile and web SDKs | 2026-11-08 | VERIFIED |
24
+ | FS-E09 | Standard edition query limits: at most 30 disjunctions in disjunctive normal form (fixed); `not-in` takes at most 10 values and cannot combine with `!=`; at most one `array-contains` per disjunction, not combinable with `array-contains-any` in the same disjunction. | <https://firebase.google.com/docs/firestore/query-data/queries> | Limitations | 2026-11-08 | VERIFIED |
25
+ | FS-E10 | Standard edition builds single-field indexes for each field automatically (collection-group-scope automatic indexes are not maintained by default); composite indexes are never created automatically; index exemptions reduce storage cost and can improve write performance. | <https://firebase.google.com/docs/firestore/query-data/index-overview> | Single-field indexes; Composite indexes; Index exemptions | 2026-11-08 | VERIFIED |
26
+ | FS-E11 | A database's location cannot be changed after provisioning; multi-region locations store replicas in several regions and keep serving through the loss of a region; regional locations cost less and give lower write latency. | <https://firebase.google.com/docs/firestore/locations> | Locations | 2026-11-08 | VERIFIED |
27
+ | FS-E12 | PITR is disabled by default; once enabled it retains one version per minute for 7 days; without PITR, documents can still be read (not exported) at any timestamp within the past hour. | <https://firebase.google.com/docs/firestore/pitr> | PITR overview | 2026-11-08 | VERIFIED |
28
+ | FS-E13 | Scheduled backups: at most one daily and one weekly schedule per database, retention up to 14 weeks, stored in the source database's location, restored to a new database. | <https://firebase.google.com/docs/firestore/backups> | Back up and restore data | 2026-11-08 | VERIFIED |
29
+ | FS-E14 | TTL deletion is not instantaneous: expired documents still appear in queries and lookups until deleted, typically within 24 hours of expiry. | <https://firebase.google.com/docs/firestore/ttl> | TTL policies | 2026-11-08 | VERIFIED |
30
+ | FS-E15 | Enterprise edition offers two modes chosen at database creation, Native mode (Core and Pipeline operations) and Firestore with MongoDB compatibility; in Enterprise, indexing is fully customizable and single-field indexes are not created automatically. Standard edition does not support MongoDB compatibility. | <https://firebase.google.com/docs/firestore/editions> | Editions overview | 2026-11-08 | VERIFIED |
31
+ | FS-E17 | PITR storage has no free tier and requires billing; queries in the PITR window (stale reads or exports) incur read costs; up to one day of PITR storage may be charged even if PITR is disabled within a day of enabling it. | <https://firebase.google.com/docs/firestore/pitr> | Pricing | 2026-11-08 | VERIFIED |
32
+ | FS-E18 | Server client library install: Python `pip install --upgrade google-cloud-firestore`; Node.js `npm install --save @google-cloud/firestore`; Go `go get cloud.google.com/go/firestore`; Java Maven `com.google.cloud:google-cloud-firestore` (version managed by `libraries-bom`). | <https://docs.cloud.google.com/firestore/native/docs/create-database-server-client-library> | Add the server client library to your app | 2026-11-08 | VERIFIED |
33
+ | FS-E19 | Datastore compatibility is a database-level setting chosen at creation that disables access to new Firestore capabilities: the database accepts Datastore API requests and denies Firestore API requests, and Firestore real-time capabilities are not available. | <https://docs.cloud.google.com/datastore/docs/firestore-or-datastore> | Choose between Firestore APIs | 2026-11-08 | VERIFIED |
34
+ | FS-E101 | Native mode backups exclude database TTL policies and Firebase Security Rules. | <https://docs.cloud.google.com/firestore/native/docs/backups> | Back up and restore data: "A backup does not contain database time to live policies or Firebase Security Rules." | 2026-11-08 | VERIFIED |
35
+ | FS-E102 | Deleting the source database does not delete its backups. | <https://docs.cloud.google.com/firestore/native/docs/backups> | Back up and restore data: "Deleting the source database does not automatically delete related backups." | 2026-11-08 | VERIFIED |
36
+ | FS-E103 | A Native mode restore writes the backup into a new database. | <https://docs.cloud.google.com/firestore/native/docs/backups> | Back up and restore data: "A restore operation writes the data from a backup to a new Firestore" | 2026-11-08 | VERIFIED |
37
+ | FS-E104 | After a restore, TTL policies must be reapplied because they are not included in backups or reapplied automatically. | <https://docs.cloud.google.com/firestore/native/docs/backups> | Back up and restore data: "TTL policies are not included in backups and are not automatically reapplied to restored databases." | 2026-11-08 | VERIFIED |
38
+ | FS-E105 | A restore operation is billed on the size of the backup. | <https://docs.cloud.google.com/firestore/native/docs/backups> | Back up and restore data: "For a restore operation, you're charged based on the size of the backup." | 2026-11-08 | VERIFIED |
39
+ | FS-E106 | Starting an in-place restore permanently loses the original database. | <https://docs.cloud.google.com/firestore/native/docs/restore-in-place> | Perform an in-place restore operation: "Once you start the in-place restore process, the original database is permanently lost, and you can't undo this operation." | 2026-11-08 | VERIFIED |
40
+ | FS-E107 | Regional Native mode databases replicate synchronously across at least three zones. | <https://docs.cloud.google.com/firestore/native/docs/disaster-recovery> | Plan disaster recovery: "Regional databases synchronously replicate data across at least three zones." | 2026-11-08 | VERIFIED |
41
+ | FS-E108 | Multi-region Native mode databases replicate synchronously across five zones in three regions (two serving regions and one witness region). | <https://docs.cloud.google.com/firestore/native/docs/disaster-recovery> | Plan disaster recovery: "Multi-region databases synchronously replicate data across five zones in three regions with two serving regions and one witness region." | 2026-11-08 | VERIFIED |
42
+ | FS-E109 | Firestore handles replication automatically without extra configuration or provisioning. | <https://docs.cloud.google.com/firestore/native/docs/disaster-recovery> | Plan disaster recovery: "Firestore automatically handles replication for you and doesn't require" | 2026-11-08 | VERIFIED |
43
+ | FS-E110 | Documented PITR recovery objectives: recovery time objective of 0 and recovery point objective of 1 minute. | <https://docs.cloud.google.com/firestore/native/docs/disaster-recovery> | Plan disaster recovery: "recovery time objective (maximum time for recovery) of 0. The recovery point objective (maximum possible data loss) is 1 minute." | 2026-11-08 | VERIFIED |
44
+ | FS-E111 | A database can be cloned from up to seven days back with PITR enabled. | <https://docs.cloud.google.com/firestore/native/docs/disaster-recovery> | Plan disaster recovery: "If PITR is enabled, you can clone from up to seven days in the past." | 2026-11-08 | VERIFIED |
45
+ | FS-E112 | Standard edition storage billing includes metadata and index overhead. | <https://cloud.google.com/firestore/pricing> | Firestore Standard edition pricing: "You are charged for the amount of data that you store in Firestore, including storage overhead." | 2026-11-08 | VERIFIED |
46
+ | FS-E113 | Standard edition: TTL deletes, PITR data, backup data, restore operations and clone operations include no free usage and require billing. | <https://cloud.google.com/firestore/pricing> | Firestore Standard edition pricing: "The following operations and features do not include free usage. You must enable billing to use these features:" | 2026-11-08 | VERIFIED |
47
+ | FS-E114 | Standard edition bills backup storage when backups are enabled. | <https://cloud.google.com/firestore/pricing> | Firestore Standard edition pricing: "you are charged for the storage of your database backups. The storage size for a backup is equal to the storage size of the database when the backup was taken." | 2026-11-08 | VERIFIED |
48
+ | FS-E115 | Standard edition bills network bandwidth used by requests. | <https://cloud.google.com/firestore/pricing> | Firestore Standard edition pricing: "You are charged for the network bandwidth used by your Firestore requests, as shown in the following sections." | 2026-11-08 | VERIFIED |
49
+ | FS-E116 | Standard edition bills one read per batch of up to 1000 index entries read by a query, with documented exceptions. | <https://cloud.google.com/firestore/pricing> | Firestore Standard edition pricing: "You are charged one read operation for each batch of up to 1000 index entries read by a query except in the following:" | 2026-11-08 | VERIFIED |
50
+ | FS-E117 | Documents read, written and deleted are billed per document on Standard edition. | <https://cloud.google.com/firestore/pricing> | Firestore Standard edition pricing: "You are charged for each document write and delete that you perform." | 2026-11-08 | VERIFIED |
51
+ | FS-E118 | The api/request_count service runtime metric counts completed requests by response code class and gRPC status, and is used to calculate the error rate. | <https://docs.cloud.google.com/firestore/native/docs/understand-performance-monitoring> | Understand performance monitoring in Firestore: "Use this metric to observe the overall API request and calculate the error rate." | 2026-11-08 | VERIFIED |
52
+ | FS-E119 | Service runtime metrics are sampled every 30 minutes, which smooths the data. | <https://docs.cloud.google.com/firestore/native/docs/understand-performance-monitoring> | Understand performance monitoring in Firestore: "These metrics are sampled every 30 minutes resulting in data being smoothed out." | 2026-11-08 | VERIFIED |
53
+ | FS-E120 | Document operation metrics (document/delete_ops_count, document/read_ops_count, document/write_ops_count) show whether the database is read heavy or write heavy. | <https://docs.cloud.google.com/firestore/native/docs/understand-performance-monitoring> | Understand performance monitoring in Firestore: "The following metrics can be used to understand whether your database is read heavy or write heavy, and the rate of new documents vs. deleted documents." | 2026-11-08 | VERIFIED |
54
+ | FS-E121 | Documented example alert: a latency alerting policy checks p99 latency over a 5 minute rolling window and fires when it stays above 250 ms for 5 minutes. | <https://docs.cloud.google.com/firestore/native/docs/use-monitoring-dashboard> | Use the Cloud Monitoring dashboard: "The alerting policy checks p99 latency over a 5 minute rolling window." | 2026-11-08 | VERIFIED |
55
+ | FS-E122 | The Native mode usage dashboard is an estimate; the billing report takes precedence over it. | <https://firebase.google.com/docs/firestore/monitor-usage> | Monitor Cloud Firestore activity: "In all cases of discrepancy, the billing report takes precedence over the usage dashboard." | 2026-11-08 | VERIFIED |
56
+ | FS-E123 | ABORTED errors can result from traffic increases that exceed the 500-50-5 rule or encounter hot-spots. | <https://docs.cloud.google.com/firestore/native/docs/understand-error-codes> | Understand error codes: "Traffic increases that exceed the 500-50-5 rule or encounter hot-spots." | 2026-11-08 | VERIFIED |
57
+ | FS-E124 | RESOURCE_EXHAUSTED can occur when the free tier quota is exceeded and billing is not enabled. | <https://docs.cloud.google.com/firestore/native/docs/understand-error-codes> | Understand error codes: "You exceeded the free tier quota and billing is not enabled for your project." | 2026-11-08 | VERIFIED |
58
+ | FS-E125 | DEADLINE_EXCEEDED occurs when an operation exceeds the 60 second default deadline. | <https://docs.cloud.google.com/firestore/native/docs/understand-error-codes> | Understand error codes: "An increase in latency caused an operation take longer than the deadline (60 seconds by default) to complete." | 2026-11-08 | VERIFIED |
59
+ | FS-E126 | INVALID_ARGUMENT is returned for indexed field values larger than 1,500 bytes. | <https://docs.cloud.google.com/firestore/native/docs/understand-error-codes> | Understand error codes: "Attempting to commit a document with an indexed field value greater than 1,500 bytes." | 2026-11-08 | VERIFIED |
60
+ | FS-E127 | Sustained high concurrent operations on a single document can hotspot because Firestore cannot split a key range below one document. | <https://docs.cloud.google.com/firestore/native/docs/understand-reads-writes-scale> | Understand reads and writes at scale: "high and sustained volumes of concurrent operations on a single document may lead to a hotspot on that document." | 2026-11-08 | VERIFIED |
61
+ | FS-E128 | Indexing monotonically increasing or decreasing values such as timestamps can cause hotspots at high read and write rates. | <https://docs.cloud.google.com/firestore/native/docs/understand-reads-writes-scale> | Understand reads and writes at scale: "Indexing fields with monotonically increasing/decreasing values, such as timestamps, can lead to hotspots which affect latency for applications with high read and write rates." | 2026-11-08 | VERIFIED |
62
+ | FS-E129 | Write and transaction latency increases as the number of splits or participants increases. | <https://docs.cloud.google.com/firestore/native/docs/understand-reads-writes-scale> | Understand reads and writes at scale: "Write/transaction latency increases as the number of splits/participants increases." | 2026-11-08 | VERIFIED |
63
+ | FS-E130 | Role roles/datastore.user grants read/write access to data in a database and is intended for application developers and service accounts. | <https://docs.cloud.google.com/firestore/native/docs/security/iam> | Identity and Access Management (IAM): "Read/write access to data in a Firestore database. Intended for application developers and service accounts." | 2026-11-08 | VERIFIED |
64
+ | FS-E131 | Role roles/datastore.restoreAdmin restores a backup into a new database and also allows creating new databases. | <https://docs.cloud.google.com/firestore/native/docs/security/iam> | Identity and Access Management (IAM): "Ability to restore a Firestore backup into a new database. This role also gives the ability to create new databases, not necessarily by restoring from a backup." | 2026-11-08 | VERIFIED |
65
+ | FS-E132 | Firestore caches IAM permissions for 5 minutes, so a role change takes up to 5 minutes to take effect. | <https://docs.cloud.google.com/firestore/native/docs/security/iam> | Identity and Access Management (IAM): "Firestore caches IAM permissions for 5 minutes, so it takes up to 5 minutes for a role change to become effective." | 2026-11-08 | VERIFIED |
66
+ | FS-E133 | IAM Conditions can define and enforce conditional access control for Firestore roles. | <https://docs.cloud.google.com/firestore/native/docs/security/iam> | Identity and Access Management (IAM): "You can use IAM Conditions to define and enforce conditional access control." | 2026-11-08 | VERIFIED |
67
+ | FS-E134 | Tags are key-value pairs on Google Cloud resources that can conditionally allow or deny policies, for example conditional IAM grants. | <https://docs.cloud.google.com/firestore/native/docs/tags> | Create and manage tags: "You can use tags to conditionally allow or deny policies based on whether a resource has a specific tag." | 2026-11-08 | VERIFIED |
68
+ | FS-E135 | Attaching tags to Firestore databases requires the Datastore Owner role (roles/datastore.owner). | <https://docs.cloud.google.com/firestore/native/docs/tags> | Create and manage tags: "To attach tags to Firestore instances, you need the Datastore Owner role" | 2026-11-08 | VERIFIED |
69
+ | FS-E136 | Tags can be added to existing databases through tag bindings. | <https://docs.cloud.google.com/firestore/native/docs/tags> | Create and manage tags: "To add a tag to existing databases, follow these steps:" | 2026-11-08 | VERIFIED |
70
+ | FS-E137 | Firestore encrypts all data before it is written to disk, with no setup or configuration required. | <https://docs.cloud.google.com/firestore/native/docs/server-side-encryption> | Server-side encryption: "Firestore automatically encrypts all data before it is written to disk." | 2026-11-08 | VERIFIED |
71
+ | FS-E138 | Data in transit over the Internet is protected with Transport Layer Security (TLS). | <https://docs.cloud.google.com/firestore/native/docs/server-side-encryption> | Server-side encryption: "To protect your data as it travels over the Internet during read and write operations, we use Transport Layer Security (TLS)." | 2026-11-08 | VERIFIED |
72
+ | FS-E139 | CMEK can be enabled only on new databases at creation time. | <https://docs.cloud.google.com/firestore/native/docs/cmek> | Customer-managed encryption keys (CMEK): "You can enable CMEK only on new databases, and you must enable it when you create the database." | 2026-11-08 | VERIFIED |
73
+ | FS-E140 | The key of a CMEK-protected database cannot be changed but can be rotated, enabled and disabled. | <https://docs.cloud.google.com/firestore/native/docs/cmek> | Customer-managed encryption keys (CMEK): "You can't change a key for a CMEK-protected database. You can rotate, enable, and disable keys." | 2026-11-08 | VERIFIED |
74
+ | FS-E141 | With CMEK, data in transit or in memory and database metadata remain under Google default encryption. | <https://docs.cloud.google.com/firestore/native/docs/cmek> | Customer-managed encryption keys (CMEK): "The following data types are encrypted with Google default encryption and not by the CMEK key:" | 2026-11-08 | VERIFIED |
75
+ | FS-E142 | When the CMEK key is unavailable, calls to the database return FAILED_PRECONDITION within 10 minutes. | <https://docs.cloud.google.com/firestore/native/docs/cmek> | Customer-managed encryption keys (CMEK): "within 10 minutes any subsequent calls to the Firestore database, including reads, writes, and queries, return a" | 2026-11-08 | VERIFIED |
76
+ | FS-E143 | The Cloud KMS key location must match the location of the Firestore database. | <https://docs.cloud.google.com/firestore/native/docs/use-cmek> | Use customer-managed encryption keys (CMEK): "The Cloud KMS key location must be the same as the location of the Firestore database that it will be used with." | 2026-11-08 | VERIFIED |
77
+ | FS-E144 | Restricting the Firestore API service in a VPC Service Controls perimeter also restricts the bundled Datastore and Key Visualizer API services. | <https://docs.cloud.google.com/firestore/native/docs/securing-with-vpc-sc> | VPC Service Controls: "service in a perimeter, the perimeter also restricts the" | 2026-11-08 | VERIFIED |
78
+ | FS-E145 | With VPC Service Controls, import and export need the Firestore service agent for full egress protection. | <https://docs.cloud.google.com/firestore/native/docs/securing-with-vpc-sc> | VPC Service Controls: "If you use VPC Service Controls, you must use the Firestore service agent to fully protect import and export operations." | 2026-11-08 | VERIFIED |
79
+ | FS-E146 | Audit logging is configured with service name datastore.googleapis.com, which covers both datastore.googleapis.com and firestore.googleapis.com. | <https://docs.cloud.google.com/firestore/native/docs/audit-logging> | Firestore audit logging information: "When configuring audit logging, use the service name datastore.googleapis.com" | 2026-11-08 | VERIFIED |
80
+ | FS-E147 | Methods needing an ADMIN_WRITE permission generate Admin Activity audit logs. | <https://docs.cloud.google.com/firestore/native/docs/audit-logging> | Firestore audit logging information: "Methods that require an IAM permission with the type property value of ADMIN_WRITE generate" | 2026-11-08 | VERIFIED |
81
+ | FS-E148 | Individual writes from import, bulk delete operations and TTL are not audit logged. | <https://docs.cloud.google.com/firestore/native/docs/audit-logging> | Firestore audit logging information: "Individual writes from import, bulk delete operations and TTL are not audit logged." | 2026-11-08 | VERIFIED |
82
+ | FS-E149 | A restore does not restore App Engine search data or blob entities from the (default) database. | <https://docs.cloud.google.com/firestore/native/docs/backups> | Back up and restore data: "A restore operation does not restore App Engine search data or blob entities from a (default)" | 2026-11-08 | VERIFIED |
83
+ | FS-E150 | Backups require billing to be enabled on the project. | <https://docs.cloud.google.com/firestore/native/docs/backups> | Back up and restore data: "Make sure that billing is enabled for your Google Cloud project." | 2026-11-08 | VERIFIED |
84
+ | FS-E151 | In-place restore requires downtime between deleting the database and the restore completing. | <https://docs.cloud.google.com/firestore/native/docs/restore-in-place> | Perform an in-place restore operation: "This process requires downtime between the moment you delete the database and when the restore operation completes." | 2026-11-08 | VERIFIED |
85
+ | FS-E152 | Multi-region databases provide 99.999 percent availability and regional databases provide 99.99 percent. | <https://docs.cloud.google.com/firestore/native/docs/disaster-recovery> | Plan disaster recovery: "Multi-region databases maximize the availability and durability of databases by providing 99.999% availability." | 2026-11-08 | VERIFIED |
86
+ | FS-E153 | Beyond 14 weeks, a PITR export can archive the whole database to Cloud Storage indefinitely. | <https://docs.cloud.google.com/firestore/native/docs/disaster-recovery> | Plan disaster recovery: "you can use PITR to create an export of your entire database and" | 2026-11-08 | VERIFIED |
87
+ | FS-E154 | Standard edition bills documents and index entries read, with a minimum of one document read for aggregation queries that read no index entries. | <https://cloud.google.com/firestore/pricing> | Firestore Standard edition pricing: "For aggregation queries that read 0 index entries, there is a minimum charge of one document read." | 2026-11-08 | VERIFIED |
88
+ | FS-E155 | The api/request_latencies metric gives latency distributions across all completed requests. | <https://docs.cloud.google.com/firestore/native/docs/understand-performance-monitoring> | Understand performance monitoring in Firestore: "metric provides latency distributions across all completed requests." | 2026-11-08 | VERIFIED |
89
+ | FS-E156 | document/ttl_deletion_count counts documents deleted by TTL policies, which document/delete_ops_count excludes. | <https://docs.cloud.google.com/firestore/native/docs/understand-performance-monitoring> | Understand performance monitoring in Firestore: "Total count of documents deleted by TTL services." | 2026-11-08 | VERIFIED |
90
+ | FS-E157 | index/write_count can be contrasted with document/write_ops_count to understand index fanout. | <https://docs.cloud.google.com/firestore/native/docs/understand-performance-monitoring> | Understand performance monitoring in Firestore: "Index write rates can be contrasted with the" | 2026-11-08 | VERIFIED |
91
+ | FS-E158 | ABORTED also signals contention between overlapping transactions on the same data. | <https://docs.cloud.google.com/firestore/native/docs/understand-error-codes> | Understand error codes: "Aborted due to cross-transaction contention. This occurs when multiple" | 2026-11-08 | VERIFIED |
92
+ | FS-E159 | Role roles/datastore.backupsAdmin gives full access to backups in a location. | <https://docs.cloud.google.com/firestore/native/docs/security/iam> | Identity and Access Management (IAM): "Full access to backups in a Firestore location." | 2026-11-08 | VERIFIED |
93
+ | FS-E160 | Tags can be added when a database is created. | <https://docs.cloud.google.com/firestore/native/docs/tags> | Create and manage tags: "You can add tags at the time of creating databases." | 2026-11-08 | VERIFIED |
94
+ | FS-E161 | CMEK availability is gated behind an access request form. | <https://docs.cloud.google.com/firestore/native/docs/cmek> | Customer-managed encryption keys (CMEK): "Note: For information about access to this release, see the" | 2026-11-08 | VERIFIED |
95
+ | FS-E162 | Cloud Audit Logs for Firestore track administrative and data-access operations on resources. | <https://docs.cloud.google.com/firestore/native/docs/audit-logging> | Firestore audit logging information: "Cloud Audit Logs for Firestore let you track administrative and" | 2026-11-08 | VERIFIED |
96
+ | FS-E163 | Methods needing DATA_READ, DATA_WRITE or ADMIN_READ permissions generate Data Access audit logs. | <https://docs.cloud.google.com/firestore/native/docs/audit-logging> | Firestore audit logging information: "Methods that require an IAM permission with the type property value of DATA_READ" | 2026-11-08 | VERIFIED |
97
+ | FS-E202 | Backups of a MongoDB-compatible database exclude database TTL policies. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/backups> | Back up and restore data: "A backup does not contain database time to live policies." | 2026-11-08 | VERIFIED |
98
+ | FS-E203 | Each database can have at most one daily and one weekly backup schedule, and the time of day cannot be configured. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/backups> | Back up and restore data: "For each database, you can configure up to one daily backup schedule and up to one weekly backup schedule." | 2026-11-08 | VERIFIED |
99
+ | FS-E204 | Backups support a maximum retention period of 14 weeks. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/disaster-recovery> | Plan disaster recovery: "Backups support a maximum retention period of 14 weeks." | 2026-11-08 | VERIFIED |
100
+ | FS-E205 | A restore writes the backup into a new database. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/backups> | Back up and restore data: "A restore operation writes the data from a backup to a new Firestore with MongoDB compatibility" | 2026-11-08 | VERIFIED |
101
+ | FS-E206 | Backups require billing to be enabled on the project. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/backups> | Back up and restore data: "Make sure that billing is enabled for your Google Cloud project." | 2026-11-08 | VERIFIED |
102
+ | FS-E207 | After a restore, TTL policies must be reapplied because they are not included in backups or reapplied automatically. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/backups> | Back up and restore data: "TTL policies are not included in backups and are not automatically reapplied to restored databases." | 2026-11-08 | VERIFIED |
103
+ | FS-E208 | Starting an in-place restore permanently loses the original database and cannot be undone. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/restore-in-place> | Perform an in-place restore operation: "Once you start the in-place restore process, the original database is permanently lost, and you can't undo this operation." | 2026-11-08 | VERIFIED |
104
+ | FS-E209 | In-place restore requires downtime between deleting the database and the restore completing. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/restore-in-place> | Perform an in-place restore operation: "This process requires downtime between the moment you delete the database and when the restore operation completes." | 2026-11-08 | VERIFIED |
105
+ | FS-E210 | PITR is disabled by default and keeps minute-granularity versions. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/pitr> | Point-in-time recovery (PITR) overview: "The data is stored at a minute granularity and you can recover data at the same granularity." | 2026-11-08 | VERIFIED |
106
+ | FS-E211 | PITR data is retained for 7 days. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/pitr> | Point-in-time recovery (PITR) overview: "PITR data is retained for 7 days in the PITR window." | 2026-11-08 | VERIFIED |
107
+ | FS-E212 | PITR data can be cloned or exported for any whole-minute timestamp within the past seven days. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/pitr> | Point-in-time recovery (PITR) overview: "You can clone or export PITR data where the timestamp" | 2026-11-08 | VERIFIED |
108
+ | FS-E213 | Regional databases replicate synchronously across at least three zones. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/disaster-recovery> | Plan disaster recovery: "Regional databases synchronously replicate data across at least three zones." | 2026-11-08 | VERIFIED |
109
+ | FS-E214 | Multi-region databases replicate synchronously across five zones in three regions (two serving regions and one witness region). | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/disaster-recovery> | Plan disaster recovery: "Multi-region databases synchronously replicate data across five zones in three regions with two serving regions and one witness region." | 2026-11-08 | VERIFIED |
110
+ | FS-E215 | Multi-region databases provide 99.999 percent availability and regional databases provide 99.99 percent. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/disaster-recovery> | Plan disaster recovery: "Multi-region databases maximize the availability and durability of databases by providing 99.999% availability." | 2026-11-08 | VERIFIED |
111
+ | FS-E216 | Replication is automatic and needs no extra configuration or provisioning. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/disaster-recovery> | Plan disaster recovery: "Firestore with MongoDB compatibility automatically handles replication for you and doesn't require" | 2026-11-08 | VERIFIED |
112
+ | FS-E217 | Documented PITR recovery objectives: recovery time objective of 0 and recovery point objective of 1 minute. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/disaster-recovery> | Plan disaster recovery: "recovery time objective (maximum time for recovery) of 0. The recovery point objective (maximum possible data loss) is 1 minute." | 2026-11-08 | VERIFIED |
113
+ | FS-E218 | Cloning recovers from a point in time up to seven days back with PITR enabled and up to one hour back without it. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/disaster-recovery> | Plan disaster recovery: "If PITR is enabled, you can clone from up to seven days in the past." | 2026-11-08 | VERIFIED |
114
+ | FS-E219 | Supported multi-region locations are eur3, nam5 and nam7; the location cannot be changed after the database is provisioned. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/locations> | Firestore with MongoDB compatibility locations: "Be aware that once you provision a database, you cannot change its location setting." | 2026-11-08 | VERIFIED |
115
+ | FS-E220 | Enterprise edition billing includes read units processed in 4 KiB tranches (documents or indexes). | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "representing the data processed (documents or indexes) when you read data from your database, calculated in 4 KiB tranches." | 2026-11-08 | VERIFIED |
116
+ | FS-E221 | Enterprise edition billing includes write units processed in 1 KiB tranches. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "representing the data processed when you write data into your database, calculated in 1 KiB tranches." | 2026-11-08 | VERIFIED |
117
+ | FS-E222 | Enterprise edition billing includes event units for data in each event, in 4 KiB tranches. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "represents the data included in each Event, calculated in 4 KiB tranches." | 2026-11-08 | VERIFIED |
118
+ | FS-E223 | Real-time update units are for real-time updates requested through the Native mode client libraries, so they do not apply to MongoDB-compatible access. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "representing real-time updates requested through the Firestore in Native mode client libraries" | 2026-11-08 | VERIFIED |
119
+ | FS-E224 | Enterprise edition bills storage including metadata and index overhead, and network bandwidth. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "Database storage size You are charged for the amount of data that you store in Firestore, including storage overhead." | 2026-11-08 | VERIFIED |
120
+ | FS-E225 | Index entries written are charged as write units on Enterprise edition. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "Creating a new document is charged based on the size of the document created and the size of the index entries being written." | 2026-11-08 | VERIFIED |
121
+ | FS-E226 | Managed deletes, PITR data, backup data, restore operations and clone operations include no free usage. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "The following operations and features do not include free usage:" | 2026-11-08 | VERIFIED |
122
+ | FS-E227 | Backup storage is billed when backups are enabled. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "you are charged for the storage of your database backups. The storage size for a backup is equal to the storage size of the database when the backup was taken." | 2026-11-08 | VERIFIED |
123
+ | FS-E228 | Change stream storage is billed on consumed storage including captured change events and the retention period. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "which includes the size of each captured change event along with the configured retention period for the event." | 2026-11-08 | VERIFIED |
124
+ | FS-E229 | Enterprise edition bills network bandwidth used by requests. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "You are charged for the network bandwidth used by your Firestore Enterprise edition requests, as shown in the following sections." | 2026-11-08 | VERIFIED |
125
+ | FS-E230 | PITR storage has no free tier and requires billing. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/pitr> | Point-in-time recovery (PITR) overview: "PITR storage doesn't have a free tier and you must have billing enabled if you want to use PITR." | 2026-11-08 | VERIFIED |
126
+ | FS-E231 | Cloud Monitoring resource firestore.googleapis.com/Database gives breakdowns by project, location and database_id for MongoDB-compatible databases. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-monitoring-dashboard> | Monitor databases with Cloud Monitoring: "Monitored resource type that provides breakdowns for project" | 2026-11-08 | VERIFIED |
127
+ | FS-E232 | The api/request_latencies service runtime metric gives latency distributions across completed requests. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-monitoring-dashboard> | Monitor databases with Cloud Monitoring: "metric provides latency distributions across all completed requests." | 2026-11-08 | VERIFIED |
128
+ | FS-E233 | Document operation metrics (document/delete_ops_count, document/read_ops_count, document/write_ops_count) show read-heavy versus write-heavy usage. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-monitoring-dashboard> | Monitor databases with Cloud Monitoring: "The following metrics can be used to understand whether your database is read heavy or write heavy, and the rate of new documents versus deleted documents." | 2026-11-08 | VERIFIED |
129
+ | FS-E234 | Billing metrics (api/billable_read_units, api/billable_write_units, document/billable_managed_delete_write_units) exclude administrator operations such as indexing, import, export and bulk delete. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-monitoring-dashboard> | Monitor databases with Cloud Monitoring: "These metrics don't include billing from administrator operations (indexing, import, export, and bulk delete)." | 2026-11-08 | VERIFIED |
130
+ | FS-E235 | index/write_count can be contrasted with document/write_ops_count to understand index fanout. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-monitoring-dashboard> | Monitor databases with Cloud Monitoring: "Index write rates can be contrasted with the" | 2026-11-08 | VERIFIED |
131
+ | FS-E236 | TTL metrics document/ttl_deletion_count and document/ttl_expiration_to_deletion_delays monitor TTL policy enforcement. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-monitoring-dashboard> | Monitor databases with Cloud Monitoring: "The TTL metrics for Firestore with MongoDB compatibility metrics are used to" | 2026-11-08 | VERIFIED |
132
+ | FS-E237 | The Monitoring page provides predefined dashboards: Request Latencies (P50 and P99), Response Codes and Query stats (P50). | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-monitoring-dashboard> | Monitor databases with Cloud Monitoring: "The Monitoring page in the Firestore section of the Google Cloud console includes predefined monitoring dashboards such as" | 2026-11-08 | VERIFIED |
133
+ | FS-E238 | Documented example alert: a latency alerting policy checks p99 latency over a 5 minute rolling window and fires when it stays above 250 ms for 5 minutes. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-monitoring-dashboard> | Monitor databases with Cloud Monitoring: "The alerting policy checks p99 latency over a 5 minute rolling window." | 2026-11-08 | VERIFIED |
134
+ | FS-E239 | The usage dashboard is an estimate; the billing report takes precedence over it. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-monitoring-dashboard> | Monitor databases with Cloud Monitoring: "In all cases of discrepancy, the billing report takes precedence over the usage dashboard." | 2026-11-08 | VERIFIED |
135
+ | FS-E240 | Aborted (112) signals contention on documents or between overlapping transactions. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/understand-error-codes> | Understand error codes: "Aborted due to cross-transaction contention. This occurs when multiple" | 2026-11-08 | VERIFIED |
136
+ | FS-E241 | DeadlineExceeded (262) occurs when an operation exceeds the 60 second default deadline. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/understand-error-codes> | Understand error codes: "An increase in latency caused an operation to take longer than the deadline (60 seconds by default) to complete." | 2026-11-08 | VERIFIED |
137
+ | FS-E242 | InvalidArgument (2) is returned when an index entry exceeds 7.5 KiB; this is a limit and not an adjustable quota. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/understand-error-codes> | Understand error codes: "You cannot exceed this limit and it's not a quota that can be adjusted." | 2026-11-08 | VERIFIED |
138
+ | FS-E243 | Sustained high concurrent operations on a single document can hotspot because Firestore cannot split a key range below one document. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/understand-reads-writes-scale> | Understand reads and writes at scale: "high and sustained volumes of concurrent operations on a single document may lead to a hotspot on that document." | 2026-11-08 | VERIFIED |
139
+ | FS-E244 | Indexing monotonically increasing or decreasing values such as timestamps can cause hotspots at high read and write rates. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/understand-reads-writes-scale> | Understand reads and writes at scale: "Indexing fields with monotonically increasing/decreasing values, such as timestamps, can lead to hotspots which affect latency for applications with high read and write rates." | 2026-11-08 | VERIFIED |
140
+ | FS-E245 | Ramping traffic up too fast on a collection may cause high latency or deadline exceeded errors while splits adjust. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/understand-reads-writes-scale> | Understand reads and writes at scale: "Splitting storage and load takes time, and ramping up traffic too fast may cause high latency or deadline exceeded errors" | 2026-11-08 | VERIFIED |
141
+ | FS-E246 | Transactions are limited to 270 seconds with a 60-second idle expiration, and a query has a 128 MiB memory limit. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/quotas> | Quotas and limits: "Time limit for a transaction 270 seconds, with a 60-second idle expiration time" | 2026-11-08 | VERIFIED |
142
+ | FS-E247 | A document may have at most 40,000 index entries, and the index entries of a document may total at most 8 MiB. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/quotas> | Quotas and limits: "Maximum sum of the sizes of a document's index entries 8 MiB" | 2026-11-08 | VERIFIED |
143
+ | FS-E248 | Drivers must connect with TLS and must disable retryable writes, which are not supported. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/connect> | Authenticate and connect to a database: "Drivers must connect with SSL enabled. Drivers must disable retryable writes." | 2026-11-08 | VERIFIED |
144
+ | FS-E249 | Data-plane MongoDB operations map to datastore.* IAM permissions (for example Find needs datastore.entities.get and datastore.entities.list). | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/security/iam> | Identity and Access Management (IAM): "GetMore The same permissions that were required by the call that created the cursor." | 2026-11-08 | VERIFIED |
145
+ | FS-E250 | Role roles/datastore.user grants read/write access to data in a database and is intended for application developers and service accounts. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/security/iam> | Identity and Access Management (IAM): "Read/write access to data in a Firestore database. Intended for application developers and service accounts." | 2026-11-08 | VERIFIED |
146
+ | FS-E251 | Role roles/datastore.userCredsAdmin gives full access to user credentials in a database. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/security/iam> | Identity and Access Management (IAM): "Full access to user credentials in a Firestore database." | 2026-11-08 | VERIFIED |
147
+ | FS-E252 | Firestore caches IAM permissions for 5 minutes, so a role change takes up to 5 minutes to take effect. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/security/iam> | Identity and Access Management (IAM): "Firestore caches IAM permissions for 5 minutes, so it takes up to 5 minutes for a role change to become effective." | 2026-11-08 | VERIFIED |
148
+ | FS-E253 | IAM Conditions can define and enforce conditional access control for Firestore roles. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/security/iam> | Identity and Access Management (IAM): "You can use IAM Conditions to define and enforce conditional access control." | 2026-11-08 | VERIFIED |
149
+ | FS-E254 | A new SCRAM user credential has no permissions until an IAM role such as roles/datastore.user is granted for the database. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/connect> | Authenticate and connect to a database: "By default, this new user credential does not have any permissions." | 2026-11-08 | VERIFIED |
150
+ | FS-E255 | Role roles/datastore.restoreAdmin restores a backup into a new database and also allows creating new databases. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/security/iam> | Identity and Access Management (IAM): "Ability to restore a Firestore backup into a new database. This role also gives the ability to create new databases, not necessarily by restoring from a backup." | 2026-11-08 | VERIFIED |
151
+ | FS-E256 | Tags are key-value pairs on Google Cloud resources that can conditionally allow or deny policies, for example conditional IAM grants. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/tags> | Create and manage tags: "You can use tags to conditionally allow or deny policies based on whether a resource has a specific tag." | 2026-11-08 | VERIFIED |
152
+ | FS-E257 | Attaching tags to databases requires the Datastore Owner role (roles/datastore.owner). | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/tags> | Create and manage tags: "To attach tags to Firestore with MongoDB compatibility instances, you need the Datastore Owner role" | 2026-11-08 | VERIFIED |
153
+ | FS-E258 | Tags can be added when a database is created. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/tags> | Create and manage tags: "You can add tags at the time of creating databases." | 2026-11-08 | VERIFIED |
154
+ | FS-E259 | Tags can be added to existing databases through tag bindings. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/tags> | Create and manage tags: "To add a tag to existing databases, follow these steps:" | 2026-11-08 | VERIFIED |
155
+ | FS-E260 | The service encrypts all data before it is written to disk, with no setup or configuration required. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/server-side-encryption> | Server-side encryption: "automatically encrypts all data before it is written to disk." | 2026-11-08 | VERIFIED |
156
+ | FS-E261 | Data in transit over the Internet is protected with Transport Layer Security (TLS). | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/server-side-encryption> | Server-side encryption: "To protect your data as it travels over the Internet during read and write operations, we use Transport Layer Security (TLS)." | 2026-11-08 | VERIFIED |
157
+ | FS-E262 | CMEK can be enabled only on new databases at creation time. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/cmek> | Customer-managed encryption keys (CMEK): "You can enable CMEK only on new databases, and you must enable it when you create the database." | 2026-11-08 | VERIFIED |
158
+ | FS-E263 | The key of a CMEK-protected database cannot be changed but can be rotated, enabled and disabled. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/cmek> | Customer-managed encryption keys (CMEK): "You can't change a key for a CMEK-protected database. You can rotate, enable, and disable keys." | 2026-11-08 | VERIFIED |
159
+ | FS-E264 | The default maximum number of CMEK databases per project is 0 because the feature is behind an allowlist. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/quotas> | Quotas and limits: "By default the quota is 0 because this feature is behind an allowlist." | 2026-11-08 | VERIFIED |
160
+ | FS-E265 | The Cloud KMS key location must match the location of the database. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/use-cmek> | Use customer-managed encryption keys (CMEK): "The Cloud KMS key location must be the same as the" | 2026-11-08 | VERIFIED |
161
+ | FS-E266 | With CMEK, data in transit or in memory and database metadata remain under Google default encryption. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/cmek> | Customer-managed encryption keys (CMEK): "The following data types are encrypted with Google default encryption and not by the CMEK key:" | 2026-11-08 | VERIFIED |
162
+ | FS-E267 | Restricting the Firestore API service in a VPC Service Controls perimeter also restricts the bundled Datastore and Key Visualizer API services. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/securing-with-vpc-sc> | VPC Service Controls: "service in a perimeter, the perimeter also restricts the" | 2026-11-08 | VERIFIED |
163
+ | FS-E268 | Using restricted VIP requires configuring connectivity to the VIP domain used by the MongoDB-compatible service, which is VPC Service Controls compliant. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/securing-with-vpc-sc> | VPC Service Controls: "To use Firestore with MongoDB compatibility with restricted VIP, you must configure connectivity to the VIP domain used by Firestore with MongoDB compatibility." | 2026-11-08 | VERIFIED |
164
+ | FS-E269 | A VM without an external IP address can reach the service by enabling Private Google Access on its subnet. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/configure-private-google-access> | Configure Private Google Access in Firestore with MongoDB compatibility: "You can allow these VMs to connect to the" | 2026-11-08 | VERIFIED |
165
+ | FS-E270 | The default and VIP domains support only the MongoDB protocol on port 443. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/configure-private-google-access> | Configure Private Google Access in Firestore with MongoDB compatibility: "support only the MongoDB protocol on port 443." | 2026-11-08 | VERIFIED |
166
+ | FS-E271 | For Private Google Access the public restricted.firestore.goog records cannot be used; a private DNS zone and records must be created. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/configure-private-google-access> | Configure Private Google Access in Firestore with MongoDB compatibility: "However, you can't use the public records when you configure Private Google Access. You must create a private DNS zone and records." | 2026-11-08 | VERIFIED |
167
+ | FS-E272 | The default domain firestore.goog reaches the service through public IP addresses and needs no special DNS configuration. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/configure-private-google-access> | Configure Private Google Access in Firestore with MongoDB compatibility: "You access the Firestore with MongoDB compatibility service through its public IP" | 2026-11-08 | VERIFIED |
168
+ | FS-E273 | Import and export need the Firestore service agent for full VPC Service Controls egress protection. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/securing-with-vpc-sc> | VPC Service Controls: "requires additional configuration to get full egress protection on import and export operations." | 2026-11-08 | VERIFIED |
169
+ | FS-E274 | Audit logging is configured with service name datastore.googleapis.com, which covers firestore.googleapis.com. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/audit-logging> | Audit logging information: "When configuring audit logging, use the service name datastore.googleapis.com" | 2026-11-08 | VERIFIED |
170
+ | FS-E275 | Methods needing an ADMIN_WRITE permission generate Admin Activity audit logs. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/audit-logging> | Audit logging information: "Methods that require an IAM permission with the type property value of ADMIN_WRITE generate" | 2026-11-08 | VERIFIED |
171
+ | FS-E276 | Methods needing DATA_READ, DATA_WRITE or ADMIN_READ permissions generate Data Access audit logs. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/audit-logging> | Audit logging information: "Methods that require an IAM permission with the type property value of DATA_READ" | 2026-11-08 | VERIFIED |
172
+ | FS-E277 | MongoDB data-plane methods (Find, Aggregate, Insert, Update, Delete and others) are listed as DATA_READ or DATA_WRITE audit log methods. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/audit-logging> | Audit logging information: "google.firestore.v1.MongoDBCompatible.EndSessions google.firestore.v1.MongoDBCompatible.KillCursors DATA_WRITE google.firestore.v1.MongoDBCompatible.Insert google.firestore.v1.MongoDBCompatible.Update google.firestore.v1.MongoDBCompatible.Delete google.firestore.v1.MongoDBCompatible.FindAndModify google.firestore.v1.MongoDBCompatible.CreateCollection" | 2026-11-08 | VERIFIED |
173
+ | FS-E278 | The AuditLog authenticationInfo field identifies the caller and requestMetadata.callerIp gives the caller IP address. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/audit-logging> | Audit logging information: "Audit Log entries include information about the identity that performed the" | 2026-11-08 | VERIFIED |
174
+ | FS-E279 | A restore is billed on the size of the backup. | <https://cloud.google.com/firestore/enterprise/pricing> | Firestore Enterprise edition pricing: "When you perform a restore operation, Firestore measures the size of the backup for the restore operation." | 2026-11-08 | VERIFIED |
175
+ | FS-E280 | Clients can authenticate with a SCRAM username and password, a Compute Engine service account, a Cloud Run service account, or the Google Auth Library. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/connect> | Authenticate and connect to a database: "Username and password (SCRAM) Compute Engine service account Cloud Run service account Google Auth Library" | 2026-11-08 | VERIFIED |
176
+ | FS-E281 | A backup resides in the same location as the source database. | <https://docs.cloud.google.com/firestore/mongodb-compatibility/docs/backups> | Back up and restore data: "A backup resides in the same location as the source database." | 2026-11-08 | VERIFIED |
177
+ | FS-E901 | gcloud auth list is a read-only listing of credentialed accounts and shows which is active (identity check). | <https://docs.cloud.google.com/sdk/gcloud/reference/auth/list> | NAME: "gcloud auth list - lists credentialed accounts" | 2026-11-09 | VERIFIED |
178
+ | FS-E902 | gcloud config list shows the active configuration properties, including account and project (identity check). | <https://docs.cloud.google.com/sdk/gcloud/reference/config/list> | NAME: "gcloud config list - list Google Cloud CLI properties for the currently active configuration" | 2026-11-09 | VERIFIED |
179
+ | FS-E903 | gcloud firestore databases describe --database reads one database's metadata (default database when omitted). | <https://docs.cloud.google.com/sdk/gcloud/reference/firestore/databases/describe> | NAME: "gcloud firestore databases describe - describes information about a Cloud Firestore database" | 2026-11-09 | VERIFIED |
180
+ | FS-E904 | gcloud firestore backups schedules list --database lists the backup schedules of a database. | <https://docs.cloud.google.com/sdk/gcloud/reference/firestore/backups/schedules/list> | NAME: "gcloud firestore backups schedules list - lists backup schedules under a Cloud Firestore database" | 2026-11-09 | VERIFIED |
181
+ | FS-E905 | gcloud firestore backups list takes an optional --location and lists backups. | <https://docs.cloud.google.com/sdk/gcloud/reference/firestore/backups/list> | NAME: "gcloud firestore backups list - list backups available to Cloud Firestore" | 2026-11-09 | VERIFIED |
182
+ | FS-E906 | gcloud projects get-iam-policy reads a project's IAM policy. | <https://docs.cloud.google.com/sdk/gcloud/reference/projects/get-iam-policy> | NAME: "gcloud projects get-iam-policy - get IAM policy for a project" | 2026-11-09 | VERIFIED |
183
+ | FS-E907 | gcloud logging read reads log entries with a filter, --freshness, --limit and --project flags, for audit-log evidence. | <https://docs.cloud.google.com/sdk/gcloud/reference/logging/read> | DESCRIPTION: "gcloud logging read reads log entries. Log entries matching log-filter are returned in order of decreasing timestamps" | 2026-11-09 | VERIFIED |
184
+ | FS-E908 | gcloud resource-manager tags bindings list --parent lists tag bindings on a full resource name; --effective shows inherited bindings. | <https://docs.cloud.google.com/sdk/gcloud/reference/resource-manager/tags/bindings/list> | NAME: "gcloud resource-manager tags bindings list - lists TagBindings bound to the specified resource" | 2026-11-09 | VERIFIED |
185
+ | FS-E909 | gcloud monitoring policies list lists alerting policies in the active project. | <https://docs.cloud.google.com/sdk/gcloud/reference/monitoring/policies/list> | NAME: "gcloud monitoring policies list - list alerting policies" | 2026-11-09 | VERIFIED |
186
+ | FS-E910 | Firestore Admin API Database resource has pointInTimeRecoveryEnablement, deleteProtectionState, cmekConfig, locationId, type, databaseEdition and tags. | <https://docs.cloud.google.com/firestore/docs/reference/rest/v1/projects.databases> | Fields: "Whether to enable the PITR feature on this database." | 2026-11-09 | VERIFIED |
187
+ | FS-E911 | Firestore Admin API BackupSchedule resource has dailyRecurrence or weeklyRecurrence and retention. | <https://docs.cloud.google.com/firestore/docs/reference/rest/v1/projects.databases.backupSchedules> | Fields: "For a schedule that runs weekly on a specific day." | 2026-11-09 | VERIFIED |
188
+ | FS-E912 | The gcloud auth/impersonate_service_account property makes API requests run as another service account instead of the active account. | <https://docs.cloud.google.com/sdk/gcloud/reference/topic/configurations> | auth, impersonate_service_account: "While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account." | 2026-11-11 | VERIFIED |
189
+ | FS-E913 | The gcloud auth/access_token_file property authenticates with an access token and ignores the active account's credentials. | <https://docs.cloud.google.com/sdk/gcloud/reference/topic/configurations> | auth, access_token_file: "Use this property to authenticate gcloud with an access token. The credentials of the active account (if it exists) will be ignored." | 2026-11-11 | VERIFIED |
190
+ | FS-E914 | Firestore API audit log entries carry the service name firestore.googleapis.com; datastore.googleapis.com is the name used to configure audit logging. | <https://docs.cloud.google.com/firestore/native/docs/audit-logging> | Notes: "Once configured, logs for the Firestore API include the the service name firestore.googleapis.com" | 2026-11-11 | VERIFIED |