Document ephemeral Composer and asynchronous deliveryHEADmain

1 files changed, 21 insertions, 3 deletions

diff --git a/README.md b/README.md
index aad5677..23a4080 100644
--- a/README.md
+++ b/README.md
@@ -69,6 +69,14 @@ configuration, and network policy. The initial `fog-drop`, `fog-mailbox`, and
 `fog-im` features run as Composer-side modules over one common messaging and
 storage protocol, not as distinguishable public services.
 
+FOG messaging is asynchronous. `fog-drop` acts as one cryptographic digital
+dead drop, while `fog-mailbox` and `fog-im` use sequences of rotating,
+capability-addressed dead drops. A Composer may prepare bounded opaque polling
+work for its online blind relay, which can later queue opaque results but
+cannot decrypt them or derive new mailbox capability state. Replica storage,
+relay retrieval, Composer commit, and human reading are different events; FOG
+does not promise real-time delivery.
+
 The Composer can run as a networkless microVM on an online host or as a
 portable bootable USB system on a physically offline computer. High-assurance
 transfer avoids USB shuttling and uses QR or `FOG-SX`, an acknowledgment-free
@@ -79,9 +87,19 @@ physical profiles remain non-active pending implementation, hardware, and
 resource review. Visible light, audio modem, and paper tape remain possible
 future backends.
 
-Composer software boots from an authenticated read-only image and keeps
-mutable secrets in a volume-encrypted, object-authenticated transactional
-vault. Imports are hostile fixed bundles; exports contain only committed
+A rootless Podman `network=none` Composer remains a functional fixture and
+does not protect unlocked state from its host or shared kernel. A non-active
+RAM-only Ephemeral Composer direction is limited to one-shot drops and
+explicitly non-resumable sessions. Closing it abandons its identity, keys,
+capabilities, pending work, and reply ability, without making a secure RAM
+erasure claim. Continuing mailbox and chat use requires a Persistent Composer
+vault.
+
+Composer software boots from an authenticated read-only image and keeps every
+sensitive mutable object in an authenticated encrypted transactional vault.
+Whole-volume encryption such as LUKS2 is highly recommended defense in depth,
+but is not a universal requirement and cannot replace object authentication.
+Imports are hostile fixed bundles; exports contain only committed
 opaque work. A local commitment chain is not presented as complete rollback
 protection. That claim requires an independent monotonic anchor outside the
 vault and host rollback domain. Identity recovery does not resume stale live