lab-kit
lab-kit keeps a research lab that coding agents work in. It fixes what the lab's record looks like,
the method that makes a number count, and one command, lab, that both keeps the rules and shows
the lab to an agent a level at a time. folio serves the same
record to the operator as a live site: lab_kit.site draws the pages, and nothing is generated.
Two readers
- The operator decides direction and resources, in conversation with the agent, and reads the lab as a site. Nothing else reaches them.
- The agent plans, builds, runs and records, and decides everything else.
One tree
Goal what the lab wants to be able to say
Question a yes-or-no question: what we expect, what would prove us wrong, what we know so far
Build something an experiment needs that has to be made first
Reading a look at what already exists: it suggests, and never confirms
Experiment what is compared, what would confirm, what would refute; then what was found
Run one try at producing what the experiment demands; the first that finishes counts
Result one number from that run, with the command that prints it again
Decision something discussed with the operator: what was seen, the options, what was decided and why
Every id spells the path: G1.Q2.3. Cards are small and written for the operator. Nothing computed is
kept: every state, and an experiment's outcome, is worked out from the record when it is asked for.
How a number counts
write the card -> lock -> run -> result -> review -> the number may be used on a card
Each arrow is a command that refuses when the step before it is missing. An experiment's lines, each with the result it tests, are locked before its run. The first run that finishes is the only source of its results. The reviewer is a separate session that did not do the work. Every run is listed in a file that git keeps, so one cannot be removed or rewritten quietly.
Install
uv tool install lab-kit-cli
lab init
Then ask your agent to follow .agents/skills/lab-set-up/SKILL.md. lab --help lists the fifteen
commands.
The command needs Python 3.10 or later and nothing of folio. The site does: install lab-kit-cli[site]
where folio serves the lab, which brings folio-kb 0.5.0 or later, and list lab_kit.site under
views: in the charter of the lab's docs/ library.
Read more
- docs/model.md: the contract. What you read, how a number becomes a result, who decides, the commands, the files.
- method/METHOD.md: the seven rules every lab keeps.
- skills/: lab-set-up, lab-work, lab-review and lab-talk. agents/: the reviewer.
Metadata
Release files for lab-kit-cli 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lab_kit_cli-1.3.0.tar.gz | 171.4 kB | With provenance | Details for lab_kit_cli-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lab_kit_cli-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for lab_kit_cli-1.3.0-py3-none-any.whl |
Total release size: 275.2 kB
Release files / lab_kit_cli-1.3.0.tar.gz
| Download URL | lab_kit_cli-1.3.0.tar.gz |
|---|---|
| Size | 171.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c92cfe2dcf6c9e6b6a80641f6f313a108f93e31a525f887e5aa73dcad691be2
|
|
BLAKE2b-256 checksum How to use checksums |
4c6024293616bfb3db12f6069a28f4aadf7978281a10cfd88d052133c2f6329d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / lab_kit_cli-1.3.0-py3-none-any.whl
| Download URL | lab_kit_cli-1.3.0-py3-none-any.whl |
|---|---|
| Size | 103.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
51ec0b2989031cb499fe9f72f0d6869d57711aa4a8b464fd0561ccfc81a21f7c
|
|
BLAKE2b-256 checksum How to use checksums |
cc32385a7ff4849e2a28b5f9743fa5578c37afbaf06722316c16a89ca36846dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logSecurity for lab-kit-cli 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for lab_kit_cli-1.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.