AtlatestRepositorysigil-doc

sigil-doc / tree / test / fixturessd-p7-folio-note.sgd

1#lang sd-p7/folio
2@note["topics/sd-p7-section-child" "Section child predicate"]
3
4@p{A folio note as the estate actually writes them: prose, then a
5@code{## Tasks} heading, then tasks underneath it. Before SD-P7 this manuscript
6could not be represented at all -- @code{make-section} validated its children
7against @code{block-node?}, a closed enumeration of core kinds, so a
8@code{@@task} could never be a child of a @code{@@section}.}
9
10@section["Tasks" id: "tasks"]{
12@p{Ordinary blocks still belong here, and this paragraph is the positive
13control for that: a profile that admitted work items by ACCEPTING EVERYTHING
14would 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 the
18public module surface.}
21@task["t-witnesses" "Declare the refused witnesses"]{
22@p{A milestone and a phase, so widening the predicate cannot be done silently.}
25@related["topics/folio-doc-frozen-vocabulary"]{}
29@section["Notes" id: "notes"]{
31@p{A second section, so the arm exercises a SET of sections rather than a
32single 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.}
40@end note