Folder Curator

A purpose-bound curator for any watched directory. Each arriving file is deterministically classified → renamed → enriched → routed to its home, and every folder stays ordered by document freshness (newest on top). One declarative contract per directory — .curator/taxonomy.yaml — declares that directory's purpose and its categories/rules; the shipped default (assets/taxonomy.default.yaml) is the Automatic AI client/prospect profile. The CLI is the executor — you invoke it, you don't re-implement its rules; when the rules can't decide, you judge in light of the directory's stated purpose.

Operating principles

• Flat categories, labels over nesting. Structure lives in frontmatter (kind, tags), not deep folders. Add a folder only when a whole class of docs earns one.
• The contract is the source of truth. Classification/naming/enrichment rules are data in taxonomy.yaml. Don't hardcode judgments the contract should own — edit the contract (see structure-evolution).
• Deterministic first, judgment second. Run the CLI. It routes confident cases and parks ambiguous ones in the review queue (pipeline-status: new) for you to decide. Only override when you have real evidence.
• Purpose guides judgment. Each curated directory declares a purpose in its contract (and plan echoes it on low-confidence items). When the rules can't classify deterministically, choose what best serves that purpose — never guess mechanically.
• Never fabricate provenance. Preserve existing frontmatter; use unknown/unconfirmed; a newer updated is a relevance signal, not proof of correctness.
• Secrets never get filed. A credential/secret is quarantined and blocked — never renamed-into-place, committed, or synced.

Quick navigation