11 docs tagged with "migration"

Rename entity_type 'automation' to 'workload' to resolve naming collisions with the broader 'Automation Definition' concept and align with cloud-native vocabulary

Migrate documentation site from MkDocs Material to Docusaurus 3

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).

Comparison of documentation frameworks — MkDocs Material vs Docusaurus vs Nextra vs Starlight vs Mintlify vs VitePress. Web-research-validated March 2026.

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

One-time migration plan — create new SecurityV0 Notion workspace with correct structure, migrate content from existing workspaces

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...

Analyzes whether the current TypeScript/Node.js stack is sufficient for the processing pipeline at scale

Plan to migrate the custom @ai-metadata HTML-comment format to standard Obsidian YAML frontmatter, unlocking the properties panel, graph view, Dataview queries, backlinks, and tag browsing.

Complete implementation plan for renaming entity_type 'automation' to 'workload' across platform, connectors, UI, database, and documentation

Phased implementation plan for adopting WorkOS as the identity provider, rebuilding tenant/user/membership model, URL-scoping tenants to /t/:slug, and establishing the SecurityV0 super-admin pattern. Implements ADR-016 and ADR-017.