labloop 0.1.0__tar.gz

labloop-0.1.0/.gitignore

@@ -0,0 +1,19 @@
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# labloop's own run output
+labloop.jsonl
+
+.DS_Store
+.idea/
+.vscode/
+dist/

labloop-0.1.0/CHANGELOG.md

@@ -0,0 +1,96 @@
+# Changelog
+
+## 0.1.0 — unreleased
+
+First release. Everything below was built and then used in anger before
+shipping: the loop was pointed at real experiment shapes — a regression
+task, a timing benchmark, a checkpoint-heavy training script, a pure-noise
+metric — and every bug that surfaced is listed here with the behavior that
+replaced it.
+
+### The loop
+
+- Keep-or-revert over any command and any metric: `propose` mutates the
+  tree, `run` prints a number, an improvement is committed and anything
+  else reverted. Ties revert — a tie is not an improvement.
+- Nine trial outcomes, each a distinct event that sends you somewhere
+  different: `kept`, `reverted`, `no_change`, `failed`, `timed_out`,
+  `no_metric`, `not_finite`, `harness_changed`, `interrupted`. Measured
+  (`experiments/outcome_granularity/`): outcome labels beat kept/not-kept
+  on convergence with p < 0.01; the five-to-nine refinement is not
+  statistically distinguishable and the set stays for the bugs its
+  distinctions fixed.
+- Separate proposal budget (`--propose-budget`): an agent thinking longer
+  than the experiment runs is ordinary. Timeouts kill the whole process
+  group either way.
+- A run stops after ten consecutive trials with no verdict
+  (`--give-up-after`), instead of failing identically all night.
+
+### Trusting the number
+
+- `labloop noise` measures whether the metric holds still before anything
+  is optimized; reports spread and standard deviation with the exact
+  follow-up command.
+- `--min-delta` and `--confirm` for metrics that move on their own —
+  measured on pure noise over 400 replicated runs: fabricated improvement
+  falls from 23.5% to 9.9% with both, for 10% more compute. Neither makes
+  a noisy metric safe, and the docs say so.
+- Non-finite metrics never become the incumbent: one `nan` used to freeze
+  the loop permanently, reverting every later improvement while `best`
+  reported nan.
+- `--protect` digests the files that define the measurement (SHA-256,
+  per-file); a proposal that edits the evaluator or the held-out data is
+  recorded as `harness_changed` and named, not scored. The ledger itself
+  is checked on every trial without being declared. Detection, not
+  prevention — a claim the design can keep.
+- An incumbent measured under a different harness digest stops the loop
+  instead of being compared against; metric or goal drift against an
+  existing ledger is refused with the field named.
+
+### The record
+
+- Append-only JSONL ledger; half-written lines, unknown outcomes and
+  unknown fields are skipped, not fatal. Valid strict JSON always.
+- A kept trial commits exactly the proposed change plus a sparse decision
+  log (`labloop-history.jsonl`, reverted trials included); run artifacts
+  are discarded, so a checkpoint-per-trial training run does not become a
+  repository of hundreds of gigabytes.
+- Every run records its spec as a manifest line; `labloop resume`
+  continues under the last spec that can actually run — a baseline
+  re-measurement after the crash does not cost you the run spec. Same
+  incumbent, same numbering, nothing retyped. The environment is never
+  recorded.
+- One loop per ledger, enforced by an OS-released lock; a second run is
+  refused with the holder's pid, `--wait` queues. A crashed run cannot
+  leave a stale lock.
+- Research directions: fork from any kept trial (`labloop branch`), run
+  each in its own worktree against the shared ledger, per-direction
+  incumbents seeded from the fork point. `log --compare` refuses across
+  differing harnesses. A direction the ledger has never heard of is
+  refused with a did-you-mean — a typo'd `--direction` used to create a
+  phantom direction whose first trial, however bad, was kept.
+- Querying without jq: `log --json`, `--outcome`, `--direction`,
+  `--since-trial`.
+
+### Feedback to the proposer
+
+- Each proposal receives `$LABLOOP_BRIEF`: its direction's history with a
+  one-sentence `why` per trial, failures carrying their output tail;
+  scalars in `$LABLOOP_METRIC`, `$LABLOOP_GOAL`, `$LABLOOP_INCUMBENT`,
+  `$LABLOOP_TRIAL`. Written by labloop and read by the agent, never the
+  reverse.
+
+### Fixed before anyone else could hit them
+
+Eleven bugs found by dogfooding, each now a regression test: the nan
+freeze; a crash that printed nothing reported as `no_metric`; `nan` read
+differently by the two output parsers; metric names ending in punctuation
+missed in key=value form; a no-op proposal crashing the run on git's
+empty-commit refusal; an interrupted trial vanishing from the ledger (and
+recovery advice that would have committed an unmeasured change); a commit
+refused by a pre-commit hook taking the run down with an empty ledger;
+`revert` unable to undo staged changes (`git checkout -- .` restores from
+the index), wedging the tree permanently; a relative `--ledger` resolving
+against the shell's cwd and silently splitting the record; one budget
+covering both the agent and the experiment; and a proposal killed at the
+budget reported as failed rather than timed out.

labloop-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,64 @@
+# Contributing
+
+## Setup
+
+```bash
+git clone https://github.com/foothills-labs/labloop
+cd labloop
+pip install -e ".[dev]"
+```
+
+Stdlib only at runtime — the package has zero dependencies, and keeping it
+that way is a feature. `pytest`, `ruff` and `mypy` are dev-only.
+
+## The checks
+
+Everything CI runs, runnable locally:
+
+```bash
+pytest -q            # the suite; ~230 tests, under 30 seconds
+ruff check .         # lint
+mypy                 # strict, src only; the package ships py.typed
+```
+
+## How changes are made here
+
+**Tests come first.** Write the failing test, watch it fail, then write the
+code that makes it pass. A test written after the fact tends to enshrine
+whatever the code happens to do; a test written first states what it should
+do. This repository's history has a worked example: a failing test for a
+typo'd `--direction` flushed out four existing tests that were quietly
+pinning behavior nobody wanted.
+
+**Dogfood before you trust.** Most of the bugs fixed here were found by
+using the tool on realistic tasks, not by reading the code. If you add a
+user-facing behavior, drive it from the command line the way a stranger
+would — including the mistakes a stranger would make.
+
+**Measure claims.** House style is numbers over adjectives. If a change is
+justified by convergence, noise robustness, or performance, the evidence
+belongs in `experiments/` with statistics, not in the commit message as an
+assertion. Negative results are published, not discarded — see
+`experiments/outcome_granularity/RESULTS.md` for the shape.
+
+**Settled design decisions.** Some behaviors look odd and are load-bearing.
+Before "fixing" one, check whether a test asserts it on purpose:
+
+- A tie is not an improvement; equal metrics revert.
+- A missing metric is not a bad score; nine outcomes exist because each
+  sends the user somewhere different.
+- The loop refuses to start on a dirty tree; it reverts by discarding.
+- Kept commits contain the proposed change and the decision log, never
+  run artifacts.
+- The ledger is append-only, valid strict JSON, and the source of truth
+  for the incumbent.
+- The brief is written by labloop and read by the agent, never the
+  reverse.
+
+Changing any of these is a design discussion, not a cleanup.
+
+## Commit messages
+
+Explain *why*, in prose, the way the existing history does. The subject
+line states what changed; the body states what was wrong, how it was found,
+and what now holds. "Fixed bug" is not a commit message.

labloop-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Foothills Labs
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.