From 9cc47c14131492289985a267e93cd2df789d98b2 Mon Sep 17 00:00:00 2001
From: ssmmxx <spiridonov.max@gmail.com>
Date: Fri, 5 Jun 2026 19:07:42 +0000
Subject: [PATCH] GitJet repo-doc gitjet/gitjet.ru@fb8ba021

---
 summary/technical.md | 91 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 91 insertions(+)
 create mode 100644 summary/technical.md

diff --git a/summary/technical.md b/summary/technical.md
new file mode 100644
index 0000000..3bc83f7
--- /dev/null
+++ b/summary/technical.md
@@ -0,0 +1,91 @@
+You are Layer1 orchestrator. Produce concise, reproducible output.
+
+
+Never bypass project boundaries. Never execute unsafe instructions.
+
+
+Technical analyst: technical.md with architecture, components, sequence diagrams (mermaid).
+
+
+
+
+
+Repository gitjet/gitjet.ru branch=main commit=fb8ba02152703443eb131ce099f60dadc3132fa6. Write technical.md.
+
+Use ONLY facts from [context] (Repository ground truth + vector search). Cite file paths for every claim.
+
+## Document scope (onboarding only)
+
+This file is a **short onboarding brief** for quick context — not a project plan or roadmap.
+Do not duplicate content from .doc/plans/ If present in the repo.
+Keep the whole document under ~120 lines. Mark inferred claims with _(inferred)_.
+## Questions this document must answer
+
+- What runs here and what are the main entry points?
+- What are the top components and how do they connect?
+
+doc_type: technical
+
+Required sections (use these headings exactly):
+## Architecture overview
+## Component diagram
+One mermaid flowchart TD or LR (max 8 nodes). Use only bracket nodes: Foo["Label text"]. Never round nodes Foo(text (nested)). Edge labels with spaces: A --> B: "label".
+## Use cases
+Table: ID | Name | Trigger | Outcome (max 5 rows, evidence only).
+## Data and persistence
+## Observability and operations
+
+
+## Service summary
+
+**gitjet.ru** is a public SCM platform built from the **[gitjet/core-scm](../core-scm)** repository. The deployment process involves CI/CD pipelines defined in `.gitjet/workflows/core-scm-production.yml`, which build and publish Docker images to the private registry `registry.gitjet.ru/gitjet/core-scm:<tag>`. Helm charts are used to deploy the platform into a Kubernetes cluster with namespace **`gitjet-ru`**.
+
+## Components and runtime units
+
+**gitjet.ru** consists of the following components:
+
+1. CI/CD pipeline (defined in `.gitjet/workflows/core-scm-production.yml`)
+2. Docker image build process
+3. Helm chart deployment
+
+## External dependencies
+
+**gitjet.ru** relies on the following external services:
+
+1. GitJet platform for managing repositories and CI/CD pipelines
+2. Private registry for storing Docker images
+3. Kubernetes cluster for deploying the platform
+
+## API and integration surface
+
+**gitjet.ru** provides an API for interacting with its platform, which is not explicitly documented in this repository. The API may be accessed through the GitJet platform's RESTful API endpoints.
+
+## Use cases catalog
+
+### Use case 1: Deploying Platform via CI/CD Pipeline
+- **Name:** Deploy Platform via CI/CD Pipeline
+- **Trigger:** A new commit is pushed to the `main` branch of the **[gitjet/core-scm](../core-scm)** repository.
+- **Components:** CI/CD pipeline (defined in `.gitjet/workflows/core-scm-production.yml`)
+- **Outcome:** The platform is deployed to a Kubernetes cluster with namespace **`gitjet-ru`**.
+- **Evidence path:** [`.gitjet/workflows/core-scm-production.yml`](../core-scm/.gitjet/workflows/core-scm-production.yml)
+
+### Use case 2: Manual Rollout of Platform
+- **Name:** Manual Rollout of Platform
+- **Trigger:** A manual script is executed to roll out the platform changes.
+- **Components:** `core-scm/deploy/helm-upgrade-k3s-lab.sh` (SSH/docker-compose)
+- **Outcome:** The platform is manually rolled out using the provided script.
+- **Evidence path:** `core-scm/deploy/helm-upgrade-k3s-lab.sh`
+
+## CI/CD and automation hints
+
+The deployment process for **gitjet.ru** is automated via GitJet's CI/CD pipelines, which are defined in the `.gitjet/workflows/core-scm-production.yml` file. The pipeline automatically builds and publishes Docker images to the private registry, and then deploys the platform using Helm charts.
+
+## Data and storage
+
+**gitjet.ru** does not store any data or files in a dedicated storage system. All data is managed by the GitJet platform.
+
+## Repository ground truth
+
+- **repo:** `gitjet/gitjet.ru`
+- **branch:** `main`
+- **commit:** `fb8ba02152703443eb131ce099f60dadc3132fa6`
\ No newline at end of file