> For the complete documentation index, see [llms.txt](https://joincare.gitbook.io/joincare-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://joincare.gitbook.io/joincare-docs/technology-and-mechanisms.md). # Technology and Mechanisms JoinCare's technical stack supports reviewable AI workflows, verifiable contribution records, DAO coordination, and the progressive release of developer and security resources. ### CareAgents and Data Workflows CareAgents improve document processing, evidence organization, risk identification, and project tracking. Defined data boundaries, human review, and verifiable workflow records keep outputs reviewable and accountable. ### Governance and Contribution Layer JoinCare combines team execution, expert input, and community coordination. The Core Team leads strategy and delivery; Scientific and Medical Advisors provide domain expertise; DAO contributors support proposals, documentation, and ecosystem development; and $JC holders may participate in governance and community feedback under the formally released governance framework. Contribution records recognize sustained participation and may inform task incentives, governance access, and future ecosystem opportunities. Token-based governance does not replace scientific, medical, legal, or operational judgment. --- # 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://joincare.gitbook.io/joincare-docs/technology-and-mechanisms.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.