Questions a company will ask.

Anadolu turns a bug reported in Teams, Slack, or Mattermost into a tested pull request on your GitHub. Someone mentions it in a mapped channel. It reproduces the bug, then waits. A project manager authorizes the fix. An approver accepts the pull request. Your pipeline deploys. Anadolu does not deploy.

A company with GitHub and tests, and a chat where bugs are reported. The pilot is Teams. Slack is the same product if that is already the chat. A company with neither gets one Mattermost workspace we host, at a subdomain of chat.anadolu-ai.online. One company has one primary chat. GitHub is required before a mention becomes a case.

No. Gate 2 submits the review as the person who clicked, through their own GitHub account link. Anadolu never approves its own pull request. A category can later earn the right to skip that second yes, after a clean track record the company configured. It cannot skip the authorization before any code is edited.

No. After the pull request merges, the company pipeline deploys. Anadolu watches that window. If the same error returns, it opens a revert pull request and pauses that category. It does not roll production back itself, and it does not hold a deploy button.

The thread gets the classification and no sandbox starts. Config, data, a user error, an outage, a duplicate, a feature request, or an unknown channel is answered there and stops. A thin report gets one question, then a wait. Anadolu is not an incident responder and not a place to ask for a new feature.

Schema, migrations, infrastructure, CI and build config, dependency manifests and lockfiles, secrets, environment files, and the policy file. Paths the company marked for money, auth, or permissions always stay with a person. The agent may propose a fix on other paths. A hook blocks a write the policy locks.

On the card in the thread. Gate 1 is Approve or Reject after a failing test. Gate 2 accepts the pull request or requests changes. The console is where an admin connects the company, maps channels, and reads the audit. A drawing of the card on this website does not decide a case.

Microsoft Entra for a Teams company. An Entra admin consents once. Slack for a Slack company, installed by a workspace admin. Email and a password for a Mattermost company we host. The session is ours. There is no Google button. GitHub is connected after sign-in, by someone who can install a GitHub App.

One design partner with Teams, GitHub, and tests that can fail for a real reason. Pull requests only. Auto-merge is off. We do not deploy, and we do not change schema. Slack and Mattermost are part of the product and are not required of the first partner. A company with Slack instead can say so in the note.

A revert pull request is opened and that category is paused. Anadolu does not roll production back itself. The case records the revert, then hands off. A later report of the same bug opens a new case. It does not reopen the resolved one. The pilot leaves auto-merge off, so a person accepted the pull request.