AzeMark 2 · AzeForge 0.6.3

AI-authoring contract.

Generate AzeMark language version 2 for AzeForge 0.6.3. Treat the generated grammar as normative and the canonical Sources as executable examples.

Hard rules

1. Emit complete .aze.md Source with azemark: 2 front matter.
2. Use exactly four colons for outer directive fences, :: only for nested figure children, and ---- between headers and bodies.
3. Choose directive fields, enum values, body records, and limits from grammar.json. Do not infer near-miss keys.
4. Use document-scoped kebab-case IDs and declare a target before referring to it when the family resolves declarations in order.
5. Run analyze or validate before render. Correct Source from diagnostic locations and suggestions. Never suppress or rewrite a diagnostic as success.
6. Do not promise TeX rendering unless capabilities advertise the configured adapter. Mermaid and visual formats need the browser capability.
7. Do not use the diagnostic sampler as valid Source. Treat the TeX Source as deployment-dependent.

Machine-readable artifacts

• grammar.jsonAll 26 directives, body schemas, enums, and limits.
• capabilities.jsonFormats, themes, engines, policies, profiles, and security properties.
• version.jsonCompiler, source-language, document-schema, and plugin-schema versions.
• llms.txtCompact routes and authoring rules for retrieval.

Do not invent these facts

The 0.6.3 evidence does not define the complete readable-equation vocabulary, defaults and outputs semantics, full citation or endnote syntax, theme visuals, a complete diagnostic-code catalog, circuit metadata semantics, or future version-transition rules.