Pre-flight Answer, format v1 (final)

Status: final, version 1. Example: spec/xybern-formats-v1/vectors/preflight.json.

The answer to "may I do this plan": one result per step, decided by the real rules without recording a decision.

Key	Meaning
format	"xybern-preflight-answer-v1"
preflight_id, workspace_id, agent_id	Identity of the answer
charter_hash	The Charter version consulted
plan_hash	SHA-256 of the canonical plan
results[]	Per step: ref, action_type, outcome (allowed, needs_approval, refused), decision, reasons, mandates, judged_at_runtime, risk_dependent, requirements, obligations, collective_limits, what_it_would_take (kind bound / request / approval / obligations / runtime, detail, request template), request_template, lifted_by
summary	Counts per outcome and steps
recorded	Whether a pre-flight record was stored

what_it_would_take is the part an agent acts on: the bound to stay under, the authority request to file, the approver to wait for, or the obligations to satisfy.