docs: define template governance boundaries - #5915
Closed
cixzhang wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
PR Analysis Report
No new or modified components detected. Bundle Size SummaryNo component packages changed. Accessibility AuditStatus: No accessibility violations detected. Generated by PR Enrichment workflow | View full report |
cixzhang
force-pushed
the
docs/template-governance-20260902
branch
from
September 2, 2026 13:54
fd12eed to
3714b00
Compare
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.
Why
Template contributors need a short contract separating design intent, CLI implementation ownership, rubric evidence, and template-local behavior.
What
design:template-compositionowns five shared visual principles. It defines no universal anatomy, state, responsive, chrome, asset, or wizard-family contract.architecture:template-authoringrequires source, metadata, discovery, and registration to ship together; separates Design approval fromjosephfarina’s implementation/CLI approval; and preserves template-ID compatibility.#5797 and #5798 remain independent templates. Both records remain
authority: draft; no schema kind or Changeset is added.Validation
check:knowledgecheck:repo