3. Your purpose shapes the experience *Your knowledge gives shared capabilities their local meaning.* The same feature can serve a different purpose Two organizations can use a video, a question, and a follow-up message to create very different experiences. A home-care team may help a family prepare for a first visit. A community center may introduce an activity and the person who will welcome newcomers. The technical pieces are similar. The knowledge, relationship, and purpose around them are different. That difference is central to genus. A partner brings more than a logo. It brings experience with its audience, the language people recognize, trusted resources, service boundaries, and an understanding of what happens on a difficult day. Those contributions shape how capabilities are configured and what the resulting experience asks people to do. An organization’s mission becomes useful when it influences decisions. If the mission includes helping people retain independence, an invitation should offer understandable choices. If it values belonging, the experience should connect people with a welcome they can actually find. If it promises responsive support, the team needs an operational way to receive and answer questions. Image description: Partner knowledge, values, lived experience, local needs, and service commitments enter human review. Reviewed knowledge shapes content and messages, workflows and responsibilities, and learning from experience. Figure 3. Your knowledge gives capabilities their local meaning · Connection map Connection map adapted for this field guide from the carePhysics idea of shared knowledge with local judgment. A partner’s purpose shapes how each capability is used. 1. Bring approved knowledge together with lived experience, values, and the needs people describe. 2. Accountable people review sources, permissions, and current versions before local use. 3. Content, workflows, and learning carry that purpose into everyday interactions. New learning returns for review. Joe Gleason · carePhysics 3.7 · chapter 13, adapted (https://genusconnect.org/carephysics/book/chapter-13) Bring knowledge into the work A useful partner knowledge base brings approved research, care strategies, explanations, and communication guidance together with local resources and questions. Central owners maintain shared standards; departments and locations contribute relevant knowledge. Review keeps contacts, service conditions, and guidance current. Knowledge may also be practical and difficult to capture in a policy document. A frontline worker knows which part of an introduction causes uncertainty. A volunteer has found a respectful way to begin a conversation. A participant notices that a message assumes access to a car. Those observations deserve a route into improvement, with permission and context preserved. The platform can help organize and deliver knowledge, but a partner must decide which material is appropriate for which audience. Staff guidance, public information, and family resources may overlap without being identical. A public explanation should not expose internal case notes. An AI assistant needs the same clarity about what it may use and for whom. Three kinds of governance Personal governance begins with the person’s choices and the authority appropriate to their circumstances. Who do they want involved? What do they understand about an invitation? How can they correct information or ask for a different arrangement? Where a representative has an authorized role, the scope of that role needs to be clear rather than assumed from a family relationship. Organizational governance assigns responsibility for operating the experience. Who approves content? Who reviews a pathway? Who manages access? What happens when a message describes a need outside the service’s scope? The answers should be specific enough that a staff member can act on them during normal work. Mission stewardship concerns the longer direction of the ecosystem. We want the mission to remain clear as genus grows: people and families first. genusCommunity Foundation’s stewardship role belongs in that conversation. Read the genusCommunity Foundation section (https://genusconnect.org/companies#genuscommunity-foundation) alongside the relevant partnership discussion. Before you commit, agree what stewardship means in practice: who is responsible, how participation works, and what happens if the arrangement changes. The carePhysics connection Shared Tools, Local Wisdom (https://genusconnect.org/carephysics/book/chapter-13) gives this chapter its practical foundation. Shared tools become more useful when they carry local knowledge without erasing the judgment and relationships that made that knowledge valuable. Bring Human Wisdom Within Reach (https://genusconnect.org/carephysics/book/chapter-09) extends the question to AI assistance. A partner’s values should appear in the behavior of an experience. A respectful tone matters, but so do the choices offered, the permissions applied, and the response when someone says the arrangement does not work. The person’s experience is where the organization’s stated values become visible. Where AI helps An assistant can help organize approved material, identify conflicting explanations, and draft content for a defined audience. A reviewer can use it to compare a proposed message with the organization’s language and purpose. The team still decides which sources are authoritative, which are current, and which should be available in that context. A broad collection of documents is not automatically a governed knowledge base. It may contain outdated material, different audiences, or unresolved disagreements. Before giving AI access, clarify the collection’s purpose and limits. Better organization improves the conditions for useful assistance; it does not remove the need to check the output. Bring your knowledge Gather one approved resource, one frequently asked question, and one frontline observation. Discuss what each contributes to a specific interaction. Decide who should review it and how the team will know when it needs updating. This small exercise often reveals more about a workable knowledge process than a plan to upload every document at once. Explore further — A practical knowledge record For a resource your team wants to reuse, record its audience, owner, source, review date, intended use, and important limitations. Include the contact or process for correcting it. If it contains another person’s experience, decide what permission is needed before sharing and what details should remain private. These are operating choices a partner should establish, not a claim that every field is implemented identically in every genus module. The purpose is to keep a useful idea connected to the conditions that make it trustworthy. That connection matters whether a human colleague or an AI assistant helps bring the idea forward.