- Data engineer
- Junior
- 22 min
A signed delivery liability
Birch Delivery recognizes only signed delivery rows. Build source_rows, accepted and liability assets. Filter status equal to signed in accepted, sum amount in liability, and preserve both declared dependencies. Negative signed adjustments remain eligible. Read hub_case.py for the supplied rows.
Skills and rubricAsset dependencies
- I pass source_rows into accepted and accepted into liability because the asset graph must describe the data the total uses. I retain signed negative adjustments and reconcile the sum to the eligible rows. File order does not establish a dependency.
- Complete the requested work and identify the source fact that makes it valid.
- I compare a signed negative adjustment with an unsigned positive delivery because filtering only positive amounts would overstate the liability. I also inspect the declared upstream keys rather than infer the graph from a correct total.