> 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-concept/system-architecture.md).

# System Architecture

## System Architecture

Githud is engineered as a scalable ecosystem designed specifically for the era of autonomous agents and high-security development. Our architecture abstracts away legacy vulnerabilities such as passwords and SSH keys to deliver a seamless, cryptographically secure version control platform.

```
┌─────────────────────────┐      ┌─────────────────────────┐
│ Human Developers (Web)  │      │ Autonomous Agents (CLI) │
└────────────┬────────────┘      └────────────┬────────────┘
             │                                │
             └───────────────┬────────────────┘
                             ▼
┌──────────────────────────────────────────────────────────┐
│               Security & Identity Gateway                │
│ (DID Authentication | Access Control | API Orchestration)│
└────────────────────────────┬─────────────────────────────┘
                             ▼
┌──────────────────────────────────────────────────────────┐
│                  Core Infrastructure                     │
│    ┌──────────────────┐          ┌──────────────────┐    │
│    │ Identity Ledger  │          │   Git Storage    │    │
│    └──────────────────┘          └──────────────────┘    │
└──────────────────────────────────────────────────────────┘
```

#### The Core Components

| Component              | Strategic Role                                                                                                                                                             |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Client Layer**       | Provides seamless, intuitive access for both human oversight (Web Interface) and machine-to-machine operations (CLI).                                                      |
| **Security Gateway**   | The intelligent orchestration layer. It intercepts every request, verifies Decentralized Identifiers (DIDs), and strictly enforces access rights before any data is moved. |
| **Git Storage Engine** | A highly resilient, industry-standard version control backend designed to ensure code integrity, rapid scaling, and high availability.                                     |
| **Identity Ledger**    | A persistent metadata store that dynamically maps cryptographic keys to repository access, ensuring absolute data consistency and privacy.                                 |

#### Design Principle: Zero-Trust by Design

The underlying storage infrastructure is completely isolated from public access. Every single interaction whether initiated by a human developer or an AI agent is mediated by our Security Gateway. This guarantees that all repository access is mathematically verified and explicitly authorized without relying on vulnerable shared secrets.


---

# 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-concept/system-architecture.md?ask=<question>&goal=<endgoal>
```

`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.