Feat/webhook backfill redelivery - #134
Merged
Merged
Conversation
…onformance bars Three manifest fields tied EEP conformance to specific vendor ecosystems: - `reputation` is OPTIONAL in `eep-manifest.json`, but the runner called `fail()` when a manifest lacked `reputation.contract` — an ERC-8004 Ethereum registry. The conformance bar was stricter than the schema, and a publisher with no blockchain involvement could not reach Full conformance. - `pqc_ready` and `x402_enabled` were in the schema's `required` array, so every EEP manifest had to declare a payment-rail flag whether or not it had anything to do with payments. For a protocol positioning itself as neutral infrastructure and heading to a standards body, hard-wiring one chain and one payment rail into the conformance bar is a strategic liability rather than a bug. Changes: - `reputation` is reported, not required: present → pass with the contract, absent → skip with the reason. - `pqc_ready` and `x402_enabled` move out of the schema's `required` and gain `"default": false`. Relaxing `required` never invalidates a document that was already valid, so every deployed manifest keeps validating. A value that is present but not a boolean still fails. - §11.6 no longer says a non-PQC node "MUST set `pqc_ready: false` (not omit the field)". Omission and `false` are now equivalent, and neither affects conformance at any tier — PQC readiness is a capability a publisher advertises, not a bar it must clear. - IETF draft updated to match, which the parity gate added in the previous PR caught automatically. Refs: EEP audit 2026-08 finding A6 Signed-off-by: Ugur Cekmez <ucekmez@gmail.com>
fix(compliance-cli,schemas): stop making a chain and a payment rail conformance bars
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
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
Scope
Checklist
npm test/pytestin affected packages).Notes for reviewers