Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/15-milestones.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ bullets into issues. Each bullet is scoped to concrete files.
- [x] Point `wasmagent-train-replay` `EpochEvidenceBundle` at the shared AEP
record schema for its evidence envelope.
- [ ] In `open-agent-audit`, add an adapter mapping `schemas/v0.1/canonical-event.schema.json` onto `@wasmagent/protocol` `aep-record`, with a conformance test proving a sample AEP record validates. (tracked: WasmAgent/open-agent-audit#94)
- [ ] Add `scripts/check-consumer-versions.mjs` + a CI job here that reads each consumer repo's declared `@wasmagent/protocol` range and fails if any is out of the supported band.
- [ ] Add `scripts/check-consumer-versions.mjs` + a CI job here that reads each consumer repo's declared `@wasmagent/protocol` range and fails if any is out of the supported band. (tracked: WasmAgent/wasmagent-protocol#69)

## Milestone 3 — Stability & conformance

Expand Down
6 changes: 6 additions & 0 deletions docs/GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,12 @@ prevents the drift that motivated the repo's creation.
See [`CONTRACT-CHANGE-PROCESS.md`](CONTRACT-CHANGE-PROCESS.md) for the full
workflow.

## Version band mechanism

- All consumer repositories must pin or declare an acceptable version range within the supported `@wasmagent/protocol` version band.
- A cross-repo CI compatibility check (`scripts/check-consumer-versions.mjs`) verifies that consumer repos do not depend on out-of-band protocol versions.
- Protocol packages (`@wasmagent/protocol` on npm, `wasmagent-protocol` on PyPI) serve as the foundation contract across all WasmAgent ecosystem services.

## Exit condition

Per org policy, every repository declares what would cause it to be archived or
Expand Down
Loading