Phero Lang documentation

Phero Lang is a multi-surface modeling language: every surface follows the same pipeline (check → ir → backends) and compiles to its own versioned JSON artifact.

Reading paths

• “I want to model a domain” → The .mox language reference, then the .mox examples in examples. Add behavior with DDD design DSL (.ddd), contracts with Event contracts (.evt).
• “I want to generate a system” → the support-desk stack in examples walks domain → policy → design → events → use cases → flows → deployment → case; the README’s walkthrough compiles each layer by hand.
• “I want to consume Phero Lang from my tool” → Writing a backend for Phero Lang (artifact contract), or the root README’s integration styles.
• “I want evidence, not assurances” → Semantics: the claim ladder for what is claimed and refused, Verification (proof-obligation register) for each row’s status, evidence pointer and review date, and Verification receipts for checking a release’s evidence without the prover toolchain.
• “I want to add a surface” → AGENTS.md (the table row), then any per-surface doc as the template.

The documents

Reference

• The .mox language reference — .mox / .actor
• The Phero Lang expression language (Tier 2) — all surfaces
• DDD design DSL (.ddd) — .ddd
• Event contracts (.evt) — .evt
• Deployment models (.deploy) — .deploy
• Use case patterns (.uc) — .uc
• Case management (.cmmn) — .cmmn
• DMN decision model DSL (.dmn) — .dmn
• IFML DSL — .ifml
• The unified semantic graph
• Diagnostic codes
• Writing a backend for Phero Lang
• Versioning and release policy — all
• Naming — all

Engineering

• Semantics: the claim ladder
• Verification (proof-obligation register)
• Verification receipts
• Rune body translation — design (RFC)

Migration

• Rebranding: rexlang → Phero Lang
• Release runbook: v0.3.0 (Phero Lang)

Decisions

• Architecture decision records
• 0001 — Rebrand rexlang to Phero Lang