17 docs tagged with "execution-chains"

Web UI architecture for SecurityV0 — page specifications for 9-type entity model, component architecture, data fetching patterns, evidence pack rendering, execution chain views, and export capabili...

New execution_chains MongoDB collection to persist automation chains as durable, listable entities with stable identity across scans

Chain (re-)materialization is triggered by sync ingestion (continuous), a deploy-gate one-shot job (when chain-builder code changes), and operator-run recovery — never by the evaluator.

REST API contract for SecurityV0 platform

Index of Architecture Decision Records (ADRs) for SecurityV0 platform

Summary of all architecture-doc changes implementing the 4-type entity reclassification (autonomous_identity → identity / automation / connection / credential) and the four ADRs (006/007/008/009) that record those decisions.

Plan to update architecture docs (01-data-model.md, 03-database.md, 05-connectors.md, glossary.md) with Round 3-5 decisions

Round 3 team-synthesis report: unanimous agreement that the data model needs chain-level temporal tracking, with consensus on a phased execution_chains collection providing stable identity, listability, and audit-ready snapshots.

Product Owner perspective on Round 3 automation-persistence analysis: option scoring across user-story coverage, with a recommendation for 'automation as virtual entity' in Phase 1 plus chain snapshots in Phase 2.

Architect perspective on Round 3 automation-persistence analysis: a lightweight execution_chains collection with versioned snapshots that gives chains stable identity and chain-level temporal tracking without duplicating entity-level temporal machinery.

Developer perspective on Round 3 automation-persistence analysis: implementation cost matrix for four chain-persistence options. Recommends Option B (lightweight collection) over Option A (computed view, temporal-query trap).

CISO perspective on Round 3 automation-persistence analysis: chain-level temporal tracking is compliance-critical (cannot answer 'how did this automation's blast radius change in 90 days' without it).

9-type entity system (identity, workload, connection, credential, owner, role, permission, resource, execution_evidence) and execution chains for the SecurityV0 execution/authority graph

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

Consolidated implementation plan incorporating all 5 rounds of analysis plus code review corrections

Implementation feasibility analysis for aligning SecurityV0's automation chains with OAA's Application/Resource model, examining three mapping approaches with TypeScript types, code impact assessme...

Developer-perspective gap analysis mapping the current sv0-platform codebase against Sergey's W1 product vision and UX specification