ADR-001: MongoDB Only for MVP
Decision to use MongoDB as the single database for SecurityV0 MVP, with Neo4j planned as future scale option
Decision to use MongoDB as the single database for SecurityV0 MVP, with Neo4j planned as future scale option
Decision to store all entity types in a single MongoDB collection with entity_type discriminator
New execution_chains MongoDB collection to persist automation chains as durable, listable entities with stable identity across scans
Serve EU and US clients via per-region MongoDB Atlas clusters with app-side tenant routing instead of a single MongoDB Atlas Global Cluster, with an explicit control-plane / tenant-data-plane split and region-tagged connector API keys to keep all hot-path lookups region-local.
Pick a persistent store for delegated_agent audit log entries. Recommend Grafana Cloud Loki (already adopted by ADR-019, free at pilot scale) for general-purpose audit retention, with a small Mongo audit_logs collection reserved only for the customer-facing 'who did what' query surface once a tenant asks for one.
Index of Architecture Decision Records (ADRs) for SecurityV0 platform
Developer perspective on Round 3 automation-persistence analysis: implementation cost matrix for four chain-persistence options. Recommends Option B (lightweight collection) over Option A (computed view, temporal-query trap).
Detailed phased plan to create a new core SecurityV0 repository from updated architecture docs, incorporating P0/P1 evidence-grade decisions and lessons from the graph-mongo draft
MongoDB schema definition for SecurityV0 including collections (entities, entity_versions, events, baseline_metadata, baseline_entities, execution_evidence, execution_chains, findings, evidence_pac...
How a single global app domain (app.securityv0.com) serves tenants in different regions via per-region MongoDB Atlas clusters with application-side tenant routing — with phased deployment topology, request flow walkthroughs, and cost progression.
System-level architecture defining services, data flow, deployment topology, and security boundaries