How we work

Engineering and handover

Connect the source records, configuration, evaluation and delivered tool. A result should remain understandable after the person who ran it has stepped away.

Delivery structure

Four connected records

Source
Input version, timestamps, rule references, rejected rows and coverage gaps, including what was available at the decision.
Configuration
Model parameters, transformations, game format, opponent assumptions, fee treatment and software versions.
Evaluation
Baseline, held-out period or population, net costs, uncertainty and sensitivity, with the test environment identified.
Delivery
The report, model, source code or tool, acceptance checks and operating notes.

Record failures as well as output

A parser that silently drops an unknown row can make data appear cleaner than it is. Using a price received after a decision leaks future information into a test. A changed rake schedule can invalidate an earlier comparison.

Schema changes, stale inputs, incomplete rows and failed validation need observable responses. For an execution tool, acceptance includes monitoring and stopping conditions before it goes into operation.

Inspect the synthetic source schema

Make the handover usable

The recipient needs to know how to run the delivered work, which inputs it accepts, where outputs are recorded and which changes require a new evaluation. Software ownership, maintenance and ongoing operation belong in the delivery terms.

For infrastructure, those responsibilities also cover the runtime, administrators, storage, logs and end-of-rental handling.