From d8c94eb2e4832250513dcafa024ece3b2206909d Mon Sep 17 00:00:00 2001
From: Giga <Giga.Chkhikvadze@gmail.com>
Date: Fri, 31 Jul 2026 13:10:43 +0400
Subject: [PATCH] chore: Company OS impact check and releases

Every pull request declares whether a customer can notice it; significant:
false is a complete answer. Pushes to the default branch maintain a Release
pull request from the conventional commits already written here.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 .github/PULL_REQUEST_TEMPLATE.md | 44 ++++++++++++++++++++++++++++++++
 .github/workflows/company-os.yml | 33 ++++++++++++++++++++++++
 2 files changed, 77 insertions(+)
 create mode 100644 .github/PULL_REQUEST_TEMPLATE.md
 create mode 100644 .github/workflows/company-os.yml

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 00000000..30788335
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,44 @@
+## What and why
+
+<!-- Normal description for reviewers. -->
+
+## Impact
+
+<!--
+Fill the block below. It is the only place "what does a customer notice, and
+why did we do this" is ever cheap and accurate, because you know it right now
+and a diff cannot answer it later.
+
+`significant: false` is a complete answer and needs nothing else. Use it for
+internal renames, behaviour-preserving refactors, formatting, editorial doc
+edits, tests, dependency bumps, build changes, and internal logging.
+
+Use `significant: true` when someone outside the team could notice without
+reading the code: a new or removed endpoint, field, screen or permission; a
+changed request or response shape; the same call returning something different;
+changed limits, quotas, timeouts or price; accuracy or latency changed enough to
+alter a published claim; changed supported regions, integrations or client
+versions; changed authentication, retention or what data is collected.
+
+It is not a size test. A one-line rate-limit change counts. A thousand-line
+refactor that preserves every behaviour does not.
+-->
+
+<!-- company-os:impact -->
+```yaml
+significant: false
+```
+
+<!-- When significant, use this shape instead:
+
+<!-- company-os:impact -->
+```yaml
+significant: true
+category: surface-added   # surface-added | surface-removed | shape-changed | behaviour-changed | limits-changed | quality-changed | availability-changed | security-or-privacy-changed
+user_impact: >-
+  What a customer can now do, or can no longer do, in their words.
+why: >-
+  The problem this removes. Not the code.
+evidence: https://...     # docs, changelog, or a screenshot
+```
+-->
diff --git a/.github/workflows/company-os.yml b/.github/workflows/company-os.yml
new file mode 100644
index 00000000..0f3fa748
--- /dev/null
+++ b/.github/workflows/company-os.yml
@@ -0,0 +1,33 @@
+name: Company OS
+
+# Copy this file into a product repository. It is the whole integration.
+#
+# Two things happen here, and neither needs editing again — the checks, the
+# vocabulary, the release strategy and the mapping from this repository to its
+# project all live in Company OS:
+#
+#   impact   every pull request must say whether a customer can notice it.
+#            `significant: false` is one line and passes.
+#   release  conventional commits accumulate into a Release pull request;
+#            merging it tags and publishes a GitHub Release.
+#
+# Uses the organization secret COMPANY_OS_TOKEN. Nothing to configure per repo.
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize, reopened, closed]
+  push:
+    branches: [main]
+
+jobs:
+  impact:
+    if: github.event_name == 'pull_request'
+    uses: Desearch-ai/company-os/.github/workflows/pr-impact.yml@main
+    secrets: inherit
+
+  release:
+    if: github.event_name == 'push'
+    uses: Desearch-ai/company-os/.github/workflows/release.yml@main
+    with:
+      release_type: simple
+    secrets: inherit