**Systematic Disambiguation of Autonomous Authority: A Framework for Security v0**
External Gemini research output: framework for systematic disambiguation of autonomous authority and a four-concept data model for security-automation UI naming.
8 docs tagged with "naming"
View all tagsAutomation Naming Separation — Implementation Plan & Open Questions
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...
Research Prompt: What Should We Call the Entity Type Currently Named "automation"?
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
Vision Alignment — Architect Perspective Analysis
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
Vision Alignment Analysis — CISO Perspective on Docs 06/07 vs W1 Product Vision
CISO-lens analysis of how the 4-concept separation model (AutomationDefinition, AutomationTopology, AutomationRun, ExecutionEvidenceEvent) aligns with Sergey's W1 product vision and UX specification
Vision Alignment Analysis — Developer Perspective
Developer-perspective gap analysis mapping the current sv0-platform codebase against Sergey's W1 product vision and UX specification
Vision Alignment Analysis — Product Owner Perspective
Product owner analysis of the 4-concept model (docs 06/07) against Sergey's W1 product vision and UX specification
Vision Alignment Synthesis — Cross-Perspective Recommendations
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...