Three of this week's Bay Area tech stories share a structural design feature: the buyer of the system gets the interface and the account rep; the person being processed by it gets the outcome, no explanation, and no appeal. That's not a customer-service failure. It's the model.

Last week's equity-divide piece named the line that ran through Bay Area tech's week: who buys the system and who gets sorted by it. Three of this week's stories fill in what that actually looks like at the moment of decision.

When Patronscan's Guard+ scanner flagged a Castro bar patron and the bar refused them entry, the story showed what the processed party receives: a refusal, and a company whose public privacy claims and marketing tagline don't square with each other. The patron has no disclosed way to see their file, no process to dispute the flag, and no contractual relationship with Patronscan at all. The bar is the customer. The patron is the input.

When AI tools tripled application volumes and pushed Bay Area time-to-hire up 76%, the story showed the asymmetry running the other direction through hiring. The company bought the ATS. The applicant didn't. When the screener eliminates someone, no explanation is owed — and at 300-plus applications per role, none is operationally possible. The friction of the AI arms race falls on the person waiting to hear back, not on the company deciding.

When UCSF and Cigna closed a new in-network deal four days after a public termination notice, the story showed that institutional parties can move when the pressure is public — and that patients at risk of losing their doctors learned about it from press coverage and employer alerts, not from either party to the contract. The deal was negotiated without them and announced after the fact.

The common structure across all three isn't a customer-service failure or an oversight. The people being processed aren't the customers. The buyer gets the interface, the account rep, and the dashboard. The person being sorted gets the decision — with no explanation, no appeal, and no relationship that would require one.

That's not incidental. It's what the business model requires.