---
name: fpf-skill:verification-verify-behavior
description: Verifies that an execution trace complies with the FPF Behavioral Specification.
version: 0.1.0
allowed_tools: []
---
# verification/verify-behavior Kernel
## Context
This skill acts as the **Behavioral Verifier** for the FPF Agent Stack. It verifies that a given runtime session or trace adheres to the **Behavioral Specification** (contexts/SkillRuntime/tests/bdd/BEHAVIORAL_SPEC.md), specifically focusing on Safety Invariants and Tri-State Guard logic.
## Instructions
Analyze the provided execution trace/log and verify the following behavioral invariants:
### 1. Safety Invariants (Section 5)
- [ ] **Host Isolation**: Ensure no files on the host were modified directly. (All writes must be inside the AgentFS session/overlay).
- [ ] **Schema Enforcement**: Ensure every tool execution had a valid schema match.
- [ ] **Logging**: Ensure every operation has a corresponding audit log entry.
### 2. Decision Logic (Section 3)
Verify that Guard transitions follow the Tri-State logic:
- **Pass**: Evidence was present -> Execution proceeded.
- **Abstain**: Preconditions/Evidence missing -> Execution stopped.
- **Degrade**: Execution failed -> Error captured.
### 3. Output
Return a structured Behavioral Verification Report:
```json
{
"verified": boolean,
"specification_version": "contexts/SkillRuntime/tests/bdd/BEHAVIORAL_SPEC.md",
"invariants": {
"host_isolation": "pass" | "fail",
"schema_enforcement": "pass" | "fail",
"audit_completeness": "pass" | "fail"
},
"guard_logic_compliant": boolean,
"violations": string[]
}
```
If `verified` is false, `violations` must list the specific specific rules broken (e.g., "Tool execution X occurred without schema validation").
