Skip to content

docs: AEP/compliance schema definitions owned by wasmagent-protocol #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
telleroutlook merged 1 commit into from
Jul 23, 2026
Merged

docs: AEP/compliance schema definitions owned by wasmagent-protocol #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
**Allowed cross-repo patterns:**
- All security and policy primitives come from `@wasmagent/*` — never reimplement MCP firewall logic locally.
- AEP evidence bundles produced here are consumed by `open-agent-audit` via `@openagentaudit/adapters` (bscode adapter) — keep that adapter contract stable.
- Rollout wire records (`rollout-wire/v1`) and `ComplianceEvalRecord` are exported to `trace-pipeline` — pin schema version against `wasmagent-js` releases.
- Rollout wire records (`rollout-wire/v1`) and `ComplianceEvalRecord` are exported to `trace-pipeline` — pin schema version against `@wasmagent/protocol` releases (the canonical schema source).
- bench-v0 fixtures serve as Golden Path reference inputs; maintain at least one stable safe-call and one malicious-call fixture per bench release.

## Test Commands
Expand Down
Loading