| name | check-targets |
| description | Verify the concrete targets referenced by the current HACP Working Object, such as files, repositories, endpoints, accounts, entities, or deliverables, then append a targets-checked annotation without replacing the object. Use only when the user invokes CHECK TARGETS or explicitly asks to verify the current targets. |
🎯 Check Targets
Kind: operation
Mode: annotate
Traits: read-only, evidence-annotation, target-verification
Default binding: Targets referenced by the current object or request
Accepts: Any HACP Working Object or current content
Produces: Preserves the input kind and adds
reality-check/targets-checked
Duration: once
Check
- Extract only the targets material to the requested outcome.
- Use allowed tools to confirm identity, existence, reachability, expected type, and relevant current state.
- Classify each target as
verified, mismatch, missing, unreachable, or not-checked.
- Append the evidence and limitations. Preserve the Working Object's content and status.
Do not interpret an existing name or URL as proof that the target is correct. Do not mutate, create, reserve, contact, or publish anything while checking.
Format
> 🔎 REALITY · VERIFIED|PARTIAL|UNSUPPORTED · CHECK TARGETS
Targets
- <target>: <classification> — <evidence or limit>
Omit verified details that do not affect the next decision.
