loopgrid-haystack 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.
- loopgrid_haystack-0.1.0/LICENSE +202 -0
- loopgrid_haystack-0.1.0/PKG-INFO +241 -0
- loopgrid_haystack-0.1.0/README.md +212 -0
- loopgrid_haystack-0.1.0/pyproject.toml +46 -0
- loopgrid_haystack-0.1.0/setup.cfg +4 -0
- loopgrid_haystack-0.1.0/src/loopgrid_haystack/__init__.py +15 -0
- loopgrid_haystack-0.1.0/src/loopgrid_haystack/integration.py +778 -0
- loopgrid_haystack-0.1.0/src/loopgrid_haystack.egg-info/PKG-INFO +241 -0
- loopgrid_haystack-0.1.0/src/loopgrid_haystack.egg-info/SOURCES.txt +12 -0
- loopgrid_haystack-0.1.0/src/loopgrid_haystack.egg-info/dependency_links.txt +1 -0
- loopgrid_haystack-0.1.0/src/loopgrid_haystack.egg-info/requires.txt +8 -0
- loopgrid_haystack-0.1.0/src/loopgrid_haystack.egg-info/top_level.txt +1 -0
- loopgrid_haystack-0.1.0/tests/test_integration.py +450 -0
- loopgrid_haystack-0.1.0/tests/test_runtime.py +292 -0
|
@@ -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.
|
|
@@ -0,0 +1,241 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: loopgrid-haystack
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: Signed, tamper-evident decision evidence for Haystack Agents using LoopGrid
|
|
5
|
+
Author: LoopGrid
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://loopgrid.io/integrations/haystack/
|
|
8
|
+
Project-URL: Repository, https://github.com/loopgridio/loopgrid-haystack
|
|
9
|
+
Project-URL: Issues, https://github.com/loopgridio/loopgrid-haystack/issues
|
|
10
|
+
Keywords: haystack,haystack-ai,ai-agents,agent-governance,decision-evidence,audit-trail,provenance,tamper-evident,loopgrid
|
|
11
|
+
Classifier: Development Status :: 4 - Beta
|
|
12
|
+
Classifier: Programming Language :: Python :: 3
|
|
13
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.14
|
|
18
|
+
Requires-Python: >=3.10
|
|
19
|
+
Description-Content-Type: text/markdown
|
|
20
|
+
License-File: LICENSE
|
|
21
|
+
Requires-Dist: loopgrid<0.9,>=0.8.0
|
|
22
|
+
Requires-Dist: haystack-ai<3.4,>=3.3.0
|
|
23
|
+
Provides-Extra: dev
|
|
24
|
+
Requires-Dist: pytest>=8; extra == "dev"
|
|
25
|
+
Requires-Dist: pytest-asyncio>=0.24; extra == "dev"
|
|
26
|
+
Requires-Dist: build>=1.2; extra == "dev"
|
|
27
|
+
Requires-Dist: twine>=6; extra == "dev"
|
|
28
|
+
Dynamic: license-file
|
|
29
|
+
|
|
30
|
+
# LoopGrid for Haystack
|
|
31
|
+
|
|
32
|
+
Native Haystack 3.3 Agent hooks + tracing integration for LoopGrid, the evidence plane for AI agents.
|
|
33
|
+
|
|
34
|
+
`loopgrid-haystack` maps Haystack's real Agent lifecycle into LoopGrid decision evidence without changing the LoopGrid Core contract.
|
|
35
|
+
|
|
36
|
+
## Evidence contract
|
|
37
|
+
|
|
38
|
+
```text
|
|
39
|
+
application starts consequential decision
|
|
40
|
+
↓
|
|
41
|
+
Haystack Agent LLM span completes
|
|
42
|
+
↓
|
|
43
|
+
LoopGrid model_completed
|
|
44
|
+
↓
|
|
45
|
+
explicit application policy / human review
|
|
46
|
+
↓
|
|
47
|
+
Haystack ConfirmationHook / other controls
|
|
48
|
+
↓
|
|
49
|
+
LoopGrid before_tool observes the surviving tool call
|
|
50
|
+
↓
|
|
51
|
+
LoopGrid tool_requested
|
|
52
|
+
↓
|
|
53
|
+
actual Haystack tool execution
|
|
54
|
+
↓
|
|
55
|
+
Haystack after_tool
|
|
56
|
+
↓
|
|
57
|
+
LoopGrid tool_executed
|
|
58
|
+
↓
|
|
59
|
+
application explicitly observes downstream outcome
|
|
60
|
+
↓
|
|
61
|
+
LoopGrid outcome_observed
|
|
62
|
+
↓
|
|
63
|
+
evidence_complete → cryptographic verification
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
LoopGrid **does not** execute tools, invent delegated authority, invent policy, infer a reviewer, treat confirmation as authorization by itself, or infer a real-world outcome from a tool return.
|
|
67
|
+
|
|
68
|
+
## Compatibility
|
|
69
|
+
|
|
70
|
+
- Python 3.10–3.14
|
|
71
|
+
- `haystack-ai` 3.3.x
|
|
72
|
+
- `loopgrid` 0.8.x
|
|
73
|
+
- LoopGrid Core validation target: `0.8.1-design-partner`
|
|
74
|
+
|
|
75
|
+
## Install
|
|
76
|
+
|
|
77
|
+
```bash
|
|
78
|
+
pip install loopgrid-haystack
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
## Quickstart
|
|
82
|
+
|
|
83
|
+
```python
|
|
84
|
+
from haystack.components.agents import Agent
|
|
85
|
+
from haystack.dataclasses import ChatMessage
|
|
86
|
+
from loopgrid_haystack import LoopGridHaystack
|
|
87
|
+
|
|
88
|
+
loopgrid = LoopGridHaystack(
|
|
89
|
+
base_url="http://127.0.0.1:8000",
|
|
90
|
+
workspace_id="default",
|
|
91
|
+
agent_id="support-agent",
|
|
92
|
+
)
|
|
93
|
+
|
|
94
|
+
# Explicit: Haystack never enables tracing automatically. If the application already owns
|
|
95
|
+
# a concrete Haystack tracer backend, pass that backend explicitly as delegate=...
|
|
96
|
+
loopgrid.enable_tracing()
|
|
97
|
+
|
|
98
|
+
decision = loopgrid.start_decision(
|
|
99
|
+
decision_type="customer_refund",
|
|
100
|
+
agent={"id": "support-agent", "version": "1"},
|
|
101
|
+
authority={"acting_for": "Example Store", "scope": ["refund:create"], "limit_usd": 100},
|
|
102
|
+
model={"provider": "openai", "name": "gpt-5"},
|
|
103
|
+
context={"prompt_version": "support-v1"},
|
|
104
|
+
proposed_action={"tool": "refund.create", "amount": 25, "currency": "USD"},
|
|
105
|
+
policy={
|
|
106
|
+
"policy_id": "refund-policy",
|
|
107
|
+
"version": "1",
|
|
108
|
+
"decision": "auto_allowed",
|
|
109
|
+
"reason": "Within delegated threshold",
|
|
110
|
+
},
|
|
111
|
+
)
|
|
112
|
+
|
|
113
|
+
agent = Agent(
|
|
114
|
+
chat_generator=...,
|
|
115
|
+
tools=[...],
|
|
116
|
+
hooks=loopgrid.agent_hooks(decision["decision_id"]),
|
|
117
|
+
)
|
|
118
|
+
|
|
119
|
+
result = agent.run(messages=[ChatMessage.from_user("Handle this duplicate charge.")])
|
|
120
|
+
loopgrid.flush()
|
|
121
|
+
loopgrid.assert_healthy()
|
|
122
|
+
|
|
123
|
+
# Only after the application observes the authoritative downstream business result:
|
|
124
|
+
loopgrid.record_outcome(
|
|
125
|
+
decision["decision_id"],
|
|
126
|
+
{"status": "succeeded", "external_reference": "refund_123"},
|
|
127
|
+
observer="billing-webhook",
|
|
128
|
+
)
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
## Human approval / ConfirmationHook
|
|
132
|
+
|
|
133
|
+
Haystack's `ConfirmationHook` remains the execution-control mechanism. LoopGrid records evidence about an application-authenticated reviewer; it does not replace Haystack confirmation or application authorization.
|
|
134
|
+
|
|
135
|
+
**Ordering is critical:** pass confirmation/modification hooks through `before_tool_prefix`. LoopGrid's request hook is appended after them, so a rejected call cannot become `tool_requested` evidence and a modified call is recorded with the final model-visible parameters that survive confirmation.
|
|
136
|
+
|
|
137
|
+
```python
|
|
138
|
+
confirmation_hook = ConfirmationHook(confirmation_strategies={...})
|
|
139
|
+
|
|
140
|
+
agent = Agent(
|
|
141
|
+
chat_generator=...,
|
|
142
|
+
tools=[...],
|
|
143
|
+
hooks=loopgrid.agent_hooks(
|
|
144
|
+
decision_id,
|
|
145
|
+
before_tool_prefix=[confirmation_hook],
|
|
146
|
+
),
|
|
147
|
+
)
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
Your authenticated approval UI/strategy should explicitly record the reviewer when the human makes the decision:
|
|
151
|
+
|
|
152
|
+
```python
|
|
153
|
+
loopgrid.record_human_review(
|
|
154
|
+
decision_id,
|
|
155
|
+
reviewer="reviewer@example.com",
|
|
156
|
+
approved=True,
|
|
157
|
+
reason="Reviewed refund evidence",
|
|
158
|
+
)
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
LoopGrid never derives reviewer identity merely from the fact that a Haystack tool call survived `ConfirmationHook`.
|
|
162
|
+
|
|
163
|
+
`record_human_review()` drains earlier queued framework evidence before writing the explicit
|
|
164
|
+
review event. This preserves the real lifecycle ordering even when the LoopGrid transport is
|
|
165
|
+
temporarily slower than the application thread.
|
|
166
|
+
|
|
167
|
+
## Native integration surfaces
|
|
168
|
+
|
|
169
|
+
The integration uses two different Haystack-native boundaries for two different facts:
|
|
170
|
+
|
|
171
|
+
- `Tracer` / `Span`: `haystack.agent.step.llm` completion → `model_completed`.
|
|
172
|
+
- Agent `before_tool` / `after_tool`: actual surviving tool request and resulting tool message → `tool_requested` / `tool_executed`.
|
|
173
|
+
|
|
174
|
+
Haystack tool spans are deliberately ignored for action evidence. The hooks are authoritative because they run after confirmation/modification and around actual Agent-owned tool execution.
|
|
175
|
+
|
|
176
|
+
## Existing Haystack tracing backends
|
|
177
|
+
|
|
178
|
+
Haystack exposes one process-level tracing facade. `enable_tracing()` is explicit:
|
|
179
|
+
|
|
180
|
+
```python
|
|
181
|
+
loopgrid.enable_tracing()
|
|
182
|
+
```
|
|
183
|
+
|
|
184
|
+
Do **not** capture `haystack.tracing.tracer` and pass that facade back as a delegate. The facade routes to the currently enabled tracer; after LoopGrid is installed that would route back into LoopGrid and recurse.
|
|
185
|
+
|
|
186
|
+
If your application already owns a concrete Haystack tracer instance, compose it explicitly:
|
|
187
|
+
|
|
188
|
+
```python
|
|
189
|
+
existing_backend = MyConcreteHaystackTracer(...)
|
|
190
|
+
loopgrid.enable_tracing(delegate=existing_backend)
|
|
191
|
+
```
|
|
192
|
+
|
|
193
|
+
LoopGrid delegates spans directly to that concrete backend while recording its own evidence. Constructing `LoopGridHaystack` by itself never changes global Haystack tracing.
|
|
194
|
+
|
|
195
|
+
## Privacy
|
|
196
|
+
|
|
197
|
+
LoopGrid defaults to `capture_content=False`.
|
|
198
|
+
|
|
199
|
+
Model span tags and tool inputs/outputs are represented by SHA-256 commitments rather than raw content. Haystack itself also disables content tracing by default. Do not enable `HAYSTACK_CONTENT_TRACING_ENABLED=true` unless your application intentionally permits content export.
|
|
200
|
+
|
|
201
|
+
If you explicitly set `capture_content=True`, LoopGrid will include the tool input/result and captured Haystack trace tags in evidence payloads.
|
|
202
|
+
|
|
203
|
+
## Failure behavior
|
|
204
|
+
|
|
205
|
+
Tracer/hook transport is queued and does not raise into the Haystack Agent execution path. Failures are retained and surfaced explicitly:
|
|
206
|
+
|
|
207
|
+
```python
|
|
208
|
+
loopgrid.flush()
|
|
209
|
+
loopgrid.assert_healthy()
|
|
210
|
+
```
|
|
211
|
+
|
|
212
|
+
A successful Agent run is not evidence that LoopGrid transport succeeded unless `assert_healthy()` passes.
|
|
213
|
+
|
|
214
|
+
## Pre-release validation gates
|
|
215
|
+
|
|
216
|
+
The release candidate is **not a public release**. Required before `v0.1.0`:
|
|
217
|
+
|
|
218
|
+
- exact `haystack-ai==3.3.0` runtime install
|
|
219
|
+
- semantic/unit tests
|
|
220
|
+
- real deterministic Haystack Agent runtime test
|
|
221
|
+
- real LoopGrid Core E2E
|
|
222
|
+
- real native `ConfirmationHook` approval ordering E2E
|
|
223
|
+
- rejection and modification regression tests
|
|
224
|
+
- parallel tool-call correlation test
|
|
225
|
+
- repeated-call idempotency across later Agent steps, including missing/reused call IDs
|
|
226
|
+
- queued-event ordering before explicit human review/outcome writes
|
|
227
|
+
- real `Agent.run_async()` runtime regression
|
|
228
|
+
- privacy regression
|
|
229
|
+
- concurrency isolation
|
|
230
|
+
- transport-failure observability
|
|
231
|
+
- `evidence_complete`, applicable coverage 100%, `verify.valid=true`, failures `[]`
|
|
232
|
+
- wheel/sdist build + `twine check`
|
|
233
|
+
- fresh wheel install/import test
|
|
234
|
+
- GitHub CI, exact tested commit tag/release
|
|
235
|
+
- PyPI Trusted Publishing + fresh public install
|
|
236
|
+
- website/docs after public install
|
|
237
|
+
- official Haystack Integrations PR after all release gates pass
|
|
238
|
+
|
|
239
|
+
## License
|
|
240
|
+
|
|
241
|
+
Apache-2.0.
|
|
@@ -0,0 +1,212 @@
|
|
|
1
|
+
# LoopGrid for Haystack
|
|
2
|
+
|
|
3
|
+
Native Haystack 3.3 Agent hooks + tracing integration for LoopGrid, the evidence plane for AI agents.
|
|
4
|
+
|
|
5
|
+
`loopgrid-haystack` maps Haystack's real Agent lifecycle into LoopGrid decision evidence without changing the LoopGrid Core contract.
|
|
6
|
+
|
|
7
|
+
## Evidence contract
|
|
8
|
+
|
|
9
|
+
```text
|
|
10
|
+
application starts consequential decision
|
|
11
|
+
↓
|
|
12
|
+
Haystack Agent LLM span completes
|
|
13
|
+
↓
|
|
14
|
+
LoopGrid model_completed
|
|
15
|
+
↓
|
|
16
|
+
explicit application policy / human review
|
|
17
|
+
↓
|
|
18
|
+
Haystack ConfirmationHook / other controls
|
|
19
|
+
↓
|
|
20
|
+
LoopGrid before_tool observes the surviving tool call
|
|
21
|
+
↓
|
|
22
|
+
LoopGrid tool_requested
|
|
23
|
+
↓
|
|
24
|
+
actual Haystack tool execution
|
|
25
|
+
↓
|
|
26
|
+
Haystack after_tool
|
|
27
|
+
↓
|
|
28
|
+
LoopGrid tool_executed
|
|
29
|
+
↓
|
|
30
|
+
application explicitly observes downstream outcome
|
|
31
|
+
↓
|
|
32
|
+
LoopGrid outcome_observed
|
|
33
|
+
↓
|
|
34
|
+
evidence_complete → cryptographic verification
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
LoopGrid **does not** execute tools, invent delegated authority, invent policy, infer a reviewer, treat confirmation as authorization by itself, or infer a real-world outcome from a tool return.
|
|
38
|
+
|
|
39
|
+
## Compatibility
|
|
40
|
+
|
|
41
|
+
- Python 3.10–3.14
|
|
42
|
+
- `haystack-ai` 3.3.x
|
|
43
|
+
- `loopgrid` 0.8.x
|
|
44
|
+
- LoopGrid Core validation target: `0.8.1-design-partner`
|
|
45
|
+
|
|
46
|
+
## Install
|
|
47
|
+
|
|
48
|
+
```bash
|
|
49
|
+
pip install loopgrid-haystack
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
## Quickstart
|
|
53
|
+
|
|
54
|
+
```python
|
|
55
|
+
from haystack.components.agents import Agent
|
|
56
|
+
from haystack.dataclasses import ChatMessage
|
|
57
|
+
from loopgrid_haystack import LoopGridHaystack
|
|
58
|
+
|
|
59
|
+
loopgrid = LoopGridHaystack(
|
|
60
|
+
base_url="http://127.0.0.1:8000",
|
|
61
|
+
workspace_id="default",
|
|
62
|
+
agent_id="support-agent",
|
|
63
|
+
)
|
|
64
|
+
|
|
65
|
+
# Explicit: Haystack never enables tracing automatically. If the application already owns
|
|
66
|
+
# a concrete Haystack tracer backend, pass that backend explicitly as delegate=...
|
|
67
|
+
loopgrid.enable_tracing()
|
|
68
|
+
|
|
69
|
+
decision = loopgrid.start_decision(
|
|
70
|
+
decision_type="customer_refund",
|
|
71
|
+
agent={"id": "support-agent", "version": "1"},
|
|
72
|
+
authority={"acting_for": "Example Store", "scope": ["refund:create"], "limit_usd": 100},
|
|
73
|
+
model={"provider": "openai", "name": "gpt-5"},
|
|
74
|
+
context={"prompt_version": "support-v1"},
|
|
75
|
+
proposed_action={"tool": "refund.create", "amount": 25, "currency": "USD"},
|
|
76
|
+
policy={
|
|
77
|
+
"policy_id": "refund-policy",
|
|
78
|
+
"version": "1",
|
|
79
|
+
"decision": "auto_allowed",
|
|
80
|
+
"reason": "Within delegated threshold",
|
|
81
|
+
},
|
|
82
|
+
)
|
|
83
|
+
|
|
84
|
+
agent = Agent(
|
|
85
|
+
chat_generator=...,
|
|
86
|
+
tools=[...],
|
|
87
|
+
hooks=loopgrid.agent_hooks(decision["decision_id"]),
|
|
88
|
+
)
|
|
89
|
+
|
|
90
|
+
result = agent.run(messages=[ChatMessage.from_user("Handle this duplicate charge.")])
|
|
91
|
+
loopgrid.flush()
|
|
92
|
+
loopgrid.assert_healthy()
|
|
93
|
+
|
|
94
|
+
# Only after the application observes the authoritative downstream business result:
|
|
95
|
+
loopgrid.record_outcome(
|
|
96
|
+
decision["decision_id"],
|
|
97
|
+
{"status": "succeeded", "external_reference": "refund_123"},
|
|
98
|
+
observer="billing-webhook",
|
|
99
|
+
)
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
## Human approval / ConfirmationHook
|
|
103
|
+
|
|
104
|
+
Haystack's `ConfirmationHook` remains the execution-control mechanism. LoopGrid records evidence about an application-authenticated reviewer; it does not replace Haystack confirmation or application authorization.
|
|
105
|
+
|
|
106
|
+
**Ordering is critical:** pass confirmation/modification hooks through `before_tool_prefix`. LoopGrid's request hook is appended after them, so a rejected call cannot become `tool_requested` evidence and a modified call is recorded with the final model-visible parameters that survive confirmation.
|
|
107
|
+
|
|
108
|
+
```python
|
|
109
|
+
confirmation_hook = ConfirmationHook(confirmation_strategies={...})
|
|
110
|
+
|
|
111
|
+
agent = Agent(
|
|
112
|
+
chat_generator=...,
|
|
113
|
+
tools=[...],
|
|
114
|
+
hooks=loopgrid.agent_hooks(
|
|
115
|
+
decision_id,
|
|
116
|
+
before_tool_prefix=[confirmation_hook],
|
|
117
|
+
),
|
|
118
|
+
)
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
Your authenticated approval UI/strategy should explicitly record the reviewer when the human makes the decision:
|
|
122
|
+
|
|
123
|
+
```python
|
|
124
|
+
loopgrid.record_human_review(
|
|
125
|
+
decision_id,
|
|
126
|
+
reviewer="reviewer@example.com",
|
|
127
|
+
approved=True,
|
|
128
|
+
reason="Reviewed refund evidence",
|
|
129
|
+
)
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
LoopGrid never derives reviewer identity merely from the fact that a Haystack tool call survived `ConfirmationHook`.
|
|
133
|
+
|
|
134
|
+
`record_human_review()` drains earlier queued framework evidence before writing the explicit
|
|
135
|
+
review event. This preserves the real lifecycle ordering even when the LoopGrid transport is
|
|
136
|
+
temporarily slower than the application thread.
|
|
137
|
+
|
|
138
|
+
## Native integration surfaces
|
|
139
|
+
|
|
140
|
+
The integration uses two different Haystack-native boundaries for two different facts:
|
|
141
|
+
|
|
142
|
+
- `Tracer` / `Span`: `haystack.agent.step.llm` completion → `model_completed`.
|
|
143
|
+
- Agent `before_tool` / `after_tool`: actual surviving tool request and resulting tool message → `tool_requested` / `tool_executed`.
|
|
144
|
+
|
|
145
|
+
Haystack tool spans are deliberately ignored for action evidence. The hooks are authoritative because they run after confirmation/modification and around actual Agent-owned tool execution.
|
|
146
|
+
|
|
147
|
+
## Existing Haystack tracing backends
|
|
148
|
+
|
|
149
|
+
Haystack exposes one process-level tracing facade. `enable_tracing()` is explicit:
|
|
150
|
+
|
|
151
|
+
```python
|
|
152
|
+
loopgrid.enable_tracing()
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
Do **not** capture `haystack.tracing.tracer` and pass that facade back as a delegate. The facade routes to the currently enabled tracer; after LoopGrid is installed that would route back into LoopGrid and recurse.
|
|
156
|
+
|
|
157
|
+
If your application already owns a concrete Haystack tracer instance, compose it explicitly:
|
|
158
|
+
|
|
159
|
+
```python
|
|
160
|
+
existing_backend = MyConcreteHaystackTracer(...)
|
|
161
|
+
loopgrid.enable_tracing(delegate=existing_backend)
|
|
162
|
+
```
|
|
163
|
+
|
|
164
|
+
LoopGrid delegates spans directly to that concrete backend while recording its own evidence. Constructing `LoopGridHaystack` by itself never changes global Haystack tracing.
|
|
165
|
+
|
|
166
|
+
## Privacy
|
|
167
|
+
|
|
168
|
+
LoopGrid defaults to `capture_content=False`.
|
|
169
|
+
|
|
170
|
+
Model span tags and tool inputs/outputs are represented by SHA-256 commitments rather than raw content. Haystack itself also disables content tracing by default. Do not enable `HAYSTACK_CONTENT_TRACING_ENABLED=true` unless your application intentionally permits content export.
|
|
171
|
+
|
|
172
|
+
If you explicitly set `capture_content=True`, LoopGrid will include the tool input/result and captured Haystack trace tags in evidence payloads.
|
|
173
|
+
|
|
174
|
+
## Failure behavior
|
|
175
|
+
|
|
176
|
+
Tracer/hook transport is queued and does not raise into the Haystack Agent execution path. Failures are retained and surfaced explicitly:
|
|
177
|
+
|
|
178
|
+
```python
|
|
179
|
+
loopgrid.flush()
|
|
180
|
+
loopgrid.assert_healthy()
|
|
181
|
+
```
|
|
182
|
+
|
|
183
|
+
A successful Agent run is not evidence that LoopGrid transport succeeded unless `assert_healthy()` passes.
|
|
184
|
+
|
|
185
|
+
## Pre-release validation gates
|
|
186
|
+
|
|
187
|
+
The release candidate is **not a public release**. Required before `v0.1.0`:
|
|
188
|
+
|
|
189
|
+
- exact `haystack-ai==3.3.0` runtime install
|
|
190
|
+
- semantic/unit tests
|
|
191
|
+
- real deterministic Haystack Agent runtime test
|
|
192
|
+
- real LoopGrid Core E2E
|
|
193
|
+
- real native `ConfirmationHook` approval ordering E2E
|
|
194
|
+
- rejection and modification regression tests
|
|
195
|
+
- parallel tool-call correlation test
|
|
196
|
+
- repeated-call idempotency across later Agent steps, including missing/reused call IDs
|
|
197
|
+
- queued-event ordering before explicit human review/outcome writes
|
|
198
|
+
- real `Agent.run_async()` runtime regression
|
|
199
|
+
- privacy regression
|
|
200
|
+
- concurrency isolation
|
|
201
|
+
- transport-failure observability
|
|
202
|
+
- `evidence_complete`, applicable coverage 100%, `verify.valid=true`, failures `[]`
|
|
203
|
+
- wheel/sdist build + `twine check`
|
|
204
|
+
- fresh wheel install/import test
|
|
205
|
+
- GitHub CI, exact tested commit tag/release
|
|
206
|
+
- PyPI Trusted Publishing + fresh public install
|
|
207
|
+
- website/docs after public install
|
|
208
|
+
- official Haystack Integrations PR after all release gates pass
|
|
209
|
+
|
|
210
|
+
## License
|
|
211
|
+
|
|
212
|
+
Apache-2.0.
|