5 docs tagged with "neo4j"

Decision to use MongoDB as the single database for SecurityV0 MVP, with Neo4j planned as future scale option

Keep Mongo + materialization; freeze new materialized graph stores in favor of read-time composition; add a deterministic predicate-to-seed-set query layer so the graph is queryable/filterable at enterprise scale; bound rendering to a comprehensible node set; and land four operational scale fixes before a Fortune-500 tenant.

Index of Architecture Decision Records (ADRs) for SecurityV0 platform

MongoDB schema definition for SecurityV0 including collections (entities, entity_versions, events, baseline_metadata, baseline_entities, execution_evidence, execution_chains, findings, evidence_pac...

Complete schema mapping analysis for modeling SecurityV0 automation chains against the Veza OAA data model