Hosted execution records
Submit model-backed work and retrieve records, outputs and available artifacts. Shared hosted command verification is disabled by default.
DELIVERY & EVIDENCE
What you can use, and what the evidence means.
Hosted records, configured checks and research have different boundaries. Review the path that produced a result.
Configured repository checks
Applicability checks, realized diffs and command results require a separately configured execution path. A plan upgrade is not that configuration.
Environment and candidate failures
Classify environment failures where the available evidence supports it. Ambiguous or unclassified failures remain review items, not automatic evidence that a patch is safe.
Declared isolation
File access, mounts, network and process permissions are properties of the chosen execution environment. Record them; do not infer an absolute isolation guarantee from a product name.
Temporary workspaces and retained evidence
Workspace cleanup and evidence retention are separate. Logs, records and artifacts follow the documented configuration and retention policy.
Facts, rules and AI explanation
Execution logs, deterministic rule findings and AI-written explanations have different origins. An explanation cannot replace an unexecuted check.
No general correctness proof
A pass covers the recorded checks and environment. It does not guarantee another CI environment, untested behavior or semantic correctness. correctness_claim=false remains explicit.
Human review authority
Default hosted reporting does not automatically apply or merge repository changes. Any configured active gate requires separate evaluation and authorization.
Research is a separate evidence scope
Published experiments include their methods, misses and limits. They are not a guarantee of performance on customer repositories or a production promotion decision.
Example report · Research and limitations · Repository-validation PoC