Curious how you think about the nuances of cross-organizational use case-specific workflows here. Access to a record is one thing, but that doesn't account for nuanced use cases, where orchestrating workflows and transactions across two types of orgs goes beyond rote request-record-respond.

The price chosen is not 'often' arbitrary: it *always* is. Not because smart people aren't applying good rationale at the time, but bc definition price-setting is just that: setting a price, regardless of how conditions change / evolve.

Markets allow for price discovery over time / conditions.