The publish-time check between a parent document and the children it names (ADR-0008's amendment of 2026-09-22).

A compile of one document cannot see the child a core.subchart or a core.map names, and at runtime a disagreement between the two is not refused: a child outcome the parent routes on but the child no longer finishes with leaves the parent's conditioned arm dead, and the child's answer falls to the parent's unconditioned arm. The document graph is the host's, so the host is what walks it. This module ships the pairwise check the walk calls, over two StatifierBlocks.Compiled artifacts, in the two directions A2 names:

• check/2 - forward, when a parent is published: every child the parent names is resolved through the host's resolver and judged against the parent.
• consumers_broken/2 - reverse, when a child is republished: the next child artifact is judged against every parent the host says currently names it (A3).

Both read only StatifierBlocks.Compiled's interface field (A5). They hold no store, start no process and perform no IO; the resolver is the host's function and the only IO either direction touches.

The three checks

1. Every child the parent names resolves (A4). A resolver answering {:error, :not_published} is a finding on the referencing block's chart field.
2. Every outcome the parent routes on is declared by the child (A1, A2). A core.subchart routes on the outcomes its author listed, or on done when the author listed none. error is exempt: the parent routes on it whether or not the author listed it, and a child reports it without declaring it. Anchored on the block's outcomes field.
3. Every done-data key the parent reads is declared by the child (A1, A2). A core.map reads the members its collect_type marks required; a core.subchart reads none. Anchored on the block's collect_type field. Only presence is checked: whether a declared key has the type the parent expects stays StatifierBlocks.BlockType.agrees?/3's dormant advisory. A collect_type that is a type name the parent was compiled with no :datamodel to resolve has no keys to check: the reference records the name as unresolved, and the pair reports the read as unchecked rather than passing it (ADR-0008's second amendment of 2026-09-22).

The other direction of the outcome rule - a child outcome the parent has no arm for, such as one a child revision adds - is not refused here. It falls to the parent's unconditioned arm, and StatifierBlocks.ViewModel.outcome_findings/3 stays the editor's :warning about it.

The findings

Every finding is a StatifierBlocks.Finding with source :graph, anchored {:config, block_id, key} on the parent's referencing block, under the field its author would change. The anchor has no document arm, so consumers_broken/2 returns each finding paired with the parent's document id, and its message names that document.

Every finding is severity :error but one: a done-data read left unchecked because the parent's collect_type names a type and the parent was compiled without :datamodel is a :warning on the block's collect_type field. The host chose not to pass that option, which is not the author's error, so a publish step refusing on :error findings does not refuse on it; passing :datamodel, or writing the collect_type inline, lets the keys be checked.