ADR-006: Entity Type Reclassification
Split autonomous_identity into 4 distinct types (identity, automation, connection, credential) to accurately model non-authenticating artifacts
Split autonomous_identity into 4 distinct types (identity, automation, connection, credential) to accurately model non-authenticating artifacts
Rename entity_type 'automation' to 'workload' to resolve naming collisions with the broader 'Automation Definition' concept and align with cloud-native vocabulary
Deep critical review of SecurityV0 architecture and data model with evidence-grade gaps, risk analysis, and prioritized improvements
Plan to add automated Claude-driven analysis and auto-fix of simple CI failures across the three sv0 repos, with reviewer-agent gating before human merge.
Strategy for reducing false positive automations and improving graph readability at scale
Tracks completed work (evaluator text, UI component rename, glossary), proposed next steps (UI label changes, 4-concept model adoption), and open naming decisions for execution chains and runtime c...
Unified strategy for moving SecurityV0 from manual scans to autonomous operations with built-in cross-validation, observability, and an Azure VM hosting lane — ahead of the MediaPro pilot.
Comprehensive CI/CD strategy for sv0-platform deployment and sv0-connectors scan pipelines, including secrets management evaluation (GitHub Secrets, SOPS+age, Tailscale, Vault, Doppler, self-hosted...
Role-based research synthesis aligned to founder vision and W1 wedge scope, separating automation definition, exposure path, topology, and runtime proof with an implementable W1-first plan
Critical assessment of architecture review suggestions with viability analysis, open question answers, and architectural decisions made
9-type entity system (identity, workload, connection, credential, owner, role, permission, resource, execution_evidence) and execution chains for the SecurityV0 execution/authority graph
Proposal for automating source system provisioning across Azure, AWS, GCP, and ServiceNow using Terraform modules for cloud identity and per-connector Python setup scripts for SaaS configuration
First-principles redesign of SecurityV0's entity type system
Round 5 CISO analysis on what entity type Business Rules, Script Includes, REST Messages, OAuth Profiles, Flow Designer Flows, and Scheduled Jobs should actually be in the SecurityV0 data model
Critical analysis of the current entity_type system
Round 5 critical analysis of entity type classification for automation artifacts (Business Rules, Script Includes, REST Messages, OAuth Profiles, Flow Designer Flows, Scheduled Jobs)
Product-level analysis of whether Business Rules, Script Includes, REST Messages, OAuth Profiles, Flow Designer Flows, and Scheduled Jobs should remain classified as entity_type 'identity' or be re...
6-agent analysis on correct entity typing for automation artifacts
Research and recommendation for giving each Claude Code agent (Alpha, Delta) a distinct identity on GitHub
Consolidated implementation plan incorporating all 5 rounds of analysis plus code review corrections
Infrastructure automation for SecurityV0 — dev environment provisioning, cloud identity setup, and source system configuration
Side-by-side comparison of Gemini, Codex 5.3, and Claude Opus (4-agent team) research on the 4-concept model naming, with areas of agreement, disagreement, and a unified recommendation for Sergey's...
Product Owner analysis of how automation execution chains should be modeled relative to OAA (Open Authorization API) entity types
Complete schema mapping analysis for modeling SecurityV0 automation chains against the Veza OAA data model
Round 4 CISO analysis evaluating how OAA (Open Authorization API) concepts map to SecurityV0's automation chain modeling
Deep analysis of how autonomous execution chains (ServiceNow Business Rules, Flow Designer flows, scheduled jobs) map to Veza OAA concepts
Detailed implementation plan for Phase A0 of Workstream A
Implementation plan for an automated weekly AI incident blog post and LinkedIn pipeline — a separate sv0-intelligence repo feeding content PRs to sv0-website, with future extensibility for multiple automated researchers.
Registry of recurring automations and scheduled routines across SecurityV0 — what runs unattended, when, where, who owns it, and how to pause it
Self-contained research prompt for AI tools to propose a better name for entity_type 'automation' to avoid collision with the broader 'Automation Definition' concept
Defines the ServiceNow automation surface relevant to W1 (Agentic AI Exposure Discovery & Assessment): in-scope automation categories, execution modes, and scope boundaries (surface-level only)
Research on authoritative ServiceNow evidence sources for execution and role changes, deterministic Entra SP to ServiceNow identity linkage, and top autonomous execution types in enterprises
Architectural analysis reconciling doc 06 (4-concept model) and doc 07 (naming plan) with Sergey's W1 product vision, UX spec, and existing 9-entity data model
Product owner analysis of the 4-concept model (docs 06/07) against Sergey's W1 product vision and UX specification
Comprehensive comparison of MVP1 PRD product vision against current platform delivery, identifying structural gaps in UI automation focus, graph visualization, ingestion architecture, and business-...
Complete implementation plan for renaming entity_type 'automation' to 'workload' across platform, connectors, UI, database, and documentation