Tsqoba (წ) TSQOBA

Home

Probabilistic input. Deterministic acceptance.

Tsqoba is a brownfield agent runtime for existing repositories. Its strongest current public slice is a repo-run write-path layer: a candidate change stays provisional until the runtime accepts it. That makes it possible to stop some cheap bad writes before patch apply and keep the result reviewable.

Local hooks and CI already solve many practical checks. This site is narrower. It shows one repo-run layer that stayed useful during dogfooding because it can reject some cheap bad writes early and keep reasons, reports, replays, exceptions, and retained material on the same surface.

Current phase: core refactor and internal dogfooding. Public pilots are not open.

See current status Browse cases

An agent multiplies what already exists

Prompts do not erase local habits. A repository teaches a model by what it accepts.

Most software work happens in brownfield systems. In that environment, accepted code teaches the next move: interfaces, naming patterns, test habits, tolerated shortcuts, and failure boundaries.

That is why acceptance matters more than prompt polish. If a cheap shortcut keeps landing, it compounds. If some mistakes are refused early and the refusal stays readable, the next move changes too.

Tsqoba is built around that practical loop. The public site shows one narrow layer inside it: a repo-run write-path layer, plus the reasons, cases, and retained material around that layer.

  • accepted code teaches more than prompts
  • tolerated shortcuts compound quickly
  • reviewable rejects are cheaper than silent drift

Where to read next

Articles

Current mechanics, boundaries, and trade-offs.

Open articles

Cases

One operating episode at a time: trigger, response, outcome.

Open cases

Artifacts

Retained material: screenshots, ledgers, diffs, inventories, and bundles.

Open artifacts

Status

What changed, what is live, and what still needs work.

Open status

Field reports

Occasional notes when the public picture changes enough to matter.

Occasional email updates

Low-frequency notes. New reports appear when the operating story changes in a way worth publishing.

Subscribe

Contact

For brownfield repositories, policy-controlled change, reviewable rejects, replay surfaces, and long-lived codebases.

Email: [email protected]

Telegram: @alena_konovalova

Email us Message on Telegram

Privacy

No tracking wall. No analytics theater.

Mailing-list signup is handled by MailerLite; direct contact links stay simple.