Accept HEP-7 Exchange layer, cut v1.1.0 — publish schema/v2/exchange.schema.json - #20
Merged
Conversation
…change.schema.json The Exchange layer's runtime prototype (ed25519/X25519 signing and verification, canonicalization, and the harness exchange keygen/offer/accept flow) has shipped in harness-kit, satisfying HEP-7's Accepted gate. The relay API remains unbuilt but is non-blocking per the HEP — clipboard/file transport already covers the zero-infrastructure MVP. Per GOVERNANCE.md's release process: schema/draft/ is snapshotted to schema/2026-07-27/ and the Exchange schema is published to website/public/schema/v2/exchange.schema.json (previously 404ing — the URL harness-kit's vendored copy has pointed at since 2026-06-06). This is a minor, backward-compatible bump (v1.0.0 -> v1.1.0): harness.yaml's version field and the v1 schema $id are unchanged. Registry (HEP-8) stays in Review pending its still-unstarted service prototype and is unaffected. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
packages/exchange+harness exchange keygen/offer/acceptCLI (ed25519/X25519 signing, verification, canonicalization, consent-first Preview/Accept/Edit/Reject/Apply flow). The relay API is not built, which the HEP itself treats as non-blocking (clipboard/file transport covers the zero-infrastructure MVP).harness.yamlfields added,versionstays"1", v1 schema$idfrozen).schema/draft/→schema/2026-07-27/and publisheswebsite/public/schema/v2/exchange.schema.json— this is the file that makeshttps://harnessprotocol.io/schema/v2/exchange.schema.json(and.ai) resolve. It's been 404ing since harness-kit vendored a copy on 2026-06-06 referencing that URL.Not included
v1.1.0git tag — per GOVERNANCE.md's release process this is created after this merges to main; happy to cut it as a follow-up.maintriggers the CI deploy to the liveharnessprotocol.io/.aicustom domains, so leaving that as an explicit decision after review here.Test plan
website/public/schema/v2/exchange.schema.jsonmatchesschema/draft/exchange.schema.json(verified identical locally via diff)https://harnessprotocol.io/schema/v2/exchange.schema.jsonand.airesolve post-deploy, and tagv1.1.0🤖 Generated with Claude Code