| 1 | # siGit product overview and taxonomy |
| 2 | |
| 3 | Status: spec v1 (2026-06-26). Audience: internal (private repo). This is the |
| 4 | canonical map of what we sell and what the words mean. Every other spec defers to |
| 5 | the names defined here. |
| 6 | |
| 7 | --- |
| 8 | |
| 9 | ## 1. The two domains |
| 10 | |
| 11 | | Domain | What it is | |
| 12 | |---|---| |
| 13 | | **sigit.si** | **Git hosting for the AI era.** The forge: repositories, branches, commits, and over time pull requests, issues, and the source-control surface that AI-native workflows run on. | |
| 14 | | **code.sigit.si** | **The universe of siGit Code**, the coding agent. Home for the agent and its hosted products. | |
| 15 | |
| 16 | Keep them distinct: sigit.si hosts the code; code.sigit.si is where the agent |
| 17 | lives and where the hosted offerings are sold. |
| 18 | |
| 19 | --- |
| 20 | |
| 21 | ## 2. siGit Code (the agent) |
| 22 | |
| 23 | **siGit Code** is a **natively local-inference coding agent** (the Rust CLI / ACP |
| 24 | agent). On-device by default: the model runs on the user's machine, the agent |
| 25 | works against local repos, nothing is sent to a server unless the user chooses a |
| 26 | hosted product. |
| 27 | |
| 28 | Because it is local-first, the **root of code.sigit.si (`/`)** is the |
| 29 | **on-device dashboard**: telemetry of the user's **local** siGit Code sessions, |
| 30 | shown only if the user opts in to enable it. Nothing leaves the machine. |
| 31 | |
| 32 | --- |
| 33 | |
| 34 | ## 3. The hosted products on code.sigit.si |
| 35 | |
| 36 | Two products sit on top of siGit Code. They mirror the two ways GitHub Copilot is |
| 37 | sold (interactive chat vs. autonomous coding agent), but the engine in both is |
| 38 | siGit Code, which we already ship. |
| 39 | |
| 40 | ### 3.1 siGit Code Cloud — hosted chat (BUILT) |
| 41 | |
| 42 | **siGit Code Cloud** is the **hosted, non-on-device chat**: an interactive |
| 43 | assistant powered by hosted inference instead of the local model. The user signs |
| 44 | in, picks a quality tier, and chats. Conversations are saved. |
| 45 | |
| 46 | - **Surfaces:** `/cloud` (the chat) and `/cloud/sessions`, `/cloud/sessions/<uuid>` |
| 47 | (saved chat history). **Both are part of siGit Code Cloud.** |
| 48 | - **Unit of work:** a **session** = one saved chat conversation. |
| 49 | - **Compute:** hosted inference only (Onde Cloud, via `/api/v1/chat/completions`). |
| 50 | - **Copilot analog:** Copilot Chat. |
| 51 | - **Status:** shipped and live at code.sigit.si. |
| 52 | |
| 53 | ### 3.2 siGit Code Cloud Agent — autonomous agent (TO BUILD) |
| 54 | |
| 55 | **siGit Code Cloud Agent** is **autonomous, sandboxed siGit Code that solves an |
| 56 | issue or task in a Git repository and opens a pull request**, working in the |
| 57 | background like a human developer. The user delegates a task and walks away; the |
| 58 | agent works on its own and comes back with a PR to review. |
| 59 | |
| 60 | - **Engine:** siGit Code, run headless in an ephemeral **sandbox** (AWS), with |
| 61 | hosted inference. The agent clones the repo, edits, runs build/test, iterates, |
| 62 | pushes a branch. |
| 63 | - **Repo target:** **sigit.si first**, then **GitHub, GitLab, and other Git |
| 64 | hosts** in the future. Scope is **Git only** (no SVN, Mercurial, or other version |
| 65 | control systems). The agent is **Git-host agnostic** behind a Git-host adapter: |
| 66 | sigit.si is the first host, not the only one. |
| 67 | - **Output:** a **pull request** on the target Git host (a pushed branch + review |
| 68 | surface) for a human to review and merge. The agent never auto-merges. |
| 69 | - **Unit of work:** an **agent run** (one delegated task → autonomous work → PR). |
| 70 | - **Copilot analog:** Copilot coding agent (the cloud agent). |
| 71 | - **Status:** planning. See [sigit-code-cloud-agent-plan.md](sigit-code-cloud-agent-plan.md). |
| 72 | |
| 73 | --- |
| 74 | |
| 75 | ## 4. Naming rules (to stop the collisions) |
| 76 | |
| 77 | These words are load-bearing. Use them exactly. |
| 78 | |
| 79 | - **siGit Code** — the local-inference coding agent. The engine. |
| 80 | - **siGit Code Cloud** — the hosted **chat** product. `/cloud` + `/cloud/sessions`. |
| 81 | - **siGit Code Cloud Agent** — the autonomous **agent** product (task → PR). |
| 82 | - **session** — a siGit Code Cloud **chat** conversation. It belongs to siGit Code |
| 83 | Cloud. Do **not** use "session(s)" to mean the agent or its runs. |
| 84 | - **agent run** — one siGit Code Cloud Agent task. Use "run" (or "task"), never |
| 85 | "session," for the agent. |
| 86 | - **on-device dashboard** — the local telemetry at `/` (opt-in). |
| 87 | |
| 88 | So: the thing at `/cloud/sessions` is **chat sessions** (siGit Code Cloud). The |
| 89 | autonomous product is the **Agent**, and its work items are **runs**, on their own |
| 90 | surface (anchored to a repo, since a run operates on one repository). |
| 91 | |
| 92 | --- |
| 93 | |
| 94 | ## 5. Information architecture (code.sigit.si) |
| 95 | |
| 96 | | Path | Product | Notes | |
| 97 | |---|---|---| |
| 98 | | `/` | on-device dashboard | local session telemetry, opt-in | |
| 99 | | `/cloud` | siGit Code Cloud | the hosted chat | |
| 100 | | `/cloud/sessions`, `/cloud/sessions/<uuid>` | siGit Code Cloud | saved chat history + detail | |
| 101 | | `/billing` | account | plan / billing | |
| 102 | | _(future)_ agent surface | siGit Code Cloud Agent | run-a-task and the list of agent runs; anchored to a repo (sigit.si first). Surface path TBD in the agent spec. | |
| 103 | |
| 104 | The current web app (`apps/code-cloud-web`) already implements rows 1 to 4. The |
| 105 | Agent surface is new and specified separately. |
| 106 | |
| 107 | --- |
| 108 | |
| 109 | ## 6. Why this is a strong position |
| 110 | |
| 111 | GitHub had to build a coding agent to ship its cloud agent. **siGit already ships |
| 112 | the agent (siGit Code) and the git host (sigit.si).** siGit Code Cloud Agent is |
| 113 | mostly: take the agent we already have, run it headless in a sandbox against a |
| 114 | repo we already host, and open a PR. The one genuinely new system is the sandbox. |
| 115 | The Git-host-agnostic design means the same agent later runs against GitHub and |
| 116 | GitLab repos, not just sigit.si (Git only; not SVN, Mercurial, or other VCS). |