wasmagent-protocol 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.
- wasmagent_protocol-0.1.0/.claude-bot/verify.yml +19 -0
- wasmagent_protocol-0.1.0/.github/workflows/conformance.yml +46 -0
- wasmagent_protocol-0.1.0/.github/workflows/release.yml +53 -0
- wasmagent_protocol-0.1.0/.gitignore +16 -0
- wasmagent_protocol-0.1.0/CODEOWNERS +6 -0
- wasmagent_protocol-0.1.0/LICENSE +202 -0
- wasmagent_protocol-0.1.0/PKG-INFO +126 -0
- wasmagent_protocol-0.1.0/README.md +106 -0
- wasmagent_protocol-0.1.0/biome.json +8 -0
- wasmagent_protocol-0.1.0/docs/15-milestones.md +42 -0
- wasmagent_protocol-0.1.0/docs/CONTRACT-CHANGE-PROCESS.md +57 -0
- wasmagent_protocol-0.1.0/docs/GOVERNANCE.md +71 -0
- wasmagent_protocol-0.1.0/index.d.ts +32 -0
- wasmagent_protocol-0.1.0/index.js +32 -0
- wasmagent_protocol-0.1.0/package.json +36 -0
- wasmagent_protocol-0.1.0/pyproject.toml +37 -0
- wasmagent_protocol-0.1.0/schemas/aep/aep-record.schema.json +177 -0
- wasmagent_protocol-0.1.0/schemas/compliance/compliance-eval-record.schema.json +135 -0
- wasmagent_protocol-0.1.0/schemas/compliance/constraint-ir.schema.json +82 -0
- wasmagent_protocol-0.1.0/schemas/compliance/constraint-violation.schema.json +103 -0
- wasmagent_protocol-0.1.0/schemas/compliance/repair-trace.schema.json +73 -0
- wasmagent_protocol-0.1.0/schemas/compliance/rollout-wire.schema.json +267 -0
- wasmagent_protocol-0.1.0/schemas/compliance/task-spec.schema.json +119 -0
- wasmagent_protocol-0.1.0/schemas/index.json +85 -0
- wasmagent_protocol-0.1.0/src/wasmagent_protocol/__init__.py +76 -0
- wasmagent_protocol-0.1.0/tests/conformance.py +195 -0
- wasmagent_protocol-0.1.0/tests/fixtures/invalid/aep-record/example.json +4 -0
- wasmagent_protocol-0.1.0/tests/fixtures/invalid/compliance-eval-record/example.json +10 -0
- wasmagent_protocol-0.1.0/tests/fixtures/invalid/constraint-ir/example.json +9 -0
- wasmagent_protocol-0.1.0/tests/fixtures/invalid/constraint-violation/example.json +8 -0
- wasmagent_protocol-0.1.0/tests/fixtures/invalid/repair-trace/example.json +6 -0
- wasmagent_protocol-0.1.0/tests/fixtures/invalid/rollout-wire/example.json +4 -0
- wasmagent_protocol-0.1.0/tests/fixtures/invalid/task-spec/example.json +9 -0
- wasmagent_protocol-0.1.0/tests/fixtures/valid/aep-record/example.json +28 -0
- wasmagent_protocol-0.1.0/tests/fixtures/valid/compliance-eval-record/example.json +11 -0
- wasmagent_protocol-0.1.0/tests/fixtures/valid/constraint-ir/example.json +8 -0
- wasmagent_protocol-0.1.0/tests/fixtures/valid/constraint-violation/example.json +13 -0
- wasmagent_protocol-0.1.0/tests/fixtures/valid/repair-trace/example.json +9 -0
- wasmagent_protocol-0.1.0/tests/fixtures/valid/rollout-wire/example.json +9 -0
- wasmagent_protocol-0.1.0/tests/fixtures/valid/task-spec/example.json +19 -0
- wasmagent_protocol-0.1.0/tests/loader.test.js +25 -0
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# Verification pipeline for wasmagent-protocol.
|
|
2
|
+
# Consumed by the WasmAgent bot's merge gate. All commands must exit 0 for a PR
|
|
3
|
+
# to be considered green. This repo is spec-only, so verification = schemas are
|
|
4
|
+
# well-formed, refs resolve, fixtures pass/fail correctly, and both loaders work.
|
|
5
|
+
version: 1
|
|
6
|
+
|
|
7
|
+
setup:
|
|
8
|
+
- python3 -m pip install --quiet --upgrade jsonschema referencing build
|
|
9
|
+
|
|
10
|
+
steps:
|
|
11
|
+
- name: schema-conformance
|
|
12
|
+
run: python3 tests/conformance.py
|
|
13
|
+
- name: js-loader
|
|
14
|
+
run: node --test
|
|
15
|
+
- name: python-wheel-import
|
|
16
|
+
run: |
|
|
17
|
+
python3 -m build --wheel
|
|
18
|
+
python3 -m pip install --quiet --force-reinstall dist/*.whl
|
|
19
|
+
python3 -c "from wasmagent_protocol import get_schema; assert get_schema('aep-record')['title']=='AEPRecord'"
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
name: conformance
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
pull_request:
|
|
5
|
+
push:
|
|
6
|
+
branches: [main]
|
|
7
|
+
workflow_dispatch:
|
|
8
|
+
|
|
9
|
+
jobs:
|
|
10
|
+
schema-conformance:
|
|
11
|
+
name: Schema conformance (Python)
|
|
12
|
+
runs-on: ubuntu-latest
|
|
13
|
+
steps:
|
|
14
|
+
- uses: actions/checkout@v4
|
|
15
|
+
- uses: actions/setup-python@v5
|
|
16
|
+
with:
|
|
17
|
+
python-version: '3.x'
|
|
18
|
+
- run: python -m pip install --upgrade pip jsonschema referencing
|
|
19
|
+
- name: Validate schemas + fixtures
|
|
20
|
+
run: python tests/conformance.py
|
|
21
|
+
|
|
22
|
+
js-loader:
|
|
23
|
+
name: JS loader smoke test
|
|
24
|
+
runs-on: ubuntu-latest
|
|
25
|
+
steps:
|
|
26
|
+
- uses: actions/checkout@v4
|
|
27
|
+
- uses: actions/setup-node@v4
|
|
28
|
+
with:
|
|
29
|
+
node-version: '20'
|
|
30
|
+
- name: getSchema round-trips every registered id
|
|
31
|
+
run: node --test
|
|
32
|
+
|
|
33
|
+
python-loader:
|
|
34
|
+
name: Python loader smoke test
|
|
35
|
+
runs-on: ubuntu-latest
|
|
36
|
+
steps:
|
|
37
|
+
- uses: actions/checkout@v4
|
|
38
|
+
- uses: actions/setup-python@v5
|
|
39
|
+
with:
|
|
40
|
+
python-version: '3.x'
|
|
41
|
+
- run: python -m pip install --upgrade pip build
|
|
42
|
+
- name: Build wheel and import from it
|
|
43
|
+
run: |
|
|
44
|
+
python -m build --wheel
|
|
45
|
+
python -m pip install dist/*.whl
|
|
46
|
+
python -c "from wasmagent_protocol import get_schema, schema_ids; assert get_schema('aep-record')['title']=='AEPRecord'; print('ids:', schema_ids())"
|
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
name: release
|
|
2
|
+
|
|
3
|
+
# Publishes wasmagent-protocol to PyPI via Trusted Publishing (OIDC) on version
|
|
4
|
+
# tags. No API token or secret is stored — PyPI verifies this workflow's OIDC
|
|
5
|
+
# identity against the pending/active publisher registered for the project
|
|
6
|
+
# (repo WasmAgent/wasmagent-protocol, workflow release.yml, no environment).
|
|
7
|
+
on:
|
|
8
|
+
push:
|
|
9
|
+
tags:
|
|
10
|
+
- 'v*'
|
|
11
|
+
workflow_dispatch:
|
|
12
|
+
|
|
13
|
+
permissions:
|
|
14
|
+
contents: read
|
|
15
|
+
|
|
16
|
+
jobs:
|
|
17
|
+
build:
|
|
18
|
+
name: Build distributions
|
|
19
|
+
runs-on: ubuntu-latest
|
|
20
|
+
steps:
|
|
21
|
+
- uses: actions/checkout@v4
|
|
22
|
+
- uses: actions/setup-python@v5
|
|
23
|
+
with:
|
|
24
|
+
python-version: '3.x'
|
|
25
|
+
- name: Build sdist + wheel
|
|
26
|
+
run: |
|
|
27
|
+
python -m pip install --upgrade pip build twine
|
|
28
|
+
python -m build
|
|
29
|
+
twine check dist/*
|
|
30
|
+
- name: Verify the built wheel is importable and schemas load
|
|
31
|
+
run: |
|
|
32
|
+
python -m pip install dist/*.whl
|
|
33
|
+
python -c "from wasmagent_protocol import get_schema, schema_ids; assert get_schema('aep-record')['title']=='AEPRecord'; print('ids:', schema_ids())"
|
|
34
|
+
- uses: actions/upload-artifact@v4
|
|
35
|
+
with:
|
|
36
|
+
name: dist
|
|
37
|
+
path: dist/
|
|
38
|
+
|
|
39
|
+
pypi-publish:
|
|
40
|
+
name: Publish to PyPI (Trusted Publishing)
|
|
41
|
+
needs: build
|
|
42
|
+
runs-on: ubuntu-latest
|
|
43
|
+
# No `environment:` — the pending publisher was registered with an empty
|
|
44
|
+
# environment, so this job must also run without one to match.
|
|
45
|
+
permissions:
|
|
46
|
+
id-token: write # mandatory for OIDC trusted publishing
|
|
47
|
+
steps:
|
|
48
|
+
- uses: actions/download-artifact@v4
|
|
49
|
+
with:
|
|
50
|
+
name: dist
|
|
51
|
+
path: dist/
|
|
52
|
+
- name: Publish to PyPI
|
|
53
|
+
uses: pypa/gh-action-pypi-publish@release/v1
|
|
@@ -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,126 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: wasmagent-protocol
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: Canonical JSON Schemas for the WasmAgent Agent Evidence Protocol (AEP) and compliance contracts. Single source of truth across the WasmAgent org.
|
|
5
|
+
Project-URL: Homepage, https://github.com/WasmAgent/wasmagent-protocol
|
|
6
|
+
Project-URL: Issues, https://github.com/WasmAgent/wasmagent-protocol/issues
|
|
7
|
+
Author: WasmAgent
|
|
8
|
+
License-Expression: Apache-2.0
|
|
9
|
+
License-File: LICENSE
|
|
10
|
+
Keywords: aep,agent-evidence-protocol,compliance,json-schema,provenance,wasmagent
|
|
11
|
+
Classifier: Development Status :: 3 - Alpha
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
14
|
+
Classifier: Programming Language :: Python :: 3
|
|
15
|
+
Classifier: Topic :: Software Development :: Libraries
|
|
16
|
+
Requires-Python: >=3.9
|
|
17
|
+
Provides-Extra: validate
|
|
18
|
+
Requires-Dist: jsonschema>=4.0; extra == 'validate'
|
|
19
|
+
Description-Content-Type: text/markdown
|
|
20
|
+
|
|
21
|
+
# wasmagent-protocol
|
|
22
|
+
|
|
23
|
+
> **Canonical source of truth for every cross-repository contract in the
|
|
24
|
+
> [WasmAgent](https://github.com/WasmAgent) org.** One public schema → one
|
|
25
|
+
> canonical source.
|
|
26
|
+
|
|
27
|
+
WasmAgent is open infrastructure for _provable_ AI agents. Proving an agent ran
|
|
28
|
+
correctly requires that every repository — the runtime, the gateway, the
|
|
29
|
+
evidence pipelines, the audit product — speak the **same** evidence and
|
|
30
|
+
compliance vocabulary. `wasmagent-protocol` is where that vocabulary is defined,
|
|
31
|
+
versioned, and published, so no repository has to keep its own copy.
|
|
32
|
+
|
|
33
|
+
This repository holds **specifications only**. It contains no business logic,
|
|
34
|
+
no runtime, and no product code — only JSON Schemas, conformance fixtures, and
|
|
35
|
+
thin loader packages that expose the schemas to JavaScript and Python
|
|
36
|
+
consumers.
|
|
37
|
+
|
|
38
|
+
## Why this repository exists
|
|
39
|
+
|
|
40
|
+
The Agent Evidence Protocol (AEP) and the compliance schemas were originally
|
|
41
|
+
authored inside `wasmagent-js` and independently copied into `trace-pipeline`.
|
|
42
|
+
By the time this repository was extracted, those copies had **drifted**: five
|
|
43
|
+
shared schemas differed (one had a copy-paste `title` bug, and the same logical
|
|
44
|
+
schema carried two conflicting `$id` URLs). Drift in a shared contract silently
|
|
45
|
+
breaks cross-repo evidence validation — exactly the failure mode WasmAgent
|
|
46
|
+
exists to prevent.
|
|
47
|
+
|
|
48
|
+
Per the org [repository boundary policy](https://github.com/WasmAgent/.github/blob/main/docs/repository-boundaries.md):
|
|
49
|
+
**one public schema has exactly one canonical source.** That source is here.
|
|
50
|
+
|
|
51
|
+
## What's in scope
|
|
52
|
+
|
|
53
|
+
Only contracts that genuinely cross a repository boundary:
|
|
54
|
+
|
|
55
|
+
| Schema | Version | Consumers |
|
|
56
|
+
| --- | --- | --- |
|
|
57
|
+
| `aep-record` | `aep/v0.2` | wasmagent-js, wasmagent-proxy, trace-pipeline, wasmagent-train-replay, open-agent-audit |
|
|
58
|
+
| `constraint-ir` | `compliance/v1` | wasmagent-js, trace-pipeline |
|
|
59
|
+
| `constraint-violation` | `compliance/v1` | wasmagent-js, trace-pipeline |
|
|
60
|
+
| `repair-trace` | `compliance/v1` | wasmagent-js, trace-pipeline |
|
|
61
|
+
| `task-spec` | `compliance/v1` | wasmagent-js, trace-pipeline |
|
|
62
|
+
| `compliance-eval-record` | `compliance-eval-record/v1` | wasmagent-js, trace-pipeline |
|
|
63
|
+
| `rollout-wire` | `rollout-wire/v1` | wasmagent-js, trace-pipeline |
|
|
64
|
+
|
|
65
|
+
The machine-readable registry is [`schemas/index.json`](schemas/index.json).
|
|
66
|
+
|
|
67
|
+
**Out of scope:** schemas owned by a single repository (e.g. trace-pipeline's
|
|
68
|
+
`*-training-record` output formats, open-agent-audit's `audit-run`). A schema
|
|
69
|
+
belongs here only when two or more repositories must agree on it.
|
|
70
|
+
|
|
71
|
+
## Consuming the schemas
|
|
72
|
+
|
|
73
|
+
Downstream repositories **must not** copy schema JSON. Depend on the published
|
|
74
|
+
package instead.
|
|
75
|
+
|
|
76
|
+
### JavaScript / TypeScript
|
|
77
|
+
|
|
78
|
+
```bash
|
|
79
|
+
npm install @wasmagent/protocol
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
```ts
|
|
83
|
+
import { schemas, getSchema } from "@wasmagent/protocol";
|
|
84
|
+
|
|
85
|
+
const aep = getSchema("aep-record"); // parsed JSON Schema object
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
### Python
|
|
89
|
+
|
|
90
|
+
```bash
|
|
91
|
+
pip install wasmagent-protocol
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
```python
|
|
95
|
+
from wasmagent_protocol import get_schema, schema_path
|
|
96
|
+
|
|
97
|
+
aep = get_schema("aep-record") # parsed dict
|
|
98
|
+
path = schema_path("aep-record") # pathlib.Path to the .json file
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
## Versioning & stability
|
|
102
|
+
|
|
103
|
+
- Each schema carries a `version` string (see the registry).
|
|
104
|
+
- **Additive** changes (new optional field) → minor package bump.
|
|
105
|
+
- **Breaking** changes (removed/renamed field, tightened `required`) → major
|
|
106
|
+
package bump **and** a new `version` value, announced in the
|
|
107
|
+
[org release ledger](https://github.com/WasmAgent/.github/blob/main/releases/public-release-ledger.yml)
|
|
108
|
+
before merge.
|
|
109
|
+
- Every schema has at least one valid and one invalid conformance fixture under
|
|
110
|
+
[`tests/fixtures/`](tests/fixtures/). CI rejects any schema without both.
|
|
111
|
+
|
|
112
|
+
See [`docs/CONTRACT-CHANGE-PROCESS.md`](docs/CONTRACT-CHANGE-PROCESS.md) for the
|
|
113
|
+
full change workflow and [`docs/GOVERNANCE.md`](docs/GOVERNANCE.md) for
|
|
114
|
+
maintainer and exit-condition policy.
|
|
115
|
+
|
|
116
|
+
## Development
|
|
117
|
+
|
|
118
|
+
```bash
|
|
119
|
+
# validate every schema is well-formed and every fixture conforms
|
|
120
|
+
python3 -m pip install jsonschema
|
|
121
|
+
python3 tests/conformance.py
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
## License
|
|
125
|
+
|
|
126
|
+
[Apache-2.0](LICENSE).
|
|
@@ -0,0 +1,106 @@
|
|
|
1
|
+
# wasmagent-protocol
|
|
2
|
+
|
|
3
|
+
> **Canonical source of truth for every cross-repository contract in the
|
|
4
|
+
> [WasmAgent](https://github.com/WasmAgent) org.** One public schema → one
|
|
5
|
+
> canonical source.
|
|
6
|
+
|
|
7
|
+
WasmAgent is open infrastructure for _provable_ AI agents. Proving an agent ran
|
|
8
|
+
correctly requires that every repository — the runtime, the gateway, the
|
|
9
|
+
evidence pipelines, the audit product — speak the **same** evidence and
|
|
10
|
+
compliance vocabulary. `wasmagent-protocol` is where that vocabulary is defined,
|
|
11
|
+
versioned, and published, so no repository has to keep its own copy.
|
|
12
|
+
|
|
13
|
+
This repository holds **specifications only**. It contains no business logic,
|
|
14
|
+
no runtime, and no product code — only JSON Schemas, conformance fixtures, and
|
|
15
|
+
thin loader packages that expose the schemas to JavaScript and Python
|
|
16
|
+
consumers.
|
|
17
|
+
|
|
18
|
+
## Why this repository exists
|
|
19
|
+
|
|
20
|
+
The Agent Evidence Protocol (AEP) and the compliance schemas were originally
|
|
21
|
+
authored inside `wasmagent-js` and independently copied into `trace-pipeline`.
|
|
22
|
+
By the time this repository was extracted, those copies had **drifted**: five
|
|
23
|
+
shared schemas differed (one had a copy-paste `title` bug, and the same logical
|
|
24
|
+
schema carried two conflicting `$id` URLs). Drift in a shared contract silently
|
|
25
|
+
breaks cross-repo evidence validation — exactly the failure mode WasmAgent
|
|
26
|
+
exists to prevent.
|
|
27
|
+
|
|
28
|
+
Per the org [repository boundary policy](https://github.com/WasmAgent/.github/blob/main/docs/repository-boundaries.md):
|
|
29
|
+
**one public schema has exactly one canonical source.** That source is here.
|
|
30
|
+
|
|
31
|
+
## What's in scope
|
|
32
|
+
|
|
33
|
+
Only contracts that genuinely cross a repository boundary:
|
|
34
|
+
|
|
35
|
+
| Schema | Version | Consumers |
|
|
36
|
+
| --- | --- | --- |
|
|
37
|
+
| `aep-record` | `aep/v0.2` | wasmagent-js, wasmagent-proxy, trace-pipeline, wasmagent-train-replay, open-agent-audit |
|
|
38
|
+
| `constraint-ir` | `compliance/v1` | wasmagent-js, trace-pipeline |
|
|
39
|
+
| `constraint-violation` | `compliance/v1` | wasmagent-js, trace-pipeline |
|
|
40
|
+
| `repair-trace` | `compliance/v1` | wasmagent-js, trace-pipeline |
|
|
41
|
+
| `task-spec` | `compliance/v1` | wasmagent-js, trace-pipeline |
|
|
42
|
+
| `compliance-eval-record` | `compliance-eval-record/v1` | wasmagent-js, trace-pipeline |
|
|
43
|
+
| `rollout-wire` | `rollout-wire/v1` | wasmagent-js, trace-pipeline |
|
|
44
|
+
|
|
45
|
+
The machine-readable registry is [`schemas/index.json`](schemas/index.json).
|
|
46
|
+
|
|
47
|
+
**Out of scope:** schemas owned by a single repository (e.g. trace-pipeline's
|
|
48
|
+
`*-training-record` output formats, open-agent-audit's `audit-run`). A schema
|
|
49
|
+
belongs here only when two or more repositories must agree on it.
|
|
50
|
+
|
|
51
|
+
## Consuming the schemas
|
|
52
|
+
|
|
53
|
+
Downstream repositories **must not** copy schema JSON. Depend on the published
|
|
54
|
+
package instead.
|
|
55
|
+
|
|
56
|
+
### JavaScript / TypeScript
|
|
57
|
+
|
|
58
|
+
```bash
|
|
59
|
+
npm install @wasmagent/protocol
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
```ts
|
|
63
|
+
import { schemas, getSchema } from "@wasmagent/protocol";
|
|
64
|
+
|
|
65
|
+
const aep = getSchema("aep-record"); // parsed JSON Schema object
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
### Python
|
|
69
|
+
|
|
70
|
+
```bash
|
|
71
|
+
pip install wasmagent-protocol
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
```python
|
|
75
|
+
from wasmagent_protocol import get_schema, schema_path
|
|
76
|
+
|
|
77
|
+
aep = get_schema("aep-record") # parsed dict
|
|
78
|
+
path = schema_path("aep-record") # pathlib.Path to the .json file
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
## Versioning & stability
|
|
82
|
+
|
|
83
|
+
- Each schema carries a `version` string (see the registry).
|
|
84
|
+
- **Additive** changes (new optional field) → minor package bump.
|
|
85
|
+
- **Breaking** changes (removed/renamed field, tightened `required`) → major
|
|
86
|
+
package bump **and** a new `version` value, announced in the
|
|
87
|
+
[org release ledger](https://github.com/WasmAgent/.github/blob/main/releases/public-release-ledger.yml)
|
|
88
|
+
before merge.
|
|
89
|
+
- Every schema has at least one valid and one invalid conformance fixture under
|
|
90
|
+
[`tests/fixtures/`](tests/fixtures/). CI rejects any schema without both.
|
|
91
|
+
|
|
92
|
+
See [`docs/CONTRACT-CHANGE-PROCESS.md`](docs/CONTRACT-CHANGE-PROCESS.md) for the
|
|
93
|
+
full change workflow and [`docs/GOVERNANCE.md`](docs/GOVERNANCE.md) for
|
|
94
|
+
maintainer and exit-condition policy.
|
|
95
|
+
|
|
96
|
+
## Development
|
|
97
|
+
|
|
98
|
+
```bash
|
|
99
|
+
# validate every schema is well-formed and every fixture conforms
|
|
100
|
+
python3 -m pip install jsonschema
|
|
101
|
+
python3 tests/conformance.py
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
## License
|
|
105
|
+
|
|
106
|
+
[Apache-2.0](LICENSE).
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
{
|
|
2
|
+
"$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
|
|
3
|
+
"vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true },
|
|
4
|
+
"files": { "ignoreUnknown": true, "ignore": ["**/dist", "**/node_modules", "**/coverage", "**/.turbo", "**/target"] },
|
|
5
|
+
"formatter": { "enabled": true, "indentStyle": "space", "indentWidth": 2, "lineWidth": 100 },
|
|
6
|
+
"linter": { "enabled": true, "rules": { "recommended": true } },
|
|
7
|
+
"javascript": { "formatter": { "quoteStyle": "single", "trailingCommas": "all", "semicolons": "always" } }
|
|
8
|
+
}
|
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
# wasmagent-protocol — Milestones
|
|
2
|
+
|
|
3
|
+
Living roadmap for the canonical protocol repository. The bot converts unchecked
|
|
4
|
+
bullets into issues. Each bullet is scoped to concrete files.
|
|
5
|
+
|
|
6
|
+
## Milestone 1 — Extraction & single source of truth
|
|
7
|
+
|
|
8
|
+
- [x] Extract AEP + compliance schemas from `wasmagent-js` and `trace-pipeline`
|
|
9
|
+
into `schemas/`, reconciling the drift (canonical `$id`, JSON Schema
|
|
10
|
+
2020-12, fixed `title` bug).
|
|
11
|
+
- [x] Publish loaders: `@wasmagent/protocol` (npm) and `wasmagent-protocol`
|
|
12
|
+
(PyPI); machine-readable registry at `schemas/index.json`.
|
|
13
|
+
- [x] Conformance harness: every schema well-formed, refs resolve, valid/invalid
|
|
14
|
+
fixtures per schema (`tests/conformance.py`).
|
|
15
|
+
- [ ] Publish `@wasmagent/protocol@0.1.0` to npm and `wasmagent-protocol==0.1.0`
|
|
16
|
+
to PyPI; record both in the org release ledger.
|
|
17
|
+
- [ ] Strip local schema copies from `wasmagent-js` (`packages/compliance/schemas/`,
|
|
18
|
+
`packages/core/src/ranking/schemas/rollout-wire.schema.json`) and depend on
|
|
19
|
+
the npm package.
|
|
20
|
+
- [ ] Strip local schema copies from `trace-pipeline` (`schemas/*.schema.json`)
|
|
21
|
+
and depend on the pip package; rename `repair-trace-entry` usage to
|
|
22
|
+
`repair-trace`.
|
|
23
|
+
|
|
24
|
+
## Milestone 2 — AEP as the authoritative evidence contract
|
|
25
|
+
|
|
26
|
+
- [ ] Migrate `wasmagent-proxy` Rust `aep-core` types to generate from / validate
|
|
27
|
+
against `schemas/aep/aep-record.schema.json`.
|
|
28
|
+
- [ ] Point `wasmagent-train-replay` `EpochEvidenceBundle` at the shared AEP
|
|
29
|
+
record schema for its evidence envelope.
|
|
30
|
+
- [ ] Map `open-agent-audit` `schemas/v0.1/*` adapter onto the canonical AEP
|
|
31
|
+
record; document the version-skew adapter.
|
|
32
|
+
- [ ] Add a cross-repo compatibility CI check: fail if any consumer pins an
|
|
33
|
+
out-of-range protocol version.
|
|
34
|
+
|
|
35
|
+
## Milestone 3 — Stability & conformance
|
|
36
|
+
|
|
37
|
+
- [ ] Promote `aep-record` from `evolving` to `stable` with a documented
|
|
38
|
+
versioning guarantee (precondition for the planned `wasmagent-py` runtime).
|
|
39
|
+
- [ ] Provide a generated TypeScript type surface (`.d.ts` from schema) and
|
|
40
|
+
Python `TypedDict`s so consumers get types, not just validation.
|
|
41
|
+
- [ ] Add a conformance test suite consumers can run against their own emitters
|
|
42
|
+
(`aep-conformance` fixtures published in the package).
|