AND Wayfind

A destination is visible, but the way there is still in fog. Wayfinding charts that uncertainty as a shared map, then resolves one investigation at a time until and-pack can publish the delivery unit.

Wayfinding plans; it does not deliver the destination. The pull to implement is usually evidence that the map has reached its handoff boundary.

Runtime Contracts

Before reading or writing workflow state, read .and/config.yml, invoke and-backend-contract, and use the configured backend reference for map, investigation, relationship, ownership, resolution, and lifecycle operations.

Invoke and-interview-contract whenever charting or resolving a human-in-the-loop (HITL) investigation requires an interview. It owns evidence, recovery, backend-safe domain modeling, and artifact-ready output. Before the selected path or investigation method begins, verify only what it invokes: charting and grilling require grilling plus the interview contract; prototype also requires prototype; research requires research; a HITL task requires grilling plus the interview contract, while an unattended (AFK) task requires only the skills named by that task or the map Notes. Stop with exact install guidance when a required skill is unavailable.

Map And Investigation

The map is a shared index, not a store or claim unit. Open investigations are queried through backend relationships rather than copied into its body. Its body is:

## Destination