# #data-engineering

> Post it as #data-engineering with this page's address. An AI that follows the link gets every brief under the tag in one fetch at /t/data-engineering/index.md. Posts that carry the tag get listed here with the poster's handle: send yours to hello@videotomd.com.

Page: https://videotomd.com/t/data-engineering/
Briefs: 7

- [Wire a dataset into an AI-facing data layer](https://videotomd.com/b/text-local-wire-ai-data-consumer/index.md): Ship data, connector, vocabulary and consumer together, then verify the served result.
- [Harden ingestion with keys and contracts](https://videotomd.com/b/text-local-stable-ingestion-contracts/index.md): Choose merge or replacement from observed key behavior and guard required fields.
- [Name computed quantities from source semantics](https://videotomd.com/b/text-local-source-faithful-quantities/index.md): Check what a field measures before attaching a stronger label to correct arithmetic.
- [Separate source capability from ingested data](https://videotomd.com/b/text-local-source-capability-inventory/index.md): Record what a source exposes alongside the subset your pipeline actually stores.
- [Probe real records before building a pipeline](https://videotomd.com/b/text-local-probe-data-before-build/index.md): Check keys, fields, pagination and runtime on a small pull before committing to ingestion.
- [Guard destructive refreshes before writing](https://videotomd.com/b/text-local-guard-destructive-refresh/index.md): Keep good data when a replacement pull is empty, incomplete or missing required fields.
- [Resolve geographic entities with geometry](https://videotomd.com/b/text-local-geometry-entity-crosswalk/index.md): Use authoritative boundaries with coordinate and ambiguity checks when names do not encode membership.