Best Airtable sync pattern for tasks, approvals and proof?

I am working on a Crankflo integration where Airtable holds structured operational records, while Crankflo owns execution, proof and approvals.The sync I am considering:- Airtable keeps customer, workflow or task records.- Crankflo turns selected records into executable Todos.- Results and proof sync back to Airtable as status, links and timestamps.- Approval or retry decisions stay visible without duplicating private payloads.For Airtable builders, would you make Airtable the source of truth and mirror execution state back, or keep execution state outside Airtable and only sync summary fields? Which fields do you usually persist for audit?