How Models and Bounded-Contexts are mapped into the codebase DDD?
This is based on my understanding of course... opinions may vary.


Model is not one thing in your code but if done well, it is the code. It is what you come up with from the knowledge crunch of the business and try and capture in code. Coming up with one model for the whole business is usually a fool errand. So you have a context that the model is valid in...
A bounded context is a context that a model is valid. This is valuable for a few reasons. It allows us to manage the scope and complexity of a model. A model is only useful insomuch as it helps us solve business problems. To do this we need to be able to keep some form of it in our heads so we can understand. This is where language comes in. The language, aggregates, etc. are valid for that context. I like to use an example here. A product in an eCommerce checkout is different from a product being picked from a warehouse. They may share some concepts but some are not relevant across contexts. How they relate should be captured in a context map.
Models and Bounded-Context conceptually are:
Model:

A system of abstractions that describes selected aspects of a domain
  and can be used to solve problems related to that domain.

Bounded-Context: 

The setting in which a word or statement appears that determines its
  meaning.

But I have to questions:

Is the relationship between the two is containment relationship,
i.e. Bounded-Context has one or more models?
As I understand DDD concepts should be identifiable (to some degree) through the codebase, this is clear for Aggregate, Entities, Event, Commands...etc, but how Models and Bounded-Context are mapped into the codebase? for example is a models just a set of one or more aggregates, or something else? is Bounded-context a namespace or something else?

Thanks in advance.
Note: Feel free to state your answer in term of some framework, Django, Axon..etc.