Make internal asset policies executable before DB-scale import
Constraint: Internal type enums need a repeatable mapping path into manifest-ready buckets before bulk database exports begin Rejected: Leave type handling as documentation only | Would force repeated manual filtering and inconsistent ingestion decisions Confidence: high Scope-risk: narrow Directive: Keep internal asset mapping defaults conservative; conditional instrumental variants should stay opt-in until version-aware training is ready Tested: internal_asset_type_mapper.py on a 6-row sample CSV produced references=2 queries=2 metadata_only=1 excluded=1 with expected type routing Not-tested: Direct SQL export integration against the live source database
Showing
3 changed files
with
215 additions
and
0 deletions
-
Please register or sign in to post a comment