What just happened

The same job exercised the whole Pilotage loop:

Stage	Harborview result
Manifest	The welcome card rode the initialize handshake; the agent was oriented before its first tool call.
Learn	The core guide taught the complete grammar skeleton.
Look up	The catalog supplied real device ids, actions, risk, and the snapshot token.
Validate	`unknown_device` located and repaired a typo without effects.
Plan	The proposed steps and their risk arrived with validation, visible before execution.
Gate	The Host paused on the destructive dock unlock.
Execute	The daytime flow ran against the pinned catalog.
Verify	The agent checked the trace against the work order, step by step.
Trace (inline door)	Each execute response carried its trace at the requested `trace_level`.
Trace (fetch door)	`trace_run` reopened retained runs later: one layer, two doors.
Store	`store: false` kept nothing, `store: true` kept everything, and absent, the declared `session` retention decided.
Deploy	The triggered alarm was installed instead of run once.
Demonstrate	The deterministic world fired the installed automation.
Recover	A stale catalog token refused safely and returned the Client to validation.

This is what a Pilotage-aware agent does. The path remains the agent's own; the server makes the path learnable and the result checkable.

Next, read the Proof to see three agents attempt this job without prior knowledge of buildingflow/1, or use the Reference for the formal rules.