Apply M31 commands through the shared ledger

[onehouse] / doc / mqtt.rst

diff --git a/doc/mqtt.rst b/doc/mqtt.rst
index 1f5fa4a6ce1d912916922588a84c7b466e95756a..e0a2d6246a23f19295d68db48162f0ababcae3da 100644 (file)
--- a/doc/mqtt.rst
+++ b/doc/mqtt.rst
@@ -30,9 +30,12 @@ run timers or implement publication suppression.
 Each operation has a ``Build`` function and a ``Parse`` function, such
 as ``BuildReported`` and ``ParseReported``. Builders accept an ID, an
 optional target, metadata, and a typed payload. They validate the same
-contract as the parsers. ``Parse`` selects the typed payload and address
-kind from an incoming topic. A caller does not split or join topics and
-does not build an envelope.
+contract as the parsers through shared typed validation. A builder
+encodes its validated payload without parsing it. Batch members use the
+same metadata and value validation without envelope encoding. Access
+flag presence checks apply to parsed JSON only. ``Parse`` selects the
+typed payload and address kind after one topic parse. A caller does not
+split or join topics and does not build an envelope.
 
 A ``Publication`` contains topic, JSON bytes, QoS, and retention. It
 also supplies the expiry deadline, response topic, and correlation data