Specification overview¶
This is the generated, human-readable view of the wacrg corpus, a machine-readable model of the WhatsApp 1:1 call protocol. Every page below is generated from YAML under spec/; do not edit the Markdown by hand.
Research scaffold, not authoritative truth
No real captures exist yet. Examples are synthetic and clearly labeled, and most facts carry probable or speculative confidence with open questions. Trust the confidence levels, not the prose.
Contents¶
| Section | Count |
|---|---|
| The spec — normative call-stack spec | 47 parts |
| Stanzas | 9 |
| Flows | 4 |
| Enums | 3 |
| Techniques | 7 |
| Flavors | 4 |
| Contributors | 6 |
| Glossary | - |
| Coverage | - |
How the spec is organized¶
- Stanzas describe individual WABinary nodes (tag, attributes, nested children) with per-fact provenance and confidence.
- Flows stitch stanzas into end-to-end signaling sequences with mermaid diagrams.
- Enums capture closed value sets (e.g. terminate reasons).
- Techniques document the reverse-engineering methods that back each fact; Tools and Contributors record what produced it and who submitted it.
- Flavors are independent reimplementations that corroborate the spec; the Implementation map records where each bit of the spec is realized in their code (the inverse of a code-to-reference pointer).
- Coverage quantifies how confirmed the spec currently is.