Bulk Record Jobs

Overview

A bulk record job is any task shaped "many records in, one structured deliverable out": a gear catalogue, a crafting-graph, a conflict survey, a whole-mod audit, a compatibility-patch rebuild, a fan-out extraction returning JSON. The houseCARL tool surface has one primitive for every loop these jobs used to improvise — this skill maps job shapes to those primitives, carries the few game-level conventions the binary format doesn't (what a crafting-station keyword means, how a temper recipe differs structurally from a craft recipe), and defines the one canonical deliverable shape so ten agents extracting in parallel produce one schema, not ten.

Two costs dominate badly-planned bulk jobs, and both are locked in by the first call: per-record loops (a reverse lookup run 548 times instead of once; ~400 one-element list ops instead of ~40 batched ones) and schema drift (each extractor inventing its own output encoding). Plan the calls and fix the output shape before touching a record.

First step — size the job, then fix the shape