hunch-ai 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- hunch_ai-0.1.0/.gitignore +182 -0
- hunch_ai-0.1.0/LICENSE +202 -0
- hunch_ai-0.1.0/NOTICE +14 -0
- hunch_ai-0.1.0/PKG-INFO +96 -0
- hunch_ai-0.1.0/README.md +70 -0
- hunch_ai-0.1.0/pyproject.toml +44 -0
- hunch_ai-0.1.0/src/hunch/__init__.py +66 -0
- hunch_ai-0.1.0/src/hunch/cli.py +36 -0
- hunch_ai-0.1.0/src/hunch/core.py +2647 -0
- hunch_ai-0.1.0/src/hunch/models.py +134 -0
- hunch_ai-0.1.0/src/hunch/recipes/agent_eval/README.md +29 -0
- hunch_ai-0.1.0/src/hunch/recipes/agent_eval/claims.yml +19 -0
- hunch_ai-0.1.0/src/hunch/recipes/agent_eval/fix_correct.yml +19 -0
- hunch_ai-0.1.0/src/hunch/recipes/agent_eval/verified.yml +14 -0
- hunch_ai-0.1.0/src/hunch/recipes/tickets/README.md +19 -0
- hunch_ai-0.1.0/src/hunch/recipes/tickets/ticket_triage.yml +30 -0
- hunch_ai-0.1.0/src/hunch/recipes/tickets/tickets.csv +41 -0
- hunch_ai-0.1.0/src/hunch/spec.schema.json +335 -0
- hunch_ai-0.1.0/src/hunch/traces.py +251 -0
|
@@ -0,0 +1,182 @@
|
|
|
1
|
+
# hunch: answer stores and results (.hunch/), downloaded example data (.cache/)
|
|
2
|
+
.hunch/
|
|
3
|
+
.cache/
|
|
4
|
+
# committed on purpose: it only points uv at ./uv.toml (no secrets), even if a global gitignore ignores .envrc
|
|
5
|
+
!.envrc
|
|
6
|
+
|
|
7
|
+
# Created by https://www.toptal.com/developers/gitignore/api/python
|
|
8
|
+
# Edit at https://www.toptal.com/developers/gitignore?templates=python
|
|
9
|
+
|
|
10
|
+
### Python ###
|
|
11
|
+
# Byte-compiled / optimized / DLL files
|
|
12
|
+
__pycache__/
|
|
13
|
+
*.py[cod]
|
|
14
|
+
*$py.class
|
|
15
|
+
|
|
16
|
+
# C extensions
|
|
17
|
+
*.so
|
|
18
|
+
|
|
19
|
+
# Distribution / packaging
|
|
20
|
+
.Python
|
|
21
|
+
build/
|
|
22
|
+
develop-eggs/
|
|
23
|
+
dist/
|
|
24
|
+
downloads/
|
|
25
|
+
eggs/
|
|
26
|
+
.eggs/
|
|
27
|
+
lib/
|
|
28
|
+
lib64/
|
|
29
|
+
parts/
|
|
30
|
+
sdist/
|
|
31
|
+
var/
|
|
32
|
+
wheels/
|
|
33
|
+
share/python-wheels/
|
|
34
|
+
*.egg-info/
|
|
35
|
+
.installed.cfg
|
|
36
|
+
*.egg
|
|
37
|
+
MANIFEST
|
|
38
|
+
|
|
39
|
+
# PyInstaller
|
|
40
|
+
# Usually these files are written by a python script from a template
|
|
41
|
+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
|
|
42
|
+
*.manifest
|
|
43
|
+
*.spec
|
|
44
|
+
|
|
45
|
+
# Installer logs
|
|
46
|
+
pip-log.txt
|
|
47
|
+
pip-delete-this-directory.txt
|
|
48
|
+
|
|
49
|
+
# Unit test / coverage reports
|
|
50
|
+
htmlcov/
|
|
51
|
+
.tox/
|
|
52
|
+
.nox/
|
|
53
|
+
.coverage
|
|
54
|
+
.coverage.*
|
|
55
|
+
.cache
|
|
56
|
+
nosetests.xml
|
|
57
|
+
coverage.xml
|
|
58
|
+
*.cover
|
|
59
|
+
*.py,cover
|
|
60
|
+
.hypothesis/
|
|
61
|
+
.pytest_cache/
|
|
62
|
+
cover/
|
|
63
|
+
|
|
64
|
+
# Translations
|
|
65
|
+
*.mo
|
|
66
|
+
*.pot
|
|
67
|
+
|
|
68
|
+
# Django stuff:
|
|
69
|
+
*.log
|
|
70
|
+
local_settings.py
|
|
71
|
+
db.sqlite3
|
|
72
|
+
db.sqlite3-journal
|
|
73
|
+
|
|
74
|
+
# Flask stuff:
|
|
75
|
+
instance/
|
|
76
|
+
.webassets-cache
|
|
77
|
+
|
|
78
|
+
# Scrapy stuff:
|
|
79
|
+
.scrapy
|
|
80
|
+
|
|
81
|
+
# Sphinx documentation
|
|
82
|
+
docs/_build/
|
|
83
|
+
|
|
84
|
+
# PyBuilder
|
|
85
|
+
.pybuilder/
|
|
86
|
+
target/
|
|
87
|
+
|
|
88
|
+
# Jupyter Notebook
|
|
89
|
+
.ipynb_checkpoints
|
|
90
|
+
|
|
91
|
+
# IPython
|
|
92
|
+
profile_default/
|
|
93
|
+
ipython_config.py
|
|
94
|
+
|
|
95
|
+
# pyenv
|
|
96
|
+
# For a library or package, you might want to ignore these files since the code is
|
|
97
|
+
# intended to run in multiple environments; otherwise, check them in:
|
|
98
|
+
# .python-version
|
|
99
|
+
|
|
100
|
+
# pipenv
|
|
101
|
+
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
|
|
102
|
+
# However, in case of collaboration, if having platform-specific dependencies or dependencies
|
|
103
|
+
# having no cross-platform support, pipenv may install dependencies that don't work, or not
|
|
104
|
+
# install all needed dependencies.
|
|
105
|
+
#Pipfile.lock
|
|
106
|
+
|
|
107
|
+
# poetry
|
|
108
|
+
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
|
|
109
|
+
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
|
110
|
+
# commonly ignored for libraries.
|
|
111
|
+
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
|
|
112
|
+
#poetry.lock
|
|
113
|
+
|
|
114
|
+
# pdm
|
|
115
|
+
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
|
|
116
|
+
#pdm.lock
|
|
117
|
+
# pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
|
|
118
|
+
# in version control.
|
|
119
|
+
# https://pdm.fming.dev/#use-with-ide
|
|
120
|
+
.pdm.toml
|
|
121
|
+
|
|
122
|
+
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
|
|
123
|
+
__pypackages__/
|
|
124
|
+
|
|
125
|
+
# Celery stuff
|
|
126
|
+
celerybeat-schedule
|
|
127
|
+
celerybeat.pid
|
|
128
|
+
|
|
129
|
+
# SageMath parsed files
|
|
130
|
+
*.sage.py
|
|
131
|
+
|
|
132
|
+
# Environments
|
|
133
|
+
.env
|
|
134
|
+
.venv
|
|
135
|
+
env/
|
|
136
|
+
venv/
|
|
137
|
+
ENV/
|
|
138
|
+
env.bak/
|
|
139
|
+
venv.bak/
|
|
140
|
+
|
|
141
|
+
# Spyder project settings
|
|
142
|
+
.spyderproject
|
|
143
|
+
.spyproject
|
|
144
|
+
|
|
145
|
+
# Rope project settings
|
|
146
|
+
.ropeproject
|
|
147
|
+
|
|
148
|
+
# mkdocs documentation
|
|
149
|
+
/site
|
|
150
|
+
|
|
151
|
+
# mypy
|
|
152
|
+
.mypy_cache/
|
|
153
|
+
.dmypy.json
|
|
154
|
+
dmypy.json
|
|
155
|
+
|
|
156
|
+
# Pyre type checker
|
|
157
|
+
.pyre/
|
|
158
|
+
|
|
159
|
+
# pytype static type analyzer
|
|
160
|
+
.pytype/
|
|
161
|
+
|
|
162
|
+
# Cython debug symbols
|
|
163
|
+
cython_debug/
|
|
164
|
+
|
|
165
|
+
# PyCharm
|
|
166
|
+
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
|
|
167
|
+
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
|
|
168
|
+
# and can be added to the global gitignore or merged into this file. For a more nuclear
|
|
169
|
+
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
|
|
170
|
+
#.idea/
|
|
171
|
+
|
|
172
|
+
### Python Patch ###
|
|
173
|
+
# Poetry local configuration file - https://python-poetry.org/docs/configuration/#local-configuration
|
|
174
|
+
poetry.toml
|
|
175
|
+
|
|
176
|
+
# ruff
|
|
177
|
+
.ruff_cache/
|
|
178
|
+
|
|
179
|
+
# LSP config files
|
|
180
|
+
pyrightconfig.json
|
|
181
|
+
|
|
182
|
+
# End of https://www.toptal.com/developers/gitignore/api/python
|
hunch_ai-0.1.0/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
hunch_ai-0.1.0/NOTICE
ADDED
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
hunch
|
|
2
|
+
Copyright 2026 Mehmet Öner Yalçın
|
|
3
|
+
|
|
4
|
+
This product includes third-party data:
|
|
5
|
+
|
|
6
|
+
- prototype/examples/banking77/*.csv: samples of the BANKING77 dataset by PolyAI
|
|
7
|
+
(https://github.com/PolyAI-LDN/task-specific-datasets), licensed CC BY 4.0.
|
|
8
|
+
See prototype/examples/banking77/NOTICE.md.
|
|
9
|
+
- prototype/examples/swe_agent/traces.csv: derived sample of SWE-agent-trajectories by Nebius
|
|
10
|
+
(https://huggingface.co/datasets/nebius/SWE-agent-trajectories), licensed CC BY 4.0.
|
|
11
|
+
See prototype/examples/swe_agent/NOTICE.md.
|
|
12
|
+
- prototype/review_panel/claude_code/packets/*.json: excerpts of Trace Commons — Agent Traces
|
|
13
|
+
(https://huggingface.co/datasets/trace-commons/agent-traces), licensed CC BY 4.0.
|
|
14
|
+
See prototype/examples/claude_code/NOTICE.md.
|
hunch_ai-0.1.0/PKG-INFO
ADDED
|
@@ -0,0 +1,96 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: hunch-ai
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: Write the questions your code asks a model as specs, then test, diff and review the answers like code
|
|
5
|
+
Project-URL: Documentation, https://fuguai.mintlify.site
|
|
6
|
+
Project-URL: Source, https://github.com/oneryalcin/hunch
|
|
7
|
+
Project-URL: Issues, https://github.com/oneryalcin/hunch/issues
|
|
8
|
+
License-Expression: Apache-2.0
|
|
9
|
+
License-File: LICENSE
|
|
10
|
+
License-File: NOTICE
|
|
11
|
+
Keywords: agents,calibration,classification,evals,judgments,llm,testing
|
|
12
|
+
Classifier: Development Status :: 3 - Alpha
|
|
13
|
+
Classifier: Intended Audience :: Developers
|
|
14
|
+
Classifier: Programming Language :: Python :: 3
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.14
|
|
18
|
+
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
|
|
19
|
+
Classifier: Topic :: Software Development :: Testing
|
|
20
|
+
Requires-Python: >=3.12
|
|
21
|
+
Requires-Dist: httpx>=0.27
|
|
22
|
+
Requires-Dist: pyyaml>=6
|
|
23
|
+
Provides-Extra: pydantic
|
|
24
|
+
Requires-Dist: pydantic>=2; extra == 'pydantic'
|
|
25
|
+
Description-Content-Type: text/markdown
|
|
26
|
+
|
|
27
|
+
# hunch
|
|
28
|
+
|
|
29
|
+
Your code asks a model small questions all day. Which team should get this ticket? Did the agent's fix work? Is this shell command safe to run? hunch writes each question down as a spec, a short YAML file in git, and tells you how often the answers are right.
|
|
30
|
+
|
|
31
|
+
- `hunch run` asks the question of every row and stores each answer under its exact input, so a re-run costs nothing.
|
|
32
|
+
- `hunch test` measures accuracy against gold, an answer key or your own reviews, as a range, not a single number.
|
|
33
|
+
- `hunch diff` shows which rows a change to the question would flip, before you ship it.
|
|
34
|
+
- `hunch review` shows you the rows worth reading, and your verdicts become gold.
|
|
35
|
+
|
|
36
|
+
If you know dbt, the idea will feel familiar: dbt did this for SQL; hunch does it for model judgments.
|
|
37
|
+
|
|
38
|
+
## Install
|
|
39
|
+
|
|
40
|
+
```sh
|
|
41
|
+
uv tool install hunch-ai # or: pip install hunch-ai
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
The package is `hunch-ai`; the command and the import are `hunch`. Python 3.12 or later.
|
|
45
|
+
|
|
46
|
+
## Try it
|
|
47
|
+
|
|
48
|
+
```sh
|
|
49
|
+
export TYPESAFE_API_KEY=... # the recipe's engine is TypeSafe's Jev
|
|
50
|
+
hunch init tickets my-tickets # a spec, 40 sample tickets and a README
|
|
51
|
+
cd my-tickets
|
|
52
|
+
hunch compile . # the exact request and its cost; nothing is sent
|
|
53
|
+
hunch run . --max-cost 0.01 # about $0.001
|
|
54
|
+
hunch test .
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
A spec looks like this:
|
|
58
|
+
|
|
59
|
+
```yaml
|
|
60
|
+
judgment: ticket_triage
|
|
61
|
+
model: jev-1.13.0
|
|
62
|
+
source: tickets.csv
|
|
63
|
+
key: id
|
|
64
|
+
state: [subject, body] # the columns the model sees
|
|
65
|
+
|
|
66
|
+
questions:
|
|
67
|
+
department:
|
|
68
|
+
type: choice
|
|
69
|
+
instructions: Which team should handle this support ticket?
|
|
70
|
+
criteria:
|
|
71
|
+
billing: Problems with money already charged or owed
|
|
72
|
+
technical: Something is broken, slow, or misbehaving
|
|
73
|
+
sales: Buying more or buying differently
|
|
74
|
+
act: 0.80 # below this confidence, a person reviews it
|
|
75
|
+
gold: gold_department # the answer key, if you have one
|
|
76
|
+
|
|
77
|
+
tests:
|
|
78
|
+
department: {min_accuracy: 0.90}
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
Engines: TypeSafe's Jev, or any LLM read through its answer-token probabilities (`deepseek:…`, `openrouter:…`). Sources: CSV, coding-agent traces (Claude Code, Cursor, OpenCode, OpenTelemetry), or a Python function.
|
|
82
|
+
|
|
83
|
+
## Docs
|
|
84
|
+
|
|
85
|
+
- [Introduction and quickstart](https://fuguai.mintlify.site)
|
|
86
|
+
- [Cookbooks](https://fuguai.mintlify.site/cookbooks): real problems with their measured results, including what did not work
|
|
87
|
+
- [Spec reference](https://fuguai.mintlify.site/reference/spec)
|
|
88
|
+
- [Design notes](docs/README.md), for working on hunch
|
|
89
|
+
|
|
90
|
+
## Status
|
|
91
|
+
|
|
92
|
+
v0.1. hunch has run on public datasets, real coding-agent sessions and a 100,000-row test, but no one outside the project has used it yet. Expect the spec format to change before 1.0.
|
|
93
|
+
|
|
94
|
+
## License
|
|
95
|
+
|
|
96
|
+
[Apache 2.0](LICENSE), except [`server/`](server/), which is under the [Elastic License 2.0](server/LICENSE). Third-party data used by the examples is listed in [NOTICE](NOTICE).
|
hunch_ai-0.1.0/README.md
ADDED
|
@@ -0,0 +1,70 @@
|
|
|
1
|
+
# hunch
|
|
2
|
+
|
|
3
|
+
Your code asks a model small questions all day. Which team should get this ticket? Did the agent's fix work? Is this shell command safe to run? hunch writes each question down as a spec, a short YAML file in git, and tells you how often the answers are right.
|
|
4
|
+
|
|
5
|
+
- `hunch run` asks the question of every row and stores each answer under its exact input, so a re-run costs nothing.
|
|
6
|
+
- `hunch test` measures accuracy against gold, an answer key or your own reviews, as a range, not a single number.
|
|
7
|
+
- `hunch diff` shows which rows a change to the question would flip, before you ship it.
|
|
8
|
+
- `hunch review` shows you the rows worth reading, and your verdicts become gold.
|
|
9
|
+
|
|
10
|
+
If you know dbt, the idea will feel familiar: dbt did this for SQL; hunch does it for model judgments.
|
|
11
|
+
|
|
12
|
+
## Install
|
|
13
|
+
|
|
14
|
+
```sh
|
|
15
|
+
uv tool install hunch-ai # or: pip install hunch-ai
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
The package is `hunch-ai`; the command and the import are `hunch`. Python 3.12 or later.
|
|
19
|
+
|
|
20
|
+
## Try it
|
|
21
|
+
|
|
22
|
+
```sh
|
|
23
|
+
export TYPESAFE_API_KEY=... # the recipe's engine is TypeSafe's Jev
|
|
24
|
+
hunch init tickets my-tickets # a spec, 40 sample tickets and a README
|
|
25
|
+
cd my-tickets
|
|
26
|
+
hunch compile . # the exact request and its cost; nothing is sent
|
|
27
|
+
hunch run . --max-cost 0.01 # about $0.001
|
|
28
|
+
hunch test .
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
A spec looks like this:
|
|
32
|
+
|
|
33
|
+
```yaml
|
|
34
|
+
judgment: ticket_triage
|
|
35
|
+
model: jev-1.13.0
|
|
36
|
+
source: tickets.csv
|
|
37
|
+
key: id
|
|
38
|
+
state: [subject, body] # the columns the model sees
|
|
39
|
+
|
|
40
|
+
questions:
|
|
41
|
+
department:
|
|
42
|
+
type: choice
|
|
43
|
+
instructions: Which team should handle this support ticket?
|
|
44
|
+
criteria:
|
|
45
|
+
billing: Problems with money already charged or owed
|
|
46
|
+
technical: Something is broken, slow, or misbehaving
|
|
47
|
+
sales: Buying more or buying differently
|
|
48
|
+
act: 0.80 # below this confidence, a person reviews it
|
|
49
|
+
gold: gold_department # the answer key, if you have one
|
|
50
|
+
|
|
51
|
+
tests:
|
|
52
|
+
department: {min_accuracy: 0.90}
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
Engines: TypeSafe's Jev, or any LLM read through its answer-token probabilities (`deepseek:…`, `openrouter:…`). Sources: CSV, coding-agent traces (Claude Code, Cursor, OpenCode, OpenTelemetry), or a Python function.
|
|
56
|
+
|
|
57
|
+
## Docs
|
|
58
|
+
|
|
59
|
+
- [Introduction and quickstart](https://fuguai.mintlify.site)
|
|
60
|
+
- [Cookbooks](https://fuguai.mintlify.site/cookbooks): real problems with their measured results, including what did not work
|
|
61
|
+
- [Spec reference](https://fuguai.mintlify.site/reference/spec)
|
|
62
|
+
- [Design notes](docs/README.md), for working on hunch
|
|
63
|
+
|
|
64
|
+
## Status
|
|
65
|
+
|
|
66
|
+
v0.1. hunch has run on public datasets, real coding-agent sessions and a 100,000-row test, but no one outside the project has used it yet. Expect the spec format to change before 1.0.
|
|
67
|
+
|
|
68
|
+
## License
|
|
69
|
+
|
|
70
|
+
[Apache 2.0](LICENSE), except [`server/`](server/), which is under the [Elastic License 2.0](server/LICENSE). Third-party data used by the examples is listed in [NOTICE](NOTICE).
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
[project]
|
|
2
|
+
name = "hunch-ai" # the PyPI name `hunch` is a placeholder someone else holds; import and command stay `hunch`
|
|
3
|
+
dynamic = ["version"] # from src/hunch/__init__.py, so the package and the release tag can't disagree
|
|
4
|
+
description = "Write the questions your code asks a model as specs, then test, diff and review the answers like code"
|
|
5
|
+
readme = "README.md"
|
|
6
|
+
license = "Apache-2.0"
|
|
7
|
+
license-files = ["LICENSE", "NOTICE"]
|
|
8
|
+
requires-python = ">=3.12"
|
|
9
|
+
dependencies = ["httpx>=0.27", "pyyaml>=6"]
|
|
10
|
+
keywords = ["llm", "evals", "classification", "judgments", "agents", "testing", "calibration"]
|
|
11
|
+
classifiers = [
|
|
12
|
+
"Development Status :: 3 - Alpha",
|
|
13
|
+
"Intended Audience :: Developers",
|
|
14
|
+
"Programming Language :: Python :: 3",
|
|
15
|
+
"Programming Language :: Python :: 3.12",
|
|
16
|
+
"Programming Language :: Python :: 3.13",
|
|
17
|
+
"Programming Language :: Python :: 3.14",
|
|
18
|
+
"Topic :: Scientific/Engineering :: Artificial Intelligence",
|
|
19
|
+
"Topic :: Software Development :: Testing",
|
|
20
|
+
]
|
|
21
|
+
|
|
22
|
+
[project.urls]
|
|
23
|
+
Documentation = "https://fuguai.mintlify.site"
|
|
24
|
+
Source = "https://github.com/oneryalcin/hunch"
|
|
25
|
+
Issues = "https://github.com/oneryalcin/hunch/issues"
|
|
26
|
+
|
|
27
|
+
[project.optional-dependencies]
|
|
28
|
+
pydantic = ["pydantic>=2"]
|
|
29
|
+
|
|
30
|
+
[project.scripts]
|
|
31
|
+
hunch = "hunch.cli:main"
|
|
32
|
+
|
|
33
|
+
[build-system]
|
|
34
|
+
requires = ["hatchling"]
|
|
35
|
+
build-backend = "hatchling.build"
|
|
36
|
+
|
|
37
|
+
[tool.hatch.version]
|
|
38
|
+
path = "src/hunch/__init__.py"
|
|
39
|
+
|
|
40
|
+
[tool.hatch.build.targets.wheel]
|
|
41
|
+
packages = ["src/hunch"]
|
|
42
|
+
|
|
43
|
+
[tool.hatch.build.targets.sdist] # the library only: not the prototype, docs site, server or anything local
|
|
44
|
+
include = ["/src/hunch", "/README.md", "/LICENSE", "/NOTICE", "/pyproject.toml"]
|
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
"""hunch: judgments as code. Write a question once, test it against gold, diff every change, review what matters,
|
|
2
|
+
and choose how much to automate by looking at the dial.
|
|
3
|
+
|
|
4
|
+
Library first; the `hunch` CLI is a thin shell over the same functions.
|
|
5
|
+
|
|
6
|
+
import hunch
|
|
7
|
+
hunch.judge("triage.yml", subject="Charged twice", body="...") # online, cached, same keys as batch
|
|
8
|
+
results = hunch.run("triage.yml") # batch: every judgment, in order
|
|
9
|
+
rows = hunch.results("triage.yml") # the materialized table, as dicts
|
|
10
|
+
|
|
11
|
+
# Pydantic classes as specs (the same mapping as Pydantic AI's TypeSafe model)
|
|
12
|
+
spec = hunch.spec_from_model(Triage, source="tickets.csv", state=["subject", "body"])
|
|
13
|
+
ticket = hunch.judge_model(Triage, spec, subject="...", body="...") # a Triage instance
|
|
14
|
+
"""
|
|
15
|
+
from pathlib import Path
|
|
16
|
+
|
|
17
|
+
from hunch.core import ( # noqa: F401 (the public surface)
|
|
18
|
+
ajudge, decide, execute, judge, lint, load_project, load_spec, spec_yaml, table_name,
|
|
19
|
+
)
|
|
20
|
+
from hunch.models import spec_from_model, to_model # noqa: F401
|
|
21
|
+
|
|
22
|
+
__version__ = "0.1.0"
|
|
23
|
+
|
|
24
|
+
|
|
25
|
+
def load(obj, base: str | Path = ".") -> dict:
|
|
26
|
+
"""A project from a spec path, a folder of specs, a spec dict (e.g. from spec_from_model) or a list of spec
|
|
27
|
+
dicts (a graph built in Python: generate the specs, don't copy them). Relative sources resolve against base."""
|
|
28
|
+
from hunch.core import expand_multi, topo_project
|
|
29
|
+
if isinstance(obj, (dict, list)):
|
|
30
|
+
specs = []
|
|
31
|
+
for s in obj if isinstance(obj, list) else [obj]:
|
|
32
|
+
spec = {**s, "_dir": Path(base).resolve()}
|
|
33
|
+
expand_multi(spec)
|
|
34
|
+
specs.append(spec)
|
|
35
|
+
return topo_project(specs)
|
|
36
|
+
return load_project(Path(obj))
|
|
37
|
+
|
|
38
|
+
|
|
39
|
+
def run(obj, base: str | Path = ".") -> dict:
|
|
40
|
+
"""Run every judgment (asks only what the store lacks) and materialize its table; returns the results."""
|
|
41
|
+
import argparse
|
|
42
|
+
from hunch.core import cmd_run
|
|
43
|
+
project = load(obj, base)
|
|
44
|
+
cmd_run(project, argparse.Namespace())
|
|
45
|
+
return project
|
|
46
|
+
|
|
47
|
+
|
|
48
|
+
def results(obj, base: str | Path = ".", judgment: str | None = None) -> list[dict]:
|
|
49
|
+
"""The materialized table of a judgment (the last complete run), as a list of dicts."""
|
|
50
|
+
from hunch.core import open_store
|
|
51
|
+
project = load(obj, base)
|
|
52
|
+
spec = project["nodes"][judgment or project["order"][-1]]
|
|
53
|
+
db = open_store(spec)
|
|
54
|
+
cur = db.execute(f'select * from "{table_name(spec)}"')
|
|
55
|
+
cols = [c[0] for c in cur.description]
|
|
56
|
+
return [dict(zip(cols, r)) for r in cur.fetchall()]
|
|
57
|
+
|
|
58
|
+
|
|
59
|
+
def judge_model(cls, spec: dict, base: str | Path = ".", **fields):
|
|
60
|
+
"""Judge one row with a spec built from a Pydantic class; returns an instance of that class."""
|
|
61
|
+
import asyncio
|
|
62
|
+
from hunch.core import aexecute
|
|
63
|
+
project = load(spec, base)
|
|
64
|
+
res = asyncio.run(aexecute(project, rows_in=[fields]))[project["order"][0]]
|
|
65
|
+
answers = {it["qid"]: {"label": decide(res["answers"][it["key"]])[0]} for it in res["items"]}
|
|
66
|
+
return to_model(cls, answers) # a bare output type (Literal, bool, ...) returns the value itself
|