PROJECT_NAME Specification
This directory defines observable contracts: inputs, outputs, validation, errors, defaults, compatibility and supported execution profiles. It is the source of truth for behavior; guides explain usage and design records explain why a contract was chosen.
Contents
Add links to completed chapters here. Start a chapter from TEMPLATE.md; the
site excludes authoring templates by default.
| Chapter | Defines |
|---|---|
| Markdown math | Formula syntax, its rendering, the assets and the page loading of markdown.math |
Conventions
MUST and MUST NOT express requirements. SHOULD expresses a recommendation. MAY expresses an allowed choice. Label proposed behavior explicitly. Examples illustrate contracts; pseudocode must be labeled as such.
Implementation status
State which contracts are implemented for each backend, platform or API. Separate planned behavior from released behavior. Record version gates and unsupported operations explicitly rather than promising universal support.