How languages track who is in the room and who benefits from what is said.
Holding questionWhose interests and inclusion are silently assumed by our data models?
APIs and payloads rarely encode who was addressed, who was included, or who a change was for. These capabilities make that fabric visible.
- 01
Inclusive and Exclusive Participation
Does "we" include the listener?
Why hereDoes 'we' include the listener? Grammatical inclusivity is a native structure for audience-aware messaging.
Participation and Agency·Research · Under review·Graft · Conceptualised - 02
Benefactive and Affected-Party Marking
Who benefits from or is affected by this action?
Why hereFor whom is this action performed? A first-class beneficiary role reshapes access, notifications, and consent.
Relationship and Responsibility·Research · Source required·Graft · Documented - 03
Politeness and Register
What is the appropriate way to say this here?
Why hereRegister carries the social contract of the utterance — one that logs and UIs strip on the way through.
Relationship and Responsibility·Research · Source required·Graft · Documented - 04
Topic and Focus
What is this statement really about?
Why hereTopic and focus decide what is old news and what is new. A payload has a topic; we simply don't mark it.
Meaning and Context·Research · Under review·Graft · Documented
Each stop names a distinction that ORM fields and REST bodies typically bury. Reading them together suggests a family of relational types the industry has yet to name.