mygopher-conventions

Folder structure and data conventions are enforced by applying defined directory responsibilities and YAML frontmatter schemas. This prevents cross-skill interference and ensures all business data routing adheres to standardized file organization rules.

Organizing vendor data using YAML schemas involves placing entity files in designated directories like `vendors/` with proper frontmatter formatting. Numerical data is routed separately to the Sheets service to maintain consistent data organization.

Data routing directs business information to designated storage locations based on data type. Entity files use YAML structures, numerical data goes to the Sheets service, and native memory logs capture operational data, preventing silos and ensuring consistency.

YAML frontmatter is required for all entity files to enforce schema consistency within the workflow management system. Adhering to defined YAML structures ensures that data organization rules are met for all business data operations.

Cross-skill interference occurs when folder ownership boundaries are not clearly delineated. Establishing explicit directory responsibilities for each skill prevents unauthorized data modifications and maintains consistent data organization across the system.

Managing multiple business entity types is supported by applying defined data routing rules and folder ownership to each entity category. This ensures specific data formats and storage locations are maintained across diverse business operations.