vybz-artifact-metadata

To standardize YAML frontmatter for design artifacts, define a strict schema enforcing required fields such as status, type, author, last_updated, and references across all Markdown files. This ensures new artifacts start in a recognized state with proper cross-referencing.

Required metadata fields for vybz design artifacts include status, type, author, last_updated, and references. Enforcing these fields in the YAML frontmatter ensures that designs, intents, bugs, critiques, and blueprints are consistently tagged and discoverable.

To apply consistent metadata schemas to existing Markdown designs, update the YAML frontmatter at the top of each file to conform to the prescribed schema. This standardizes discovery and governance across all artifacts located in .vybz folders.

Yes, you can use YAML frontmatter to govern design artifacts across a workspace by facilitating centralized tagging, auditing, and cross-referencing. Applying a strict schema to all Markdown files in .vybz folders ensures consistent artifact discovery and management.

The best way to organize design artifact metadata in .vybz folders is by enforcing a strict YAML frontmatter schema. This approach defines required fields including status, type, author, last_updated, and references to standardize tagging for designs, intents, bugs, critiques, and blueprints.

Standardizing Markdown frontmatter helps with design artifact discovery because it ensures consistent tagging and governance across the workspace. By enforcing required fields like status, type, author, last_updated, and references, artifacts become easily searchable and auditable.