@techreport{borthwick-msebenzi-environment-state-01,
    number =    {draft-borthwick-msebenzi-environment-state-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-borthwick-msebenzi-environment-state/01/},
    author =    {Douglas Cameron Borthwick and Michael Msebenzi},
    title =     {{Verifiable Intent -- environment.* Constraint Family}},
    pagetotal = 44,
    year =      2026,
    month =     jun,
    day =       13,
    abstract =  {Agent-authorization mandate formats authorise autonomous agents to act on behalf of human principals through cryptographically signed constraint instances bound into delegated mandates. Their existing constraint families describe properties of the transaction itself — what is being purchased, by whom, for how much, against which credential. They do not describe properties of the environment in which the transaction is executed: whether the venue is open, whether the source of funds is funded, whether other relevant external conditions hold at the moment of execution. This document specifies the environment.* constraint family for agent-authorization mandate vocabularies. It is defined against a host-binding profile (Section 1.3.1) that the Verifiable Intent (VI) mandate format satisfies and that other mandate formats may satisfy; VI is used throughout as the reference host. It defines the membership criterion under which a constraint type qualifies as a member of the family, the family-wide vocabulary every member uses, the composition discipline by which family members compose with each other and with constraints from other families, the register discipline under which family-wide and per-type prose is written, the family-wide security considerations, and the IANA registry mechanics under which new family members are registered. It does not define any individual constraint type. Two reference type specifications (environment.market\_state and environment.wallet\_state) are referenced informatively in Appendix A.},
}