A project charter, future processes, requirements and stakeholder analysis need a home. Try placing them in three possible contract packages, or keep them with the people shaping and operating the project.
Context, internal ownership and concept of operations
Try one split. Keep the business requirement with Internal ownership and place its proposed delivery work in a contract package. In the notes, state who will confirm that the delivered output meets the requirement and what must cross that interface. Moving the cards clarifies an allocation proposal; it does not create the agreement or verify the handover.
Context holds background, assumptions and constraints that explain the work. Internal ownership holds work or decisions you intend to retain. Concept of operations (ConOps) describes how the future service or capability will be used and operated. These are thinking aids: moving a card does not establish a supplier obligation or transfer accountability.
Each artefact has one primary home. Use its notes to explain shared interfaces; split an idea into distinct artefacts if it represents separate work. The three contracts are editable planning placeholders, not a procurement recommendation. The board does not assess cost, legality, completeness, dependencies or contractual responsibility.