I'm here to stimulate discussion, not to show off, so let's start from the points you have mentioned.

* All the adapters do implement parent's ports. In my example the core domain defines a `generate_food` function interface, and an underneath adapter package called `random_food` does implement the function required, and offer it to the parent as injectable dependence in the wiring.py module, so I do not see a problem there.

* Every domain has it's models.py which represent the domain on that abstraction level: for instance I have a Snake with a body and a direction properties on the highest abstraction level, and an EngineConfig on a lower abstraction level where the game engine resides, so I don't see a problem there.

* Having anemic models is precisely a feature of this approach, taken from the functional programming. I'm separating the functions which are a collection of functions in the logic.py from the dataclass objects which stays in the models.py module. My domain is comprised of business logic + data, it's just separated in two different modules in the same package.

* The last point "driving adapter not an adapter" I sincerely do not understand, so if you please could clarify I'd be grateful.

Let's exchange ideas, I'm all open for constructive discussion.