ADR-010: Workload Entity Type Rename
Rename entity_type 'automation' to 'workload' to resolve naming collisions with the broader 'Automation Definition' concept and align with cloud-native vocabulary
Rename entity_type 'automation' to 'workload' to resolve naming collisions with the broader 'Automation Definition' concept and align with cloud-native vocabulary
Composed analysis turning founder W1 feedback into an architecture: Authority Path is the durable object, Exposure is a time-bound finding on a path, and Risk Clusters group related exposures.
Round 1 team-synthesis from the 5-agent automation-analysis (PO, Architect, CISO, Integrator, Developer): agreed 4-tier classification of ServiceNow automations and the 'ingest all, filter in UI' mandate.
Azure identity-plane integration specification supporting W1 (Agentic AI Exposure Discovery & Assessment)
W1 Gap 1 plan: align the four exposure-aggregation endpoints (posture summary, risk-clusters, exposures list, exposure detail) with the W1 spec so the four UI pages render correct demo data.
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...
Single source of truth for all SecurityV0 implementation plans and their status. Updated as work progresses; lists active sprint, completed work, and remaining effort.
Product owner documentation including vision, wedge definitions, and progress tracking for SecurityV0 platform
W1 Gap 2 plan: replace static one-size-fits-all remediation strings in evidence packs with context-aware content that names entities, roles, resources, sensitivity levels, and source systems.
W1 Gap 3 plan: enrich the scope-drift Finding Detail page so it tells the 'so what' story (which roles were added, what they grant, what changed) rather than only stating drift occurred.
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)
Defines how the ServiceNow integration contributes first-party artifacts to W1 (Agentic AI Exposure Discovery & Assessment) for deterministic exposure evaluation
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
CISO-lens analysis of how the 4-concept separation model (AutomationDefinition, AutomationTopology, AutomationRun, ExecutionEvidenceEvent) aligns with Sergey's W1 product vision and UX specification
Developer-perspective gap analysis mapping the current sv0-platform codebase against Sergey's W1 product vision and UX specification
Product owner analysis of the 4-concept model (docs 06/07) against Sergey's W1 product vision and UX specification
Unified synthesis of 4-perspective analysis (CISO, Product Owner, Developer, Architect) comparing docs 06/07 (definition-vs-runtime separation, naming plan) against Sergey's W1 product vision and U...
Unresolved product and logic questions for W1 Exposure evaluation
W1 (Wedge 1) post-demo gap analysis and sprint-priority alignment derived from Sergey's 2-3 week priorities email. Defines the G1-G6 gap workstreams.
Comprehensive implementation plan synthesizing workload rename, W1 evaluator rules, risk cluster computation, exposure concept, posture summary, and full UX redesign
Defines the user experience for W1 exposure discovery, incorporating prioritized autonomous authority risk clusters, execution activity magnitude, structured evidence presentation, and investigatio...