ADR-004: Import-by-Type Connector Architecture
Decision to replace pre-linked ExecutionChain objects with flat DiscoveredEntities + EdgeResolver, simplifying connector discovery and moving relationship resolution to an explicit step
Decision to replace pre-linked ExecutionChain objects with flat DiscoveredEntities + EdgeResolver, simplifying connector discovery and moving relationship resolution to an explicit step
Add 4 new typed edge types (CALLS, INVOKES, USES, AUTHENTICATES_AS) to model the execution chain across reclassified entity types
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...
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
First-principles redesign of SecurityV0's entity type system
Canonical definitions for SecurityV0 domain terminology — NHI, execution chains, entity types (identity, workload, connection, credential, owner), relationship types (RUNS_AS, CALLS, INVOKES, USES,...
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
Deep analysis of how autonomous execution chains (ServiceNow Business Rules, Flow Designer flows, scheduled jobs) map to Veza OAA concepts
6-agent analysis on mapping autonomous execution flows to OAA (Open Authorization API) concepts
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