docs: record consumes/emits emptiness is expected ECCA-nascency (decision 65, closes #305) - #307
Merged
Conversation
…sion 65, closes #305) Traces the near-total emptiness of contract-level consumes/emits back to decision 56's already-shipped choice not to backfill them for already-published capabilities -- the real producer/consumer declaration mechanism is the ECCA events/ descriptor tree (spec 016), which today has exactly one governed event. No code or schema change needed.
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
#305found thatconsumes/emitsare empty ([]) on 114/116 publishedcontract.jsonversions, with all 116 having emptyconsumesand onlycore.transition-action-statusdeclaring a non-emptyemits. Investigated whether this is a data-quality gap worth backfilling/enforcing, or expected — traced it to decision-log entry 56 (#168, ECCA event-product publish path), which already answered this exact question when it shipped: it deliberately chose not to rewrite publishedemitsarrays in place, routing real producer/consumer declarations through the separate ECCAevents/descriptor tree (spec 016) instead. The registry has published exactly one governed event product to date, so near-total emptiness is the correct current state, not neglect.Changes
docs/decision-log.md: entry 65 records the finding, the trace back to decision 56, and why no backfill or new CI enforcement is warranted.No code, schema, or CI change — this is a documentation-only resolution.
Governing Spec
Project Item
Registry Project — issue #305
Definition of Done
Validation