Governance ownership

An application description explains the work. A governance control sets the requirement applied to it. Check which one needs to change before editing either.

Developer-provided context

Developers describe the application in plain language:

• Business context explains what the application does and why.
• Good outcomes explain what a successful session looks like.
• Risk concerns explain the harms the team wants to prevent.

Use this context to choose the organization policies and application controls the workflow needs.

To require supporting sources, add a policy rule as well as describing the expected response under Good outcomes.

Governance controls

Authorized governance roles maintain the settings that determine how VeriProof reviews application activity. Organization settings apply broadly; application settings apply to one application.

When the interface shows Set by, use it to identify the source of the current value. It identifies the setting’s source, not necessarily the person who last edited it. Review the source setting before deciding who should make the change.

Make a change in the right place

1. Open the application setting or control you want to understand.
2. Check Set by and the current value.
3. Confirm who owns that source and who the change will affect.
4. Update the owning organization or application setting.
5. Review the resulting policy or application status before you finish.

If the developer-provided context is inaccurate, update the context itself. If the policy behavior is wrong, ask an authorized governance owner to change the control instead of changing the application description to force a result.