See one example
In the checked NGINX example, development changed spec.replicas from three to four. Staging stayed at three until that exact change was promoted. The staging namespace remained unchanged.
The receipt records the base, development, and staging revisions instead of asking someone to reconstruct the change from copied values files.
Check the record
Open the development-to-staging promotion receipt. Its limits say that this is one field promotion; rollback and fleet rollout are separate checks.
Do this next
Follow the ConfigHub tutorial to create a development configuration, make one change, and promote it to production.