coulomb/mail-address-semantics
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Map a MAS gateway event into the email-connect evidence ceiling.

Browse source 
mas-email-evidence 0.1 reports MX acceptance, a bounce, or a reply, and
refuses the claim that a person read the message. Ordinary product mail
stays in email-connect. A product speaks the mode contract.

Assistant: grok
Assistant-Session: 01a198fa-fd27-7e41-a0a2-57355c3e4efd
This commit is contained in:
tegwick 2026-11-01 23:13:04 +01:00
parent f18eb0b8df
commit aef4c5dd71
5 changed files with 271 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/reuse-surface.md
View file

@ -45,6 +45,17 @@ that handoff (it carries a per-handoff token), with an increasing `seq`.
Never send `timed-out`.
`mas_modes/stubs/callback.py` is a complete example.
## Ordinary product mail stays in email-connect
A product integrates with this facility by speaking the mode contract. It
does not send MAS syntax through the email-connect transactional receiver.
`docs/mas-email-evidence-v0.1.json` maps one gateway event into
email-connect's evidence ceiling: the MX accepted the message, the message
is a bounce, or the message is a non-automatic reply. The ceiling refuses
the claim that a person read it. `mas_gateway.email_evidence` is the
reference function. Tickets and statutes stay here. Templates and the
product ledger stay in email-connect.
## Examples only, not products
- `examples/ticket_service/`: the reference ticket service, used as the