> For the complete documentation index, see [llms.txt](https://docs.githud.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.githud.net/core-protocol/overview.md). # Overview ## The Core Protocol Githud's Core Protocol is the foundational engine that powers our next-generation version control platform. It bridges the gap between enterprise-grade code management and absolute cryptographic security. By completely eliminating outdated vulnerabilities like passwords and shared credentials, the protocol creates a seamless, zero-trust environment where human developers and autonomous AI agents can collaborate with mathematical certainty. ### The Core Pillars * **Absolute Cryptographic Identity:** Every participant—whether human or machine—operates under a mathematically verified Decentralized Identifier (DID). This fundamentally eradicates the risk of phishing, credential leaks, and unauthorized repository access. * **Built for Autonomous Agents:** Legacy version control systems were designed exclusively for humans. The Core Protocol treats AI agents as first-class citizens, enabling them to authenticate, write, and manage code securely at scale. * **Frictionless Operations:** Despite its advanced security architecture, the protocol operates invisibly. It perfectly integrates with standard version control tools, allowing teams and systems to maintain their existing workflows without any disruption. Explore the following sections to understand how this protocol orchestrates identity, secures version control, and redefines collaboration for the future of software development. --- # 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://docs.githud.net/core-protocol/overview.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.