# BpmnAuthoringGuide
## Properties
**how_to_use** | **Vec<String>** | How to read the exported artifacts. Protocol, not engine semantics. |
**workflow** | **Vec<String>** | The authoring loop, in the order it has to happen. |
**element_support** | [**serde_json::Value**](.md) | `element-support.json`: 35 element kinds with per-kind support status, plus `caveats`, `recognized_tags`, `event_definitions` and `ignored_subtrees`. Read `caveats` first -- it is where a naive generator dies. |
**validation_codes** | [**serde_json::Value**](.md) | `validation-codes.json`: every code the engine's `ValidationError` can return. |
**api_issue_codes** | [**Vec<models::BpmnAuthoringGuideApiIssueCodesInner>**](BpmnAuthoringGuide_api_issue_codes_inner.md) | The codes this API reports that the engine crate cannot, because they need a database -- delegate bindings, form bindings, `calledElement` resolution, task identities, plus `ParseError`. `validation_codes` alone is **not** the complete set of codes a caller sees. |
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)