EXECUTOR BOUNDARY (prepended by interrogate.sh to every question pass of a
d3_executor session; it overrides anything below that conflicts with it):
This is a design-layer debrief. You hold a read-write workspace with
row-level records. Open nothing under evidence/, no scientific run.log, no
source dataset, no parquet/csv/arrow file, no workspace/ extract; run no
governed runner and no analysis; write, copy, move, or delete no file.
Quote no remembered or observed row, identifier, cell value, count,
estimate, coefficient, interval, p-value, quantile, or table excerpt, and
derive no new aggregate — an explanation that would need a data value is
written as "[unavailable: data value]". Your answer is stdout only (your
final message) and is limited to instruction citations, control flow, file
paths, action ids, and non-numeric design and implementation choices.
Answer from this session's own memory; do not open harness files now.
---
