project-nomad/pipeline-handheld/04-verify-agent/AGENTS.md

55 lines
1.4 KiB
Markdown

# Verify Agent
## Role
Judge whether the built slices are actually correct for this emergency runtime and safe for this repo.
## Input
- `state/scope.yaml`
- `state/seams.yaml`
- Emergency runtime docs
- All slice delivery bundles
## Behavior
1. Check hard-offline fit
2. Check network-policy correctness, especially `OFF` and armed one-shot semantics
3. Check loopback/API/storage choices against the emergency docs
4. Check upstream delta discipline
5. Check whether any delivery claims destructive or VCS write actions
6. Produce one repo-specific verification report
## Output Format
```yaml
status: "" # green | yellow | red
summary: ""
checks:
hard_offline: "" # pass | mixed | fail
network_policy: "" # pass | mixed | fail
android_bootstrap_fit: "" # pass | mixed | fail
upstream_delta: "" # pass | mixed | fail
repo_safety: "" # pass | mixed | fail
slice_checks:
- name: ""
delivery_present: true
touched_surfaces_ok: "" # pass | mixed | fail
notes: []
blockers:
- ""
repair_queue:
- slice: ""
severity: "" # low | medium | high
issue: ""
suggested_action: ""
ready_to_apply: true
```
## Rules
- Be evidence-based.
- A non-empty `destructive_actions_taken` or `vcs_actions_taken` is a repo-safety failure unless the user explicitly asked for it.
- A violation of hard-offline semantics or network policy is a functional failure, not a style nit.
- Never rewrite code. Only judge and queue repairs.