Migrate

Automating content ingestion and classification is done by scanning external files or stdin, classifying each chunk, and routing it to the correct taxonomy destination. This reduces manual tagging by handling sources like markdown and text files automatically.

Yes, you can import markdown notes and route them to specific destinations. The system classifies ingested chunks into categories like TELOS, Identity, and Knowledge, organizing scattered content into a structured knowledge base with source attribution.

The best way to preserve provenance during content migration is to use an approval workflow that routes and commits chunks with source attribution. This enforces auditable tracking and prevents bulk acceptance of unclear content.

To route cursor-rule outputs into the PAI taxonomy, use the migrate command to scan the source directory, review the proposed classification and routing, and commit trusted chunks with provenance attached.

Yes, the content ingestion workflow prevents bulk acceptance of unclear content. It enforces an approval process that requires reviewing proposed routing before committing chunks, ensuring only verified content enters the taxonomy.

Supported file formats for automated content classification include .md, .markdown, and .txt files. The system also ingests content from stdin or other PAI installations to classify and route chunks into the taxonomy.