> Note: This page is an sketch of what Liam inteprets what Daniel describes... so its a sketch of a sketch which I feel is both important and possibly relates to my views on human centred agreement workshops and Domain Driven Design.
> Agreements are a requirement, not the whole interface
For management activities, “the interface is about coming to agreements” is strongly true. Buying, selling, listing, pricing, delivery, returns, rights, and accountability all require explicit agreements and shared states. For creation activities, “agreement” is less complete as a frame. Exploring ideas, drafting, editing, curating, reviewing, and discovering emergent value often involves ambiguity, provisional outcomes, and productive disagreement. So “agreements” should be treated as a requirement for the buy/sell domain, but not as the whole definition of interface.
# Roles are fluid, so interfaces must be integral In many marketplaces and knowledge ecosystems, “buyer” and “seller” are not fixed identities. People swap hats: a customer can resell, a seller can curate and write, a creator can buy, and a community member can move between roles over time. That implies an integral interface that supports role-switching gracefully, rather than a narrow interface that assumes stable user categories.