spec(bazaar): add Observational worked example for Compliance category#2
Closed
danielnorkin wants to merge 0 commit into
Conversation
chopmob-cloud
force-pushed
the
spec/bazaar-compliance-category
branch
from
10f7379 to
6261a1b
Compare
danielnorkin
force-pushed
the
add-observational-class
branch
from
1bb388a to
6261a1b
Compare
Author
|
@chopmob-cloud rebased onto your latest tip. One clean commit now adds the observational worked example (between the regulatory section and the Discovery Filter section), with the No other content changes on my side. Let me know if anything needs tightening. |
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.
Per the conversation on x402-foundation#2285 and x402-foundation#2322, adding the observational worked example to fill the third class in the Compliance category worked-examples section.
The new subsection lives between "Regulatory: Multi-framework compliance oracle" and "Compliance Category: Discovery Filter", matching the shape of the behavioral and regulatory blocks already in this PR.
Structure of the addition:
signedReceipt: false,anchor_chains == contributing_chains,determinism: aggregating)PaymentRequiredextension fragment (JSON)anchor_vs_contributing_constraint_checkoutput as the independent-auditability layer for the behavioralanchor_chains ⊆ contributing_chainsruleNo changes to existing content, no schema modifications. Purely additive.
Cross-references: