sigmoid-hunch 0.1.0__tar.gz

sigmoid_hunch-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 [yyyy] [name of copyright owner]
+
+   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.

sigmoid_hunch-0.1.0/PKG-INFO

@@ -0,0 +1,168 @@
+Metadata-Version: 2.4
+Name: sigmoid-hunch
+Version: 0.1.0
+Summary: A zero-config experiment journal for ML research: every run keeps its code, config, environment and the reason you ran it, as plain files.
+Keywords: machine-learning,experiment-tracking,reproducibility,research,mlops
+Author: Usmon N
+Author-email: Usmon N <rainxch.dev@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.11
+Project-URL: Repository, https://github.com/sigmoid-ide/hunch
+Project-URL: Issues, https://github.com/sigmoid-ide/hunch/issues
+Project-URL: Format, https://github.com/sigmoid-ide/hunch/blob/main/docs/format.md
+Description-Content-Type: text/markdown
+
+# Hunch
+
+A zero-config experiment journal for ML research. Every run keeps its code,
+config, environment, metrics and the reason you ran it, as plain files in your
+project. Each run also knows which run it came from, so your experiments form a
+history you can read back, like `git log` for results.
+
+```
+$ hunch log
+*    a7f3  Nov 14  warmup + cosine decay  val_loss 2.303                  █▅▃▂▁▁▁▁  keep  "cosine helps a bit"
+| x  c21e  Nov 13  warmup 2k, lr 6e-4     crashed, exit 1; val_loss 7.42  ▃▂▂▁▁▄▆█  drop
+|/
+*    9b40  Nov 12  warmup 1k steps        val_loss 2.323                  █▅▃▂▁▁▁▁  keep
+*    3d1c  Nov 10  baseline               val_loss 2.462                  █▅▃▂▁▁▁▁  (no conclusion yet)
+```
+
+No server, no account, no network calls, no telemetry, no dependencies.
+Hunch is the first standalone piece of Sigmoid IDE, an open-source ML research IDE.
+
+## Install
+
+```
+pip install sigmoid-hunch
+```
+
+Python 3.11 or newer. The command is `hunch` and the import is `import hunch`.
+
+## Record a run
+
+Put `hunch run` in front of the command you already use:
+
+```
+hunch run -m "warmup to fix loss spikes" -- python train.py --lr 3e-4
+```
+
+Leave out `-m` in an interactive terminal and Hunch asks why (Enter skips). It
+never asks when input is not a terminal, as in cluster jobs, background jobs and
+piped scripts. Pass `-m` in shell scripts that launch many runs.
+
+Or record from inside your code. One line records every run, however it is
+launched:
+
+```python
+import hunch
+
+run = hunch.init(config={"lr": 3e-4}, why="warmup to fix loss spikes")
+for step in range(steps):
+    ...
+    hunch.log({"train_loss": loss, "val_loss": val_loss}, step=step)
+```
+
+Use both: inside `hunch run`, `hunch.init()` joins the wrapper's run instead of
+starting a second one. The names follow W&B, so `import hunch as wandb` works
+for `init`, `log`, `config`, `summary` and `finish`. `config` can be a dict or
+an `argparse.Namespace`. Tensors are turned into numbers. In distributed
+training only rank 0 records: Hunch reads `RANK`, `OMPI_COMM_WORLD_RANK` and
+`PMI_RANK`, and inside `hunch run` also `SLURM_PROCID`.
+
+## Read it back
+
+```
+hunch ls                 recent runs, newest first
+hunch log                the tree of runs
+hunch show a7f3          everything about one run
+hunch diff 9b40 a7f3     what changed: code, config, environment and metrics
+hunch diff 9b40 a7f3 --code     the full code diff
+```
+
+```
+$ hunch diff 9b40 a7f3
+9b40  Nov 12 14:12  warmup 1k steps
+a7f3  Nov 14 09:30  warmup + cosine decay
+
+code     train.py  +6 -1   (--code for the full diff)
+config   schedule: const -> cosine
+env      no changes
+metrics  val_loss 2.323 -> 2.303 (-0.02)
+```
+
+Runs are named by the end of their id, usually 4 characters. Runs that ended in
+under 30 seconds (typos, quick crashes) are hidden; `--all` shows them.
+
+## Close the loop
+
+```
+hunch note a7f3 "cosine helps a bit" --keep     a conclusion and a verdict
+hunch note c21e --drop                          a dead end
+hunch note a7f3 --why "warmup + cosine decay"   a better why
+hunch link a7f3 --from 9b40                     fix the run it came from
+hunch set main-metric val/acc                   the metric shown for each run
+```
+
+Notes are added, never overwritten, so a run's history stays visible in
+`hunch show`.
+
+## What a run records
+
+- The command, arguments and working directory
+- The git commit and branch, the uncommitted changes to tracked files, and
+  copies of small untracked text files, so the exact code can be rebuilt
+- The config passed to `hunch.init()`
+- Python version and path, installed packages, torch and CUDA versions, GPU
+  model and driver, host, and the SLURM job id
+- Metrics, final values, output (with `hunch run`), exit status and duration
+- The why, your conclusion and your verdict
+
+## Lineage
+
+Each run's parent is picked for you: the run on the same git branch that ended
+most recently, skipping runs still in progress, runs under 30 seconds and runs
+you dropped. Branch per idea and you get a tree; stay on one branch and you get
+a straight history. Use `hunch run --from <run>` to choose the parent yourself,
+and `hunch link` to fix it later.
+
+## Where it lives
+
+Everything is in `.hunch/` at the root of your git repository (outside git, in
+the current folder), one folder per run. The
+folder ignores itself in git, so your repository is never touched. Runs never
+change after they end and have unique ids, so copying them between machines is
+a plain `rsync` of folders. The format is documented in
+[docs/format.md](docs/format.md), for anyone who wants to read it without Hunch.
+
+## Privacy
+
+Nothing leaves your machine. Only these environment variables are recorded:
+`CUDA_VISIBLE_DEVICES`, `CONDA_DEFAULT_ENV`, `VIRTUAL_ENV` and `SLURM_*`.
+Credentials are removed from git remote URLs. Command arguments are recorded as
+typed, so do not pass secrets as arguments.
+
+## Known limits in this first version
+
+- `hunch run` pipes the command's output to save it, so programs that check for
+  a terminal may turn off colors. It sets `PYTHONUNBUFFERED=1` to keep output
+  live.
+- `hunch run` passes SIGTERM on to the command. It survives SIGHUP, SIGUSR1
+  and SIGUSR2 without passing them on, because SLURM and terminals send those
+  to the whole process group, so the command already gets them.
+- Without `hunch run`, a script that ends with `sys.exit(n)` is recorded as
+  finished, and one killed outright shows as lost after 5 minutes. Use
+  `hunch run` for exact exit codes.
+- No plots beyond sparklines, no sweeps, no checkpoint storage, no importers
+  from other trackers yet.
+
+## License
+
+Apache-2.0. See [CONTRIBUTING.md](CONTRIBUTING.md) to contribute.

