Method / Evidence

Deployment Evidence Template

Connect a deployment claim to a system model, explicit invariant, controlled exploration, inspectable evidence, finding, remediation, and retest decision.

Evidence record

1. Decision and target

Name the system, release, environment, operating mode, owner, decision date, and scope exclusions.

Evidence record

2. Claim or invariant

State the property that must hold, why it matters, and the conditions under which it is expected to hold.

Evidence record

3. Authority and control path

Map the actors, identities, permissions, state, trust boundaries, commands, enforcement points, and possible physical effect.

Evidence record

4. Scenario and exploration

Record the baseline, controlled variation, expected observation, stop conditions, actual observation, and reproducible procedure.

Evidence record

5. Evidence level

Label design, configuration, simulation, runtime reachability, command acceptance, physical consequence, detection, stop, and recovery evidence separately.

Evidence record

6. Finding and boundary

Separate observed fact, inference, hypothesis, and missing evidence. State the impact boundary and what the evidence does not prove.

Evidence record

7. Remediation and retest

Tie the proposed enforcement change to the violated invariant and define the exact evidence needed to close the retest.

Evidence record

8. Decision statement

Supported / unsupported / unknown / blocked—followed by the evidence and remaining uncertainty that justify the status.

Minimum inspectable record

Keep enough provenance for another reviewer to follow the claim.

  • Stable record ID and target version
  • Owner, observer, timestamp, environment, and tool versions
  • Linked concept, interaction, flow, invariant, scenario, exploration, and finding IDs
  • Commands, logs, screenshots, hashes, or source locations needed for review
  • Evidence level and explicit unsupported-claim boundary
  • Remediation owner, status, and retest condition

Delivered through Attify

Apply the template to a humanoid or physical-AI deployment.

The Attify checklist turns this CFSE evidence structure into a concrete cross-layer review across firmware, ROS 2, cloud, autonomy, actuation, stop, and recovery.