adobe / adobe/spectrum-design-data
RFC #715: platform-private experimental tokens policy
- Dominant language
- Rust
- Stars
- 153
- Forks
- 35
- Avg merge
- 7h 54m
- Merged PRs (30d)
- 111
Description
## Context
Open question from RFC #715 (Distributed Design Data Architecture), tracked in `docs/rfc-coordination.md`.
Define the policy for tokens that a platform repo marks as experimental or private — tokens that should not appear in the foundation's published surface. Covers: how experimental tokens are declared, whether they flow through the cascade, and what the upgrade / promotion path looks like.
## References
- RFC #715: https://github.com/adobe/spectrum-design-data/discussions/715
- `docs/rfc-coordination.md` RFC #715 row
Contributor guide
Research direction
Start with the RFC #715 discussion and the RFC #715 row in docs/rfc-coordination.md. Determine the policy for declaring experimental or private tokens, their behavior in the cascade, and their upgrade or promotion path. Done means these questions have a documented, agreed policy for platform repositories and the foundation’s published surface.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100