AtlatestRepositorysigil-doc
1
#lang sd-p7/folio2
@note["topics/sd-p7-section-child" "Section child predicate"]4
@p{A folio note as the estate actually writes them: prose, then a5
@code{## Tasks} heading, then tasks underneath it. Before SD-P7 this manuscript6
could not be represented at all -- @code{make-section} validated its children7
against @code{block-node?}, a closed enumeration of core kinds, so a8
@code{@@task} could never be a child of a @code{@@section}.}10
@section["Tasks" id: "tasks"]{12
@p{Ordinary blocks still belong here, and this paragraph is the positive13
control for that: a profile that admitted work items by ACCEPTING EVERYTHING14
would satisfy the task assertions below just as well.}16
@task["t-predicate" "Make the section-child predicate a profile parameter"]{17
@p{The predicate is carried by a content profile and consumed through the18
public module surface.}19
}21
@task["t-witnesses" "Declare the refused witnesses"]{22
@p{A milestone and a phase, so widening the predicate cannot be done silently.}23
}25
@related["topics/folio-doc-frozen-vocabulary"]{}27
}29
@section["Notes" id: "notes"]{31
@p{A second section, so the arm exercises a SET of sections rather than a32
single one, and so a bug that only ever populated the first would show.}34
@task["t-second-section" "Appear under a second section"]{35
@p{Same predicate, different section.}36
}38
}40
@end note