Files
jhonny-editor/code/docs/recommendations/2026-08-18-round-2/38-metadata-batch-planner.md
T
João Henrique b541f502ba feat: initial commit - Jhonny Editor
- Adicionado estrutura completa do projeto
- Configurado MCP server para Premiere Pro
- Adicionado documentação e skills
- Configurado Gitignore para o projeto
2026-09-08 09:59:31 -04:00

955 B
Executable File
Raw Blame History

Recommendation 38: metadata batch planner

Evidence

Adobe’s production-style metadata sample supports column copy/exchange, batch prefix/suffix/numbering, metadata export, and clip-marker export.

Proposed improvement

Create a bounded metadata plan/preview/apply workflow with explicit namespaces, typed coercion, per-item expected values, conflict detection, and chunked transactions. Default to exporting a rollback artifact before changes.

Acceptance criteria

  • Preview identifies writable fields, collisions, truncation, and no-op edits.
  • Apply requires exact project revision and plan digest.
  • Partial batches return per-item certainty and never retry unknown commits.
  • Sensitive metadata fields are excluded unless explicitly allowlisted.

Adobe’s sample demonstrates a workflow pattern; real project schemas still require host validation.