Claude Brainlab

A question goes in — knowledge comes out.

  The working setup of BRAIn Lab: Claude Code skills, hooks and rules
  plus a lab knowledge base that is plain git — GitHub for ideas.

  Knowledge engine ·
  GitHub for ideas ·
  Agent harness ·
  Install ·
  All skills

The repository is the lab's own configuration, packaged so another lab can install it. Claude Code
runs on the researcher's machine, a server agent keeps runs going overnight, and everything they
produce lands in one git tree that is at the same time the Obsidian vault and the lab base in GitLab.
The atlas shows the whole loop page by page, in English and Russian; this README follows
the same three tabs.

Knowledge engine

Eight stages, one loop, with the lab GitLab at the centre. Each stage is a handful of skills you
actually type.

GitHub for ideas

Code has had git for decades: history of every line, branches, review, merge. Ideas had none of it,
and once agents launch dozens of runs and read hundreds of papers overnight, knowledge without
versions turns into noise. The base gives research what git gave code: every idea, run and number
comes with its history, its checks and its author.

The base answers the question a lab loses most often: *has anyone here already tried this, and what
came out of it?* It is a GitLab group, and everything in it is ordinary git. The knowledge service that
used to sit in front of it was removed on 07-10-2026 together with its database; there is nothing to
connect to and nothing to configure.

Two halves, measured on 09-10-2026:

- What the lab knows — one repository per work, 29 of them with claims. A claim is a folder,
  claims//, holding the claim itself and the runs, series and derivations under it. Codes such
  as H-DYC-007 are stable, so they can be cited in a paper, a…