> For the complete documentation index, see [llms.txt](https://bdi.gitbook.io/bdi-public-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bdi.gitbook.io/bdi-public-documentation/readme/boundary-management-kit.md). # Boundary Management ## 1. Introduction Usually, many parties are involved in a logistic process. Each of these parties maintains a set of valuable assets that they needs to protect. In abstract terms, this protection is realized by creating an perimeter, a boundary around the assets that is controlled by the party. Other parties can not cross the boundary without permission of the owner, hence the value is protected. However it is often required that parties do cross the boundary to facilitate cooperation. Three different kinds of assets and their associated boundaries are distinguished: * Digital assets, such as IT systems (applications, processes) and data * Physical assets, such as distribution centers and production facilities * Legal (ownership, liability and accountability) assets, such as responsibilities for and ownership of cargo The nature and implementation of the protecting boundaries is different for each kind of assets and each one requires specific measures to allow third parties to cross them in order to cooperate in a logistic process. There are two reasons to allow others (representatives as in human and IT-processes) to cross a boundary: * To allow them to use an asset * To transfer an asset between parties Boundary Management is about managing boundaries in practice. ## 2. Interlinkages with other building blocks Digital Identity M2M Digital Identity H2M Authorization Federation KIT --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://bdi.gitbook.io/bdi-public-documentation/readme/boundary-management-kit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.