docs(adr): ADR-0082 — react-tier component contract governance#2490
Merged
Conversation
Records the model that the spec↔contract↔conformance↔prop-gate work converged on (now implemented + merged across framework #2478/#2480/#2482/#2484/#2485/#2488/ #2489 and objectui #2113/#2115), so future contributors don't re-litigate it: - the spec zod schema is the protocol source of truth; the AI-facing contract is GENERATED from it (zero-drift), never hand-authored; - registry inputs are the designer palette (a curated subset) — spec-only is a soft signal, frontend-only is the actionable one; - React-interaction props (callbacks/controlled/binding escape-hatches) live in a thin overlay, not the spec; declaring a genuine binding there is how a frontend-only prop is closed (baseline now 0 frontend-only); - conformance is a build-time baseline ratchet (build-console.sh, warn-only), not a per-PR gate — the manifest only exists at console-build time; - authoring correctness is a hard gate at os validate (missing-required = error, typo = warning); and the dogfood golden page proves the chain closes. Captures the alternatives rejected (copy props into spec / per-PR hard gate / hand-authored contract / registry-as-source). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
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.
What
A capstone ADR recording the governance model that the react-tier contract work converged on — now fully implemented and merged, but spread across many small PRs (framework #2478/#2480/#2482/#2484/#2485/#2488/#2489, objectui #2113/#2115) with no single document recording why it's built this way.
Why
Multiple prior memos flagged "架构结论(待 ADR)" — the design was deferred to a decision repeatedly. Now that the chain is real and closed, this ADR captures it so future contributors don't re-litigate: where the source of truth lives, why the registry is only a subset, why conformance is a ratchet and not a per-PR gate, and what each gate enforces.
The model (recorded)
react-blocks.md) is generated from it — zero-drift, never hand-authored.inputs= the designer palette (a subset). spec-only is a soft signal (panel gap); frontend-only is the actionable one (undocumented extension).build-console.sh, warn-only), not a per-PR gate — the manifest only exists at console-build time.os validate(missing-required → error, typo → warning).Plus the alternatives rejected (copy props into spec / per-PR hard gate / hand-authored contract / registry-as-source).
Docs-only; all cross-ADR links verified to resolve.
🤖 Generated with Claude Code