Read the agreement.
Inspect the result.
What was required? What was permitted? What actually happened?
Make the scope explicit.
Permissions and approval
Name the systems, data, tools, and operations the executor may use. Require a human decision for specified actions.
Cost
Distinguish an estimated price from an authorized budget. Define what happens when further work would exceed that budget.
The host, credentials, and tool configuration must enforce the corresponding limits. Confirm storage, access and retention behavior before connecting institutional data.
Preserve the basis. Preserve uncertainty.
Identify the contract, observed sources, relevant changes, and actions behind the conclusion. Missing evidence, blocked work, and unmet requirements must remain visible.
A replay can establish consistency with a retained trace. It cannot, by itself, prove that the underlying judgment was correct.
Know what has been established.
Evaluate a specific release and execution environment before depending on a particular control. This site claims no certification or universal deployment configuration. The quant example is a design specimen; published research supports its stated findings, not every product capability.
Use of the hosted service is governed by the Terms of Service, Privacy Policy, and Acceptable Use Policy.