sigmoid_hunch-0.1.0/README.md

@@ -0,0 +1,147 @@
+# Hunch
+
+A zero-config experiment journal for ML research. Every run keeps its code,
+config, environment, metrics and the reason you ran it, as plain files in your
+project. Each run also knows which run it came from, so your experiments form a
+history you can read back, like `git log` for results.
+
+```
+$ hunch log
+*    a7f3  Nov 14  warmup + cosine decay  val_loss 2.303                  █▅▃▂▁▁▁▁  keep  "cosine helps a bit"
+| x  c21e  Nov 13  warmup 2k, lr 6e-4     crashed, exit 1; val_loss 7.42  ▃▂▂▁▁▄▆█  drop
+|/
+*    9b40  Nov 12  warmup 1k steps        val_loss 2.323                  █▅▃▂▁▁▁▁  keep
+*    3d1c  Nov 10  baseline               val_loss 2.462                  █▅▃▂▁▁▁▁  (no conclusion yet)
+```
+
+No server, no account, no network calls, no telemetry, no dependencies.
+Hunch is the first standalone piece of Sigmoid IDE, an open-source ML research IDE.
+
+## Install
+
+```
+pip install sigmoid-hunch
+```
+
+Python 3.11 or newer. The command is `hunch` and the import is `import hunch`.
+
+## Record a run
+
+Put `hunch run` in front of the command you already use:
+
+```
+hunch run -m "warmup to fix loss spikes" -- python train.py --lr 3e-4
+```
+
+Leave out `-m` in an interactive terminal and Hunch asks why (Enter skips). It
+never asks when input is not a terminal, as in cluster jobs, background jobs and
+piped scripts. Pass `-m` in shell scripts that launch many runs.
+
+Or record from inside your code. One line records every run, however it is
+launched:
+
+```python
+import hunch
+
+run = hunch.init(config={"lr": 3e-4}, why="warmup to fix loss spikes")
+for step in range(steps):
+    ...
+    hunch.log({"train_loss": loss, "val_loss": val_loss}, step=step)
+```
+
+Use both: inside `hunch run`, `hunch.init()` joins the wrapper's run instead of
+starting a second one. The names follow W&B, so `import hunch as wandb` works
+for `init`, `log`, `config`, `summary` and `finish`. `config` can be a dict or
+an `argparse.Namespace`. Tensors are turned into numbers. In distributed
+training only rank 0 records: Hunch reads `RANK`, `OMPI_COMM_WORLD_RANK` and
+`PMI_RANK`, and inside `hunch run` also `SLURM_PROCID`.
+
+## Read it back
+
+```
+hunch ls                 recent runs, newest first
+hunch log                the tree of runs
+hunch show a7f3          everything about one run
+hunch diff 9b40 a7f3     what changed: code, config, environment and metrics
+hunch diff 9b40 a7f3 --code     the full code diff
+```
+
+```
+$ hunch diff 9b40 a7f3
+9b40  Nov 12 14:12  warmup 1k steps
+a7f3  Nov 14 09:30  warmup + cosine decay
+
+code     train.py  +6 -1   (--code for the full diff)
+config   schedule: const -> cosine
+env      no changes
+metrics  val_loss 2.323 -> 2.303 (-0.02)
+```
+
+Runs are named by the end of their id, usually 4 characters. Runs that ended in
+under 30 seconds (typos, quick crashes) are hidden; `--all` shows them.
+
+## Close the loop
+
+```
+hunch note a7f3 "cosine helps a bit" --keep     a conclusion and a verdict
+hunch note c21e --drop                          a dead end
+hunch note a7f3 --why "warmup + cosine decay"   a better why
+hunch link a7f3 --from 9b40                     fix the run it came from
+hunch set main-metric val/acc                   the metric shown for each run
+```
+
+Notes are added, never overwritten, so a run's history stays visible in
+`hunch show`.
+
+## What a run records
+
+- The command, arguments and working directory
+- The git commit and branch, the uncommitted changes to tracked files, and
+  copies of small untracked text files, so the exact code can be rebuilt
+- The config passed to `hunch.init()`
+- Python version and path, installed packages, torch and CUDA versions, GPU
+  model and driver, host, and the SLURM job id
+- Metrics, final values, output (with `hunch run`), exit status and duration
+- The why, your conclusion and your verdict
+
+## Lineage
+
+Each run's parent is picked for you: the run on the same git branch that ended
+most recently, skipping runs still in progress, runs under 30 seconds and runs
+you dropped. Branch per idea and you get a tree; stay on one branch and you get
+a straight history. Use `hunch run --from <run>` to choose the parent yourself,
+and `hunch link` to fix it later.
+
+## Where it lives
+
+Everything is in `.hunch/` at the root of your git repository (outside git, in
+the current folder), one folder per run. The
+folder ignores itself in git, so your repository is never touched. Runs never
+change after they end and have unique ids, so copying them between machines is
+a plain `rsync` of folders. The format is documented in
+[docs/format.md](docs/format.md), for anyone who wants to read it without Hunch.
+
+## Privacy
+
+Nothing leaves your machine. Only these environment variables are recorded:
+`CUDA_VISIBLE_DEVICES`, `CONDA_DEFAULT_ENV`, `VIRTUAL_ENV` and `SLURM_*`.
+Credentials are removed from git remote URLs. Command arguments are recorded as
+typed, so do not pass secrets as arguments.
+
+## Known limits in this first version
+
+- `hunch run` pipes the command's output to save it, so programs that check for
+  a terminal may turn off colors. It sets `PYTHONUNBUFFERED=1` to keep output
+  live.
+- `hunch run` passes SIGTERM on to the command. It survives SIGHUP, SIGUSR1
+  and SIGUSR2 without passing them on, because SLURM and terminals send those
+  to the whole process group, so the command already gets them.
+- Without `hunch run`, a script that ends with `sys.exit(n)` is recorded as
+  finished, and one killed outright shows as lost after 5 minutes. Use
+  `hunch run` for exact exit codes.
+- No plots beyond sparklines, no sweeps, no checkpoint storage, no importers
+  from other trackers yet.
+
+## License
+
+Apache-2.0. See [CONTRIBUTING.md](CONTRIBUTING.md) to contribute.

sigmoid_hunch-0.1.0/pyproject.toml

@@ -0,0 +1,46 @@
+[project]
+name = "sigmoid-hunch"
+version = "0.1.0"
+description = "A zero-config experiment journal for ML research: every run keeps its code, config, environment and the reason you ran it, as plain files."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+dependencies = []
+keywords = [
+    "machine-learning",
+    "experiment-tracking",
+    "reproducibility",
+    "research",
+    "mlops",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Science/Research",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+]
+
+[[project.authors]]
+name = "Usmon N"
+email = "rainxch.dev@gmail.com"
+
+[project.scripts]
+hunch = "hunch.cli:main"
+
+[project.urls]
+Repository = "https://github.com/sigmoid-ide/hunch"
+Issues = "https://github.com/sigmoid-ide/hunch/issues"
+Format = "https://github.com/sigmoid-ide/hunch/blob/main/docs/format.md"
+
+[build-system]
+requires = ["uv_build>=0.11.16,<0.12.0"]
+build-backend = "uv_build"
+
+[tool.uv.build-backend]
+module-name = "hunch"
+
+[dependency-groups]
+dev = ["pytest>=9.2.0"]

sigmoid_hunch-0.1.0/pyproject.toml.orig

@@ -0,0 +1,41 @@
+[project]
+name = "sigmoid-hunch"
+version = "0.1.0"
+description = "A zero-config experiment journal for ML research: every run keeps its code, config, environment and the reason you ran it, as plain files."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [
+    { name = "Usmon N", email = "rainxch.dev@gmail.com" }
+]
+requires-python = ">=3.11"
+dependencies = []
+keywords = ["machine-learning", "experiment-tracking", "reproducibility", "research", "mlops"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Science/Research",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+]
+
+[project.scripts]
+hunch = "hunch.cli:main"
+
+[project.urls]
+Repository = "https://github.com/sigmoid-ide/hunch"
+Issues = "https://github.com/sigmoid-ide/hunch/issues"
+Format = "https://github.com/sigmoid-ide/hunch/blob/main/docs/format.md"
+
+[build-system]
+requires = ["uv_build>=0.11.16,<0.12.0"]
+build-backend = "uv_build"
+
+[tool.uv.build-backend]
+module-name = "hunch"
+
+[dependency-groups]
+dev = [
+    "pytest>=9.2.0",
+]

sigmoid_hunch-0.1.0/src/hunch/__init__.py

@@ -0,0 +1,33 @@
+"""Hunch: a zero-config experiment journal for ML research.
+
+Every run keeps its code, config, environment, metrics and the reason you ran
+it, as plain files in the project's .hunch folder.
+
+    import hunch
+    run = hunch.init(config={"lr": 3e-4}, why="warmup to fix loss spikes")
+    hunch.log({"val_loss": 2.31}, step=1000)
+"""
+
+from importlib import metadata as _metadata
+
+from .api import Run, finish, init, log
+
+try:
+    __version__ = _metadata.version("sigmoid-hunch")
+except _metadata.PackageNotFoundError:
+    __version__ = "0+unknown"
+
+__all__ = ["Run", "init", "log", "finish", "config", "summary", "run"]
+
+
+def __getattr__(name):
+    # hunch.config, hunch.summary and hunch.run follow the active run, as in W&B.
+    if name in ("config", "summary", "run"):
+        from . import api
+
+        if name == "run":
+            return api._active
+        if api._active is None:
+            raise AttributeError(f"hunch.{name} is available after hunch.init()")
+        return getattr(api._active, name)
+    raise AttributeError(f"module 'hunch' has no attribute '{name}'")

sigmoid_hunch-0.1.0/src/hunch/__main__.py

@@ -0,0 +1,5 @@
+import sys
+
+from .cli import main
+
+sys.exit(main())