AzeForge

AzeForge compiler and renderer

Technical documents, built from plain text.

AzeForge is the compiler and renderer for AzeMark — a library for both humans and AI agents. Validate structured technical Source, then render HTML, SVG, PNG, or PDF.

Install AzeForgeRead the docs
npm install @aruzone/aze-forge

01 / Capabilities

Compiler contracts instead of plugin guesswork.

The 26-directive grammar comes from the same registered definitions the compiler validates.

  • Readable SourceMarkdown prose and typed AzeMark directives stay in one .aze.md file.
  • Corrective diagnosticsErrors carry codes, severity, locations, suggestions, and optional edits.
  • Deterministic outputThe same valid Source and render options produce byte-identical Artifacts.
  • Fail-closed renderingInvalid Source publishes no partial Artifact and does not replace a previous output.

02 / Use cases

Native structures for technical work.

Use one Source format across quantitative notes, engineering records, software models, and publication-ready documents.

  • Mathematicsequation derivation
  • Scienceformula reaction structure
  • Engineeringcircuit timing control free-body
  • Dataplot chart
  • Geometrygeometry
  • Softwaresequence state entity class
  • Documentstable algorithm statement example bibliography figure callout
  • Diagrams and escape hatchesdiagram mermaid tex

03 / AzeMark Source

A complete document stays readable before it renders.

Front matter pins AzeMark language version 2. Directive fences use exactly four colons and a ---- header separator.

variance.aze.mdComplete Source
---
azemark: 2
title: Sample variance
---

# Sample variance

Spread of a sample around its mean.

:::: equation
id: sample-variance
number: true
----
sigma^2 = frac(1, n) sum i=1..n of (x_i - mu)^2
::::
variance.aze.md · rendered Document previewDocument preview
Browse the verified examples

04 / Compare

What Changes When the Document Is a Contract.

Other tools render pages. AzeForge validates meaning first: every Block is typed, every field is checked, and the grammar is published as JSON so humans and agents author against the same contract.

CapabilityAzeForgeTypstQuartoLaTeX
Authoring ModelWhat you write to get a documentTyped AzeMark SourceMarkdown plus validated directive BlocksScripted MarkupCode-like syntax with packagesMarkdown Plus ExtensionsProse with bolted-on filtersTypesetting ProgramExplicit layout commands
Technical DiagramsCircuits, timing, geometry, controlNative Typed BlocksDeclared topology, rendered wiresCommunity PackagesExternal ExtensionsSpecialist Packages
Correctness FeedbackWhat happens when Source is wrongCompiler DiagnosticsCoded errors with locations and fixesCompiler ErrorsBuild LogsLog Diving
Machine-Readable ContractCan an agent verify before renderingPublished JSON Grammar26 directives, fields, enums, limits———
Programmatic AccessUse from code and agentsCompiler npm APIAnalyze, compile, formatDifferent Ecosystem——
Output GuaranteeWhat a successful render promisesSelf-Contained ArtifactsHTML, SVG, PNG, PDF with content hashVaries by OutputVaries by OutputUsually PDF

Mathematics and Mermaid rendering are table stakes — every column handles them. The rows above are where the authoring experience actually diverges.

Docs and Playground

Read the contract or try the hosted authoring flow.

DocumentationPinned 0.6.3 guides, generated reference data, and AI-authoring rules.PlaygroundUse an access token to author and render the Current document in the browser.