write-rich-descriptions

You create machine-readable architecture documentation by defining system-model metadata blocks for business context and Markdown tables for deployment details, ensuring elements are queryable while remaining human-friendly.

The best way to structure deployment descriptions is using a single Markdown table per element in your deployment model to present network, hardware, and service details in a readable format.

Metadata blocks work by capturing business context and technical details for containers and components in a structured format, enabling machine-readable queries across your architecture documentation.

Yes, you can use arrays for multi-valued fields and cross-references to link related resources, avoiding duplication and keeping documentation consistent and navigable across elements.

To document a new service, describe it using a metadata block in system-model.c4, then add a deployment description in deployment.c4 with a single Markdown table and links to related resources.

You should avoid using multiple Markdown tables per element in deployment descriptions, as the recommended approach enforces a single deployment table per element to maintain readable and consistent documentation.