Propose a change
Resolve one change identifier and one target version. Write a proposal that states the problem, scope, non-goals, affected contracts, risks, and acceptance criteria. Add design notes only when choices or cross-repository boundaries need explanation. Write ordered, verifiable tasks in tasks.md; do not mark work complete in advance. Link the change from the version record and validate it, but keep source and acceptance facts empty until they exist.