@setoelkahfi / homebrew-tap
Code Commits Pulls CI/CD 205
main
main
md 5.31 KB
View source Raw

siGit product overview and taxonomy

Status: spec v1 (2026-06-26). Audience: internal (private repo). This is the canonical map of what we sell and what the words mean. Every other spec defers to the names defined here.

1. The two domains

Domain What it is
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.
code.sigit.si The universe of siGit Code, the coding agent. Home for the agent and its hosted products.

Keep them distinct: sigit.si hosts the code; code.sigit.si is where the agent lives and where the hosted offerings are sold.

2. siGit Code (the agent)

siGit Code is a natively local-inference coding agent (the Rust CLI / ACP agent). On-device by default: the model runs on the user's machine, the agent works against local repos, nothing is sent to a server unless the user chooses a hosted product.

Because it is local-first, the root of code.sigit.si (/) is the on-device dashboard: telemetry of the user's local siGit Code sessions, shown only if the user opts in to enable it. Nothing leaves the machine.

3. The hosted products on code.sigit.si

Two products sit on top of siGit Code. They mirror the two ways GitHub Copilot is sold (interactive chat vs. autonomous coding agent), but the engine in both is siGit Code, which we already ship.

3.1 siGit Code Cloud — hosted chat (BUILT)

siGit Code Cloud is the hosted, non-on-device chat: an interactive assistant powered by hosted inference instead of the local model. The user signs in, picks a quality tier, and chats. Conversations are saved.

  • Surfaces: /cloud (the chat) and /cloud/sessions, /cloud/sessions/<uuid> (saved chat history). Both are part of siGit Code Cloud.
  • Unit of work: a session = one saved chat conversation.
  • Compute: hosted inference only (Onde Cloud, via /api/v1/chat/completions).
  • Copilot analog: Copilot Chat.
  • Status: shipped and live at code.sigit.si.

3.2 siGit Code Cloud Agent — autonomous agent (TO BUILD)

siGit Code Cloud Agent is autonomous, sandboxed siGit Code that solves an issue or task in a Git repository and opens a pull request, working in the background like a human developer. The user delegates a task and walks away; the agent works on its own and comes back with a PR to review.

  • Engine: siGit Code, run headless in an ephemeral sandbox (AWS), with hosted inference. The agent clones the repo, edits, runs build/test, iterates, pushes a branch.
  • Repo target: sigit.si first, then GitHub, GitLab, and other Git hosts in the future. Scope is Git only (no SVN, Mercurial, or other version control systems). The agent is Git-host agnostic behind a Git-host adapter: sigit.si is the first host, not the only one.
  • Output: a pull request on the target Git host (a pushed branch + review surface) for a human to review and merge. The agent never auto-merges.
  • Unit of work: an agent run (one delegated task → autonomous work → PR).
  • Copilot analog: Copilot coding agent (the cloud agent).
  • Status: planning. See sigit-code-cloud-agent-plan.md.

4. Naming rules (to stop the collisions)

These words are load-bearing. Use them exactly.

  • siGit Code — the local-inference coding agent. The engine.
  • siGit Code Cloud — the hosted chat product. /cloud + /cloud/sessions.
  • siGit Code Cloud Agent — the autonomous agent product (task → PR).
  • session — a siGit Code Cloud chat conversation. It belongs to siGit Code Cloud. Do not use "session(s)" to mean the agent or its runs.
  • agent run — one siGit Code Cloud Agent task. Use "run" (or "task"), never "session," for the agent.
  • on-device dashboard — the local telemetry at / (opt-in).

So: the thing at /cloud/sessions is chat sessions (siGit Code Cloud). The autonomous product is the Agent, and its work items are runs, on their own surface (anchored to a repo, since a run operates on one repository).

5. Information architecture (code.sigit.si)

Path Product Notes
/ on-device dashboard local session telemetry, opt-in
/cloud siGit Code Cloud the hosted chat
/cloud/sessions, /cloud/sessions/<uuid> siGit Code Cloud saved chat history + detail
/billing account plan / billing
(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.

The current web app (apps/code-cloud-web) already implements rows 1 to 4. The Agent surface is new and specified separately.

6. Why this is a strong position

GitHub had to build a coding agent to ship its cloud agent. siGit already ships the agent (siGit Code) and the git host (sigit.si). siGit Code Cloud Agent is mostly: take the agent we already have, run it headless in a sandbox against a repo we already host, and open a PR. The one genuinely new system is the sandbox. The Git-host-agnostic design means the same agent later runs against GitHub and GitLab repos, not just sigit.si (Git only; not SVN, Mercurial, or other VCS).