With complete, this is done. And it's really nice.

Exactly. This is a philosophical issue, to do with how comprehensively stripes-connect provides us with the communication mechanisms we need.

But, yes, it does happen also give us a great motivating example of the kinds of compound-write operations we're going to be needing the business-logic modules to do, and gives us a chance to establish a general framework for how they might work.

I don't want to see frontend work get impeded in the meantime.

Just to be clear, there's no currently scheduled front-end work being blocked by this

Right. Here's how I see this.

1. UI posts a composite record to a high-level endpoint

2. users-bl plucks the creds and perms records out of the user record, so it's left with three separate records of different types, each of which it knows how to handle.

3. users-bl invokes the three operations in the context of some kind of transaction API. Maybe something like this:

Nominally, didItWork is a status for the whole three-operation transaction.

4. But for now, the transaction object is implemented by just running each operation as it comes in and remembering if it succeeded. If they all succeed, it returns true, otherwise false. Because that's sort of Good Enough for now.

5. When it's convenient, you can upgrade the implementation of the transaction object to do back-patching if something goes wrong.

6. The day may come when we somehow have to upgrade this to do real transactions; but it is not this day.

You are correct. I was talking in the sense of: "Does JSONAPI offer us a way to design a transaction-type API that we can follow?"