Planning normalizes records, resolves identity, validates the candidate set,
and binds its expected record heads to the active store and schema. It does
not persist records or batch metadata. Invalid input returns a plan whose
@valid property is FALSE and whose @issues table describes the failure.
Arguments
- store
An initialized
GraftStore.- records
A named list of concrete-class data frames.
- provenance
A
graft_provenance()object.