newspaper_wedding/.aidlc/sensors/aidlc-required-sections.md

id, kind, command, default_severity, fire_on, description, category, matches, input_schema, output_schema, timeout_seconds

id	kind	command	default_severity	fire_on	description	category	matches	input_schema	output_schema	timeout_seconds
required-sections	deterministic	aidlc engine sensor-required-sections	advisory	gate	Checks at the gate that stage output contains the required H2 headings	document-shape	**/{aidlc-docs,intents}/**	output_path stage_slug string string	pass h2_count headings findings_count edge_block template template_expected template_missing config_warning boolean integer string[] integer string string string[] string[] string	5

required-sections sensor

Default mode: checks the output contains at least 2 H2 headings (generic content-shape sanity check).

For unit-of-work-dependency.md (units-generation 2.7), additionally requires the fenced yaml units: edge block to be present, well-formed, and cycle-free — the machine-readable DAG the runtime compiler parses into the batch fan-out. The check reports edge_block as ok, absent, malformed, or cyclic; anything but ok fails the sensor at the gate so the malformed block never reaches the compiler. Every other artefact keeps the generic H2-count check only.

Heading-set overrides — two paths, with precedence

The default heading set can be overridden two ways. Precedence: a resolving templates/<artifact>.md wins over a ## Sensors-documented heading set.

1. Template-override layer (file-driven, preferred). A team drops aidlc/spaces/<space>/memory/templates/<artifact>.md (keyed by the output filename stem — artifact X writes to X.md). When one resolves for the output path, its ## headings become the expected set and the sensor passes iff expected ⊆ output; the missing headings are precise findings. Whole-doc, advisory — the human decides at the gate. The same file is the skeleton the agent fills (see the stage protocol § Template overrides), so the produced shape and the checked shape cannot drift. A template applies only to a template-eligible artifact (the stage's prose produces entries, threaded by the dispatcher); a template resolving for a questions/timestamp marker is ignored with a config warning, and the marker keeps the generic floor.

2. ## Sensors-prose override (in-stage, legacy anticipation). A stage's ## Sensors body may document a heading-set override (post-milestone-12 mechanism). This applies only when no template file resolves for the output.

The framework ships no per-stage ## Sensors overrides by default — teams introduce specific heading shapes either by authoring a template (path 1) or via the §13 learning loop when there's a real reason. When neither override is present, the output keeps the generic ≥2-H2 floor.

Failure mode

When required headings are missing, emits SENSOR_FAILED and writes detail to aidlc/spaces/<active-space>/intents/<active-intent>/.aidlc-sensors/<stage-slug>/required-sections-<fire-id>.md, where the space and intent come from the active cursors. The fire id is the 8-hex correlator from the SENSOR_FIRED row in the active record's audit/<host>-<clone-id>.md shard. The detail lists the missing headings.