ProgramBindings in compute and store_secret

[oceans404]

I want to understand * ProgramBindings * I noticed bindings (inputs, outputs, program id) are parameters in 2 places:

• as a parameter for compute
• as an optional parameter for store_secret

Compute takes in both [store_ids] and compute secrets at runtime. If compute is being used on stored secrets, the secrets have been stored ahead of time.
When/why would someone need/want to pass bindings to store_secret? Is the point of this to limit how a secret is allowed to be used? If bindings are set on store_secret with a specific program id, could that secret not be used to compute with other program ids?
If a stored secret is meant to be general purpose (used in future programs), would it be more likely that bindings is "None" or empty

Also if store_secret requires program bindings, I think the only possible flow is

1. store a program
2. create secrets and add bindings, binding the secret to the program
3. compute on the program with the secret

Can bindings be update?