workspace-ingest

Shape detection automatically identifies v1.x, v2.x, custom-markdown, and generic fallback formats during workspace ingestion. This phased detection mechanism parses source data and generates corresponding JSON substrates without manual configuration.

Yes, you can safely rollback a data migration using undo logging. The process implements copy-first backup safeguards and strict safety checks, preserving original data integrity and enabling idempotent operations to prevent corruption.

The best way to handle file migration conflicts is through automated queuing and conflict handling. This ingestion approach processes file migrations into the workspace structure atomically, ensuring idempotent behavior and safe rollback if conflicts arise.

Yes, workspace ingestion supports custom markdown shapes and generic data dumps. It applies phased shape detection to parse these formats, converting them into structured JSON data substrates like entities.json and aliases.json with atomic writes.

You generate audit logs during workspace onboarding by running the ingestion process with built-in audit trail tracking. It integrates deeply with onboarding flows and produces post-ingest reports detailing the migration and shape detection phases.