attune-harness 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.
- attune_harness-0.1.0/LICENSE +201 -0
- attune_harness-0.1.0/MANIFEST.in +4 -0
- attune_harness-0.1.0/PKG-INFO +191 -0
- attune_harness-0.1.0/README.md +145 -0
- attune_harness-0.1.0/pyproject.toml +53 -0
- attune_harness-0.1.0/setup.cfg +4 -0
- attune_harness-0.1.0/src/attune_harness/__init__.py +118 -0
- attune_harness-0.1.0/src/attune_harness/__main__.py +32 -0
- attune_harness-0.1.0/src/attune_harness/_pytest_worker.py +97 -0
- attune_harness-0.1.0/src/attune_harness/_windows_worker.py +25 -0
- attune_harness-0.1.0/src/attune_harness/a2a.py +275 -0
- attune_harness-0.1.0/src/attune_harness/adapters.py +113 -0
- attune_harness-0.1.0/src/attune_harness/assessment_effects.py +158 -0
- attune_harness-0.1.0/src/attune_harness/attune_bridge.py +129 -0
- attune_harness-0.1.0/src/attune_harness/cli.py +188 -0
- attune_harness-0.1.0/src/attune_harness/cli_help.py +51 -0
- attune_harness-0.1.0/src/attune_harness/documentation.py +235 -0
- attune_harness-0.1.0/src/attune_harness/execution_evidence.py +312 -0
- attune_harness-0.1.0/src/attune_harness/extension_cli.py +42 -0
- attune_harness-0.1.0/src/attune_harness/extensions.py +207 -0
- attune_harness-0.1.0/src/attune_harness/features.py +75 -0
- attune_harness-0.1.0/src/attune_harness/github_checks.py +44 -0
- attune_harness-0.1.0/src/attune_harness/grounded_review.py +130 -0
- attune_harness-0.1.0/src/attune_harness/llama_tokens.py +98 -0
- attune_harness-0.1.0/src/attune_harness/mcp_server.py +213 -0
- attune_harness-0.1.0/src/attune_harness/memory_bridge.py +116 -0
- attune_harness-0.1.0/src/attune_harness/memory_cli.py +104 -0
- attune_harness-0.1.0/src/attune_harness/memory_context.py +203 -0
- attune_harness-0.1.0/src/attune_harness/memory_contract.py +219 -0
- attune_harness-0.1.0/src/attune_harness/memory_native.py +563 -0
- attune_harness-0.1.0/src/attune_harness/memory_worker.py +324 -0
- attune_harness-0.1.0/src/attune_harness/native.py +218 -0
- attune_harness-0.1.0/src/attune_harness/ollama.py +180 -0
- attune_harness-0.1.0/src/attune_harness/ollama_review.py +159 -0
- attune_harness-0.1.0/src/attune_harness/operations.py +162 -0
- attune_harness-0.1.0/src/attune_harness/passage_review.py +120 -0
- attune_harness-0.1.0/src/attune_harness/process.py +127 -0
- attune_harness-0.1.0/src/attune_harness/recovery.py +407 -0
- attune_harness-0.1.0/src/attune_harness/repair.py +313 -0
- attune_harness-0.1.0/src/attune_harness/retrieval.py +73 -0
- attune_harness-0.1.0/src/attune_harness/retrieval_task.py +55 -0
- attune_harness-0.1.0/src/attune_harness/review.py +84 -0
- attune_harness-0.1.0/src/attune_harness/review_cli.py +92 -0
- attune_harness-0.1.0/src/attune_harness/review_contract.py +166 -0
- attune_harness-0.1.0/src/attune_harness/review_participants.py +195 -0
- attune_harness-0.1.0/src/attune_harness/review_store.py +134 -0
- attune_harness-0.1.0/src/attune_harness/spec_bridge.py +404 -0
- attune_harness-0.1.0/src/attune_harness/spec_handoff.py +90 -0
- attune_harness-0.1.0/src/attune_harness/task_cli.py +257 -0
- attune_harness-0.1.0/src/attune_harness/task_contract.py +539 -0
- attune_harness-0.1.0/src/attune_harness/task_handoff.py +533 -0
- attune_harness-0.1.0/src/attune_harness/task_policies.py +339 -0
- attune_harness-0.1.0/src/attune_harness/task_runtime.py +223 -0
- attune_harness-0.1.0/src/attune_harness/test_change.py +564 -0
- attune_harness-0.1.0/src/attune_harness/test_cli.py +135 -0
- attune_harness-0.1.0/src/attune_harness/test_execution.py +244 -0
- attune_harness-0.1.0/src/attune_harness/test_scope.py +297 -0
- attune_harness-0.1.0/src/attune_harness/verification.py +53 -0
- attune_harness-0.1.0/src/attune_harness/voyage_cli.py +60 -0
- attune_harness-0.1.0/src/attune_harness/voyage_index.py +232 -0
- attune_harness-0.1.0/src/attune_harness/voyage_provider.py +239 -0
- attune_harness-0.1.0/src/attune_harness/voyage_retrieval.py +177 -0
- attune_harness-0.1.0/src/attune_harness/voyage_sources.py +296 -0
- attune_harness-0.1.0/src/attune_harness/windows.py +113 -0
- attune_harness-0.1.0/src/attune_harness/work_bodies.py +164 -0
- attune_harness-0.1.0/src/attune_harness/work_build.py +744 -0
- attune_harness-0.1.0/src/attune_harness/work_cli.py +712 -0
- attune_harness-0.1.0/src/attune_harness/work_contract.py +835 -0
- attune_harness-0.1.0/src/attune_harness/work_decisions.py +140 -0
- attune_harness-0.1.0/src/attune_harness/work_effects.py +647 -0
- attune_harness-0.1.0/src/attune_harness/work_review_handoff.py +343 -0
- attune_harness-0.1.0/src/attune_harness/work_runtime.py +1079 -0
- attune_harness-0.1.0/src/attune_harness.egg-info/PKG-INFO +191 -0
- attune_harness-0.1.0/src/attune_harness.egg-info/SOURCES.txt +76 -0
- attune_harness-0.1.0/src/attune_harness.egg-info/dependency_links.txt +1 -0
- attune_harness-0.1.0/src/attune_harness.egg-info/entry_points.txt +2 -0
- attune_harness-0.1.0/src/attune_harness.egg-info/requires.txt +30 -0
- attune_harness-0.1.0/src/attune_harness.egg-info/top_level.txt +1 -0
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2025 Deep Study AI, LLC
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1,191 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: attune-harness
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: Portable execution contracts for multi-model agent work
|
|
5
|
+
Author-email: Patrick Roebuck <admin@smartaimemory.com>
|
|
6
|
+
Maintainer-email: Smart-AI-Memory <admin@smartaimemory.com>
|
|
7
|
+
License-Expression: Apache-2.0
|
|
8
|
+
Project-URL: Homepage, https://github.com/Smart-AI-Memory/attune-harness
|
|
9
|
+
Project-URL: Repository, https://github.com/Smart-AI-Memory/attune-harness
|
|
10
|
+
Project-URL: Issues, https://github.com/Smart-AI-Memory/attune-harness/issues
|
|
11
|
+
Keywords: ai-agent,multi-agent,agent-harness,llm,mcp,developer-tools,cli
|
|
12
|
+
Classifier: Development Status :: 3 - Alpha
|
|
13
|
+
Classifier: Intended Audience :: Developers
|
|
14
|
+
Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
|
|
15
|
+
Classifier: Programming Language :: Python :: 3
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
18
|
+
Classifier: Environment :: Console
|
|
19
|
+
Requires-Python: >=3.10
|
|
20
|
+
Description-Content-Type: text/markdown
|
|
21
|
+
License-File: LICENSE
|
|
22
|
+
Provides-Extra: tokens
|
|
23
|
+
Requires-Dist: tiktoken==0.12.0; extra == "tokens"
|
|
24
|
+
Provides-Extra: verify
|
|
25
|
+
Requires-Dist: attune-verify==0.6.0; extra == "verify"
|
|
26
|
+
Provides-Extra: rag
|
|
27
|
+
Requires-Dist: attune-rag==1.2.0; extra == "rag"
|
|
28
|
+
Provides-Extra: voyage
|
|
29
|
+
Requires-Dist: voyageai==0.5.0; extra == "voyage"
|
|
30
|
+
Requires-Dist: lancedb==0.38.0; extra == "voyage"
|
|
31
|
+
Requires-Dist: pyarrow==25.0.1; extra == "voyage"
|
|
32
|
+
Requires-Dist: jsonschema==4.26.0; extra == "voyage"
|
|
33
|
+
Provides-Extra: review
|
|
34
|
+
Requires-Dist: attune-forms==0.17.0; extra == "review"
|
|
35
|
+
Requires-Dist: attune-verify==0.6.0; extra == "review"
|
|
36
|
+
Requires-Dist: attune-rag==1.2.0; extra == "review"
|
|
37
|
+
Provides-Extra: mcp
|
|
38
|
+
Requires-Dist: mcp==2.2.0; extra == "mcp"
|
|
39
|
+
Requires-Dist: attune-forms==0.17.0; extra == "mcp"
|
|
40
|
+
Requires-Dist: attune-verify==0.6.0; extra == "mcp"
|
|
41
|
+
Requires-Dist: attune-rag==1.2.0; extra == "mcp"
|
|
42
|
+
Provides-Extra: memory-native
|
|
43
|
+
Requires-Dist: anthropic==1.6.0; extra == "memory-native"
|
|
44
|
+
Requires-Dist: httpx2==2.13.0; extra == "memory-native"
|
|
45
|
+
Dynamic: license-file
|
|
46
|
+
|
|
47
|
+
# Attune Harness
|
|
48
|
+
|
|
49
|
+
**Run an agent's work, check it independently, and keep a receipt of which happened.**
|
|
50
|
+
|
|
51
|
+
> **Status: 0.1.0, alpha.** Interfaces, configuration formats and CLI commands may
|
|
52
|
+
> change before 1.0. What is and is not qualified is
|
|
53
|
+
> [listed below](#what-is-qualified-and-what-is-not), not implied.
|
|
54
|
+
|
|
55
|
+
On September 18, 2026 I ran twelve model-written implementations of a small JSONL
|
|
56
|
+
exporter through Harness. Nine behaved correctly under the full check. The other three passed when their serializer
|
|
57
|
+
was tested directly, and failed when run through the real command line, which is the
|
|
58
|
+
only way anyone would ever use them
|
|
59
|
+
([results](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/plan-build-native-results.md)).
|
|
60
|
+
|
|
61
|
+
That gap is what Harness is for. A participant produces output: a model, a command,
|
|
62
|
+
or your own code. A check you supply, separate from the participant, decides whether
|
|
63
|
+
the output counts. You get back a receipt that says which. The participant's account
|
|
64
|
+
of its own work is recorded. It is never the evidence.
|
|
65
|
+
|
|
66
|
+
## A wrong answer comes back rejected
|
|
67
|
+
|
|
68
|
+
```sh
|
|
69
|
+
pip install attune-harness
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
The core has no dependencies and needs Python 3.10 or later. No provider SDK, no
|
|
73
|
+
API key, and no attune-ai installation.
|
|
74
|
+
|
|
75
|
+
```python
|
|
76
|
+
from attune_harness import Check, Output, Task, run
|
|
77
|
+
|
|
78
|
+
class Worker:
|
|
79
|
+
def run(self, task: Task) -> Output:
|
|
80
|
+
return Output("4")
|
|
81
|
+
|
|
82
|
+
receipt = run(
|
|
83
|
+
Task("addition", "Compute 2 + 2", ("Return the integer result",)),
|
|
84
|
+
"example-worker",
|
|
85
|
+
Worker(),
|
|
86
|
+
lambda task, output: Check(output.text == "4", "Compared with independent arithmetic"),
|
|
87
|
+
)
|
|
88
|
+
print(receipt.status.value) # verified
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
Change the worker to return `"5"` and the same call returns `rejected`, with the
|
|
92
|
+
output and the check's evidence still attached. If the participant or the check
|
|
93
|
+
raises, the status is `failed` and the receipt names the stage and the error. `run`
|
|
94
|
+
executes once. It never retries on its own.
|
|
95
|
+
|
|
96
|
+
`python -m attune_harness` runs the installed demonstration and prints a JSON receipt.
|
|
97
|
+
|
|
98
|
+
## The CLI applies the same contract to larger work
|
|
99
|
+
|
|
100
|
+
```text
|
|
101
|
+
attune-harness --help
|
|
102
|
+
|
|
103
|
+
Task execution
|
|
104
|
+
plan Define intent and accept its scope
|
|
105
|
+
build Execute accepted tasks and protected checks
|
|
106
|
+
review Assess a document against project evidence
|
|
107
|
+
fix Repair scoped files and check the result
|
|
108
|
+
test Test a captured change and retain the evidence
|
|
109
|
+
|
|
110
|
+
Task controls
|
|
111
|
+
status Inspect a saved task
|
|
112
|
+
resume Continue a saved task
|
|
113
|
+
|
|
114
|
+
AI tools and integration
|
|
115
|
+
--help-all Browse operational tools and compatibility commands
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
Every verb follows one pattern. You accept a scope before anything runs, the host
|
|
119
|
+
applies the effects, and checks fixed in advance decide the outcome. `fix` is the
|
|
120
|
+
clearest example: it freezes an acceptance probe before the worker starts, applies
|
|
121
|
+
the worker's proposed replacement itself, and keeps the failed-before and
|
|
122
|
+
passed-after probe evidence. A saved task can be inspected with `status` and
|
|
123
|
+
continued with `resume`; completed operations replay from saved evidence instead of
|
|
124
|
+
running again.
|
|
125
|
+
|
|
126
|
+
Reaching outside the process takes explicit permission. External command
|
|
127
|
+
participants need `--allow-external`, and native model participants also need
|
|
128
|
+
`--allow-native`. **Approving a plan does not authorize paid calls.**
|
|
129
|
+
|
|
130
|
+
Many of these commands are there for the agent and its integrations to call.
|
|
131
|
+
Learning their syntax is not the price of entry, and `attune-harness COMMAND --help`
|
|
132
|
+
covers direct use. Full usage, exit codes and recovery controls are in the
|
|
133
|
+
[CLI guide](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/cli-guide.md).
|
|
134
|
+
|
|
135
|
+
## Install only what you use
|
|
136
|
+
|
|
137
|
+
| You want | Install |
|
|
138
|
+
| --- | --- |
|
|
139
|
+
| The core contracts and CLI, with no dependencies | `pip install attune-harness` |
|
|
140
|
+
| Document claim verification (`attune-verify` 0.6.0) | `pip install 'attune-harness[verify]'` |
|
|
141
|
+
| Local Markdown retrieval with source hashes, no model calls (`attune-rag` 1.2.0) | `pip install 'attune-harness[rag]'` |
|
|
142
|
+
| The evidence-review and test journeys: forms, retrieval and verification together | `pip install 'attune-harness[review]'` |
|
|
143
|
+
| Accepted retrieval grants served over MCP stdio (`mcp` 2.2.0) | `pip install 'attune-harness[mcp]'` |
|
|
144
|
+
| Repository-first retrieval on Voyage embeddings | `pip install 'attune-harness[voyage]'` |
|
|
145
|
+
| Token counting (`tiktoken` 0.12.0) | `pip install 'attune-harness[tokens]'` |
|
|
146
|
+
| Experimental: memory proposals from a Claude model over a pinned, data-only Anthropic API transport (`anthropic` 1.6.0, `httpx2` 2.13.0). POSIX only, needs `ANTHROPIC_API_KEY`, makes paid calls | `pip install 'attune-harness[memory-native]'` |
|
|
147
|
+
|
|
148
|
+
Extras pin exact versions as of 0.1.0. Keep the quotes: zsh and bash treat square
|
|
149
|
+
brackets as glob characters. When an extra is missing, the command that needs it
|
|
150
|
+
returns an actionable unavailable report instead of a traceback.
|
|
151
|
+
|
|
152
|
+
## What is qualified and what is not
|
|
153
|
+
|
|
154
|
+
I would rather you find the limits here than in your own checkout. Green software
|
|
155
|
+
tests and model quality are different claims, and this project keeps them apart.
|
|
156
|
+
|
|
157
|
+
| Area | Qualified | Not qualified |
|
|
158
|
+
| --- | --- | --- |
|
|
159
|
+
| Platforms | CI builds and installs the wheel on macOS, Ubuntu and Windows with Python 3.10 and 3.12, and exercises timeouts, cancellation, bounded output, crash-released locks and recovery ([guide](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/qualification.md)) | Other Python versions are outside the matrix. On Windows, a process that holds a run's `record.json` open for more than about two seconds still fails that run closed |
|
|
160
|
+
| Models | CI calls no model provider. Native Claude and Codex adapters have recorded comparisons | Native planning and building are experimental. In the September 18, 2026 comparison the original reply contract accepted 1 of 24 replies; after the contract was corrected it accepted 12 of 12. Two repetitions per role do not establish a reliability rate |
|
|
161
|
+
| `fix` and `test` | Local POSIX Git checkouts, regular files, default pytest discovery | Windows repair effects, file creation, deletion and renames, linked worktrees, custom pytest collectors, committed revision ranges |
|
|
162
|
+
| Isolation | Commands and probes run as supervised processes with deadlines and bounded output | **This is not a security sandbox.** Use a dedicated checkout and commands you trust |
|
|
163
|
+
| Receipts | Receipts retain the task, output and check evidence locally | They are local values, not signed attestations. Constructing a `Receipt` directly certifies nothing |
|
|
164
|
+
| Plan acceptance | Core imports, help and the library run standalone | `plan --accept` needs the optional Attune AI Spec runtime in the same environment |
|
|
165
|
+
| Protocols | MCP (2025-11-25 and 2026-07-28 profiles) and A2A 1.0 have local independent-client receipts | Remote authentication, arbitrary executable plugins and automatic host installation |
|
|
166
|
+
| Memory | A read-only integration plan is accepted and qualified in a temporary install | The memory modules and the `memory-native` extra ship in the wheel but are experimental and not activated for live memories. The native transport is POSIX only, accepts two exact model IDs, refuses any other SDK version, and is never exercised in CI |
|
|
167
|
+
| Roadmap | | `ship` and `reflect` are planned routes and do not exist yet |
|
|
168
|
+
|
|
169
|
+
## Harness and attune-ai
|
|
170
|
+
|
|
171
|
+
Harness is the successor I am building to
|
|
172
|
+
[attune-ai](https://pypi.org/project/attune-ai/). It starts from a constraint
|
|
173
|
+
attune-ai never had: the core must run with no provider SDK and nothing else from
|
|
174
|
+
the Attune family installed. The Attune libraries come in as extras, where you can
|
|
175
|
+
see exactly what each one adds.
|
|
176
|
+
|
|
177
|
+
attune-ai is still where cross-session memory, the Claude Code plugin and the
|
|
178
|
+
multi-agent workflows live. Harness does not replace those today. If that is what
|
|
179
|
+
you need, install attune-ai.
|
|
180
|
+
|
|
181
|
+
## Links
|
|
182
|
+
|
|
183
|
+
- [Qualification guide](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/qualification.md)
|
|
184
|
+
- [CLI guide](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/cli-guide.md)
|
|
185
|
+
- [Portable contract](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/portable-contract.md)
|
|
186
|
+
- [Repository](https://github.com/Smart-AI-Memory/attune-harness) and
|
|
187
|
+
[issues](https://github.com/Smart-AI-Memory/attune-harness/issues)
|
|
188
|
+
|
|
189
|
+
**Apache License 2.0.**
|
|
190
|
+
|
|
191
|
+
Built by Patrick Roebuck, working with Codex and Claude.
|
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
# Attune Harness
|
|
2
|
+
|
|
3
|
+
**Run an agent's work, check it independently, and keep a receipt of which happened.**
|
|
4
|
+
|
|
5
|
+
> **Status: 0.1.0, alpha.** Interfaces, configuration formats and CLI commands may
|
|
6
|
+
> change before 1.0. What is and is not qualified is
|
|
7
|
+
> [listed below](#what-is-qualified-and-what-is-not), not implied.
|
|
8
|
+
|
|
9
|
+
On September 18, 2026 I ran twelve model-written implementations of a small JSONL
|
|
10
|
+
exporter through Harness. Nine behaved correctly under the full check. The other three passed when their serializer
|
|
11
|
+
was tested directly, and failed when run through the real command line, which is the
|
|
12
|
+
only way anyone would ever use them
|
|
13
|
+
([results](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/plan-build-native-results.md)).
|
|
14
|
+
|
|
15
|
+
That gap is what Harness is for. A participant produces output: a model, a command,
|
|
16
|
+
or your own code. A check you supply, separate from the participant, decides whether
|
|
17
|
+
the output counts. You get back a receipt that says which. The participant's account
|
|
18
|
+
of its own work is recorded. It is never the evidence.
|
|
19
|
+
|
|
20
|
+
## A wrong answer comes back rejected
|
|
21
|
+
|
|
22
|
+
```sh
|
|
23
|
+
pip install attune-harness
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
The core has no dependencies and needs Python 3.10 or later. No provider SDK, no
|
|
27
|
+
API key, and no attune-ai installation.
|
|
28
|
+
|
|
29
|
+
```python
|
|
30
|
+
from attune_harness import Check, Output, Task, run
|
|
31
|
+
|
|
32
|
+
class Worker:
|
|
33
|
+
def run(self, task: Task) -> Output:
|
|
34
|
+
return Output("4")
|
|
35
|
+
|
|
36
|
+
receipt = run(
|
|
37
|
+
Task("addition", "Compute 2 + 2", ("Return the integer result",)),
|
|
38
|
+
"example-worker",
|
|
39
|
+
Worker(),
|
|
40
|
+
lambda task, output: Check(output.text == "4", "Compared with independent arithmetic"),
|
|
41
|
+
)
|
|
42
|
+
print(receipt.status.value) # verified
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
Change the worker to return `"5"` and the same call returns `rejected`, with the
|
|
46
|
+
output and the check's evidence still attached. If the participant or the check
|
|
47
|
+
raises, the status is `failed` and the receipt names the stage and the error. `run`
|
|
48
|
+
executes once. It never retries on its own.
|
|
49
|
+
|
|
50
|
+
`python -m attune_harness` runs the installed demonstration and prints a JSON receipt.
|
|
51
|
+
|
|
52
|
+
## The CLI applies the same contract to larger work
|
|
53
|
+
|
|
54
|
+
```text
|
|
55
|
+
attune-harness --help
|
|
56
|
+
|
|
57
|
+
Task execution
|
|
58
|
+
plan Define intent and accept its scope
|
|
59
|
+
build Execute accepted tasks and protected checks
|
|
60
|
+
review Assess a document against project evidence
|
|
61
|
+
fix Repair scoped files and check the result
|
|
62
|
+
test Test a captured change and retain the evidence
|
|
63
|
+
|
|
64
|
+
Task controls
|
|
65
|
+
status Inspect a saved task
|
|
66
|
+
resume Continue a saved task
|
|
67
|
+
|
|
68
|
+
AI tools and integration
|
|
69
|
+
--help-all Browse operational tools and compatibility commands
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
Every verb follows one pattern. You accept a scope before anything runs, the host
|
|
73
|
+
applies the effects, and checks fixed in advance decide the outcome. `fix` is the
|
|
74
|
+
clearest example: it freezes an acceptance probe before the worker starts, applies
|
|
75
|
+
the worker's proposed replacement itself, and keeps the failed-before and
|
|
76
|
+
passed-after probe evidence. A saved task can be inspected with `status` and
|
|
77
|
+
continued with `resume`; completed operations replay from saved evidence instead of
|
|
78
|
+
running again.
|
|
79
|
+
|
|
80
|
+
Reaching outside the process takes explicit permission. External command
|
|
81
|
+
participants need `--allow-external`, and native model participants also need
|
|
82
|
+
`--allow-native`. **Approving a plan does not authorize paid calls.**
|
|
83
|
+
|
|
84
|
+
Many of these commands are there for the agent and its integrations to call.
|
|
85
|
+
Learning their syntax is not the price of entry, and `attune-harness COMMAND --help`
|
|
86
|
+
covers direct use. Full usage, exit codes and recovery controls are in the
|
|
87
|
+
[CLI guide](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/cli-guide.md).
|
|
88
|
+
|
|
89
|
+
## Install only what you use
|
|
90
|
+
|
|
91
|
+
| You want | Install |
|
|
92
|
+
| --- | --- |
|
|
93
|
+
| The core contracts and CLI, with no dependencies | `pip install attune-harness` |
|
|
94
|
+
| Document claim verification (`attune-verify` 0.6.0) | `pip install 'attune-harness[verify]'` |
|
|
95
|
+
| Local Markdown retrieval with source hashes, no model calls (`attune-rag` 1.2.0) | `pip install 'attune-harness[rag]'` |
|
|
96
|
+
| The evidence-review and test journeys: forms, retrieval and verification together | `pip install 'attune-harness[review]'` |
|
|
97
|
+
| Accepted retrieval grants served over MCP stdio (`mcp` 2.2.0) | `pip install 'attune-harness[mcp]'` |
|
|
98
|
+
| Repository-first retrieval on Voyage embeddings | `pip install 'attune-harness[voyage]'` |
|
|
99
|
+
| Token counting (`tiktoken` 0.12.0) | `pip install 'attune-harness[tokens]'` |
|
|
100
|
+
| Experimental: memory proposals from a Claude model over a pinned, data-only Anthropic API transport (`anthropic` 1.6.0, `httpx2` 2.13.0). POSIX only, needs `ANTHROPIC_API_KEY`, makes paid calls | `pip install 'attune-harness[memory-native]'` |
|
|
101
|
+
|
|
102
|
+
Extras pin exact versions as of 0.1.0. Keep the quotes: zsh and bash treat square
|
|
103
|
+
brackets as glob characters. When an extra is missing, the command that needs it
|
|
104
|
+
returns an actionable unavailable report instead of a traceback.
|
|
105
|
+
|
|
106
|
+
## What is qualified and what is not
|
|
107
|
+
|
|
108
|
+
I would rather you find the limits here than in your own checkout. Green software
|
|
109
|
+
tests and model quality are different claims, and this project keeps them apart.
|
|
110
|
+
|
|
111
|
+
| Area | Qualified | Not qualified |
|
|
112
|
+
| --- | --- | --- |
|
|
113
|
+
| Platforms | CI builds and installs the wheel on macOS, Ubuntu and Windows with Python 3.10 and 3.12, and exercises timeouts, cancellation, bounded output, crash-released locks and recovery ([guide](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/qualification.md)) | Other Python versions are outside the matrix. On Windows, a process that holds a run's `record.json` open for more than about two seconds still fails that run closed |
|
|
114
|
+
| Models | CI calls no model provider. Native Claude and Codex adapters have recorded comparisons | Native planning and building are experimental. In the September 18, 2026 comparison the original reply contract accepted 1 of 24 replies; after the contract was corrected it accepted 12 of 12. Two repetitions per role do not establish a reliability rate |
|
|
115
|
+
| `fix` and `test` | Local POSIX Git checkouts, regular files, default pytest discovery | Windows repair effects, file creation, deletion and renames, linked worktrees, custom pytest collectors, committed revision ranges |
|
|
116
|
+
| Isolation | Commands and probes run as supervised processes with deadlines and bounded output | **This is not a security sandbox.** Use a dedicated checkout and commands you trust |
|
|
117
|
+
| Receipts | Receipts retain the task, output and check evidence locally | They are local values, not signed attestations. Constructing a `Receipt` directly certifies nothing |
|
|
118
|
+
| Plan acceptance | Core imports, help and the library run standalone | `plan --accept` needs the optional Attune AI Spec runtime in the same environment |
|
|
119
|
+
| Protocols | MCP (2025-11-25 and 2026-07-28 profiles) and A2A 1.0 have local independent-client receipts | Remote authentication, arbitrary executable plugins and automatic host installation |
|
|
120
|
+
| Memory | A read-only integration plan is accepted and qualified in a temporary install | The memory modules and the `memory-native` extra ship in the wheel but are experimental and not activated for live memories. The native transport is POSIX only, accepts two exact model IDs, refuses any other SDK version, and is never exercised in CI |
|
|
121
|
+
| Roadmap | | `ship` and `reflect` are planned routes and do not exist yet |
|
|
122
|
+
|
|
123
|
+
## Harness and attune-ai
|
|
124
|
+
|
|
125
|
+
Harness is the successor I am building to
|
|
126
|
+
[attune-ai](https://pypi.org/project/attune-ai/). It starts from a constraint
|
|
127
|
+
attune-ai never had: the core must run with no provider SDK and nothing else from
|
|
128
|
+
the Attune family installed. The Attune libraries come in as extras, where you can
|
|
129
|
+
see exactly what each one adds.
|
|
130
|
+
|
|
131
|
+
attune-ai is still where cross-session memory, the Claude Code plugin and the
|
|
132
|
+
multi-agent workflows live. Harness does not replace those today. If that is what
|
|
133
|
+
you need, install attune-ai.
|
|
134
|
+
|
|
135
|
+
## Links
|
|
136
|
+
|
|
137
|
+
- [Qualification guide](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/qualification.md)
|
|
138
|
+
- [CLI guide](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/cli-guide.md)
|
|
139
|
+
- [Portable contract](https://github.com/Smart-AI-Memory/attune-harness/blob/v0.1.0/docs/portable-contract.md)
|
|
140
|
+
- [Repository](https://github.com/Smart-AI-Memory/attune-harness) and
|
|
141
|
+
[issues](https://github.com/Smart-AI-Memory/attune-harness/issues)
|
|
142
|
+
|
|
143
|
+
**Apache License 2.0.**
|
|
144
|
+
|
|
145
|
+
Built by Patrick Roebuck, working with Codex and Claude.
|
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
[build-system]
|
|
2
|
+
requires = ["setuptools>=77"]
|
|
3
|
+
build-backend = "setuptools.build_meta"
|
|
4
|
+
|
|
5
|
+
[project]
|
|
6
|
+
name = "attune-harness"
|
|
7
|
+
version = "0.1.0"
|
|
8
|
+
description = "Portable execution contracts for multi-model agent work"
|
|
9
|
+
requires-python = ">=3.10"
|
|
10
|
+
readme = "README.md"
|
|
11
|
+
license = "Apache-2.0"
|
|
12
|
+
license-files = ["LICENSE"]
|
|
13
|
+
authors = [
|
|
14
|
+
{name = "Patrick Roebuck", email = "admin@smartaimemory.com"}
|
|
15
|
+
]
|
|
16
|
+
maintainers = [
|
|
17
|
+
{name = "Smart-AI-Memory", email = "admin@smartaimemory.com"}
|
|
18
|
+
]
|
|
19
|
+
keywords = ["ai-agent", "multi-agent", "agent-harness", "llm", "mcp", "developer-tools", "cli"]
|
|
20
|
+
classifiers = [
|
|
21
|
+
"Development Status :: 3 - Alpha",
|
|
22
|
+
"Intended Audience :: Developers",
|
|
23
|
+
"Topic :: Software Development :: Libraries :: Application Frameworks",
|
|
24
|
+
"Programming Language :: Python :: 3",
|
|
25
|
+
"Programming Language :: Python :: 3.10",
|
|
26
|
+
"Programming Language :: Python :: 3.12",
|
|
27
|
+
"Environment :: Console",
|
|
28
|
+
]
|
|
29
|
+
dependencies = []
|
|
30
|
+
|
|
31
|
+
[project.urls]
|
|
32
|
+
Homepage = "https://github.com/Smart-AI-Memory/attune-harness"
|
|
33
|
+
Repository = "https://github.com/Smart-AI-Memory/attune-harness"
|
|
34
|
+
Issues = "https://github.com/Smart-AI-Memory/attune-harness/issues"
|
|
35
|
+
|
|
36
|
+
[project.optional-dependencies]
|
|
37
|
+
tokens = ["tiktoken==0.12.0"]
|
|
38
|
+
verify = ["attune-verify==0.6.0"]
|
|
39
|
+
rag = ["attune-rag==1.2.0"]
|
|
40
|
+
voyage = ["voyageai==0.5.0", "lancedb==0.38.0", "pyarrow==25.0.1", "jsonschema==4.26.0"]
|
|
41
|
+
review = ["attune-forms==0.17.0", "attune-verify==0.6.0", "attune-rag==1.2.0"]
|
|
42
|
+
mcp = ["mcp==2.2.0", "attune-forms==0.17.0", "attune-verify==0.6.0", "attune-rag==1.2.0"]
|
|
43
|
+
memory-native = ["anthropic==1.6.0", "httpx2==2.13.0"]
|
|
44
|
+
|
|
45
|
+
[project.scripts]
|
|
46
|
+
attune-harness = "attune_harness.cli:main"
|
|
47
|
+
|
|
48
|
+
[tool.setuptools.packages.find]
|
|
49
|
+
where = ["src"]
|
|
50
|
+
|
|
51
|
+
[tool.pytest.ini_options]
|
|
52
|
+
testpaths = ["tests"]
|
|
53
|
+
pythonpath = ["src"]
|