Generated from smart-base/L2/skills/smart-l2/dth-authoring.md — do not edit here.

✎ Edit this page’s source

dth-authoring

Skill id: dth-authoring · Package: authoring-who-smart-guidelines · Process: dth-authoring.bpmn (opt-in smart-base.L2-collab) (generated walk: dth-authoring.checklist.md (opt-in smart-base.L2-collab)). Pilot: litlfred/dth-hrh.

The diagram is the authority for the steps. This file holds only the rules that apply across them.

The stages, in one line each

stageends atwhat it is
0 · InitiateM0 · Charter recordedscope, DIIG phase, TWG, roles and RACI, repository from the dth-hrh layout, work plan seeded
1 · Ingest sourcesM1 · Library frozenevery source into library/ (WHO publications through who-iris), L1 coverage
2 · OutlineM2 · Outline agreedchapters against the dth kind, introduction, glossary candidates, list of processes, roles, decisions and indicators to model
3 · Structured draftingM3 · Zero draftcontent written as DAK-kind blocks, linked to smart-ra ArchiMate and SKOS
4 · Contributor feedbackM4 · Working-group drafteditors and contributors comment; change sets; issues
5 · Public commentM5, M6public draft released, comments dispositioned through change sets
6 · QA and publishM7 · Final publishededitorial, voice and translation QA, then publication

A milestone is recorded in the work plan when it is reached. It never blocks work in a later stage that is ready early.

Which review sheet, by stage

The sheet follows the stage the document is in.

stagesheettemplatemode in review-sheet-script
0-3 drafting and authoring, 4 contributor feedbackContributor sheet: one Contributor Feedback tab, each row a change set with its own issue; one Contributor Feedback (<initials>) column per person; no TWGs, no public-comment tabsFolio Assistant - Contributor Templatedrafting
5 public commentPublic Comment sheet: comment source, review of public comments, change sets with TWG and architect feedbackFolio Assistant - Public Comment Review Templatepublic-comment

How the sheets work, the template links, the generic Code.gs and its Config tab, and setup are in folio-assistant-core’s review-sheet-script skill; the Agent-tab rule is review-sheet-agent-columns. Do not set up the Public Comment sheet before stage 5.

Every DTH is written in the DAK kinds

Content that has a DAK kind goes in that kind’s block, never only in prose or a Markdown table:

contentDAK kind
user personas, roles, governance bodies as actorspersona, actor-definition
user scenarios, walkthroughsuser scenario
business processesbusiness-process (.bpmn, by bpmn-authoring)
decision tablesdecision-logic (.dmn, by dmn-authoring)
data elementscore data element
functional and non-functional requirementsrequirement
indicatorsprogram indicator

The fields of each kind are WHO’s DAK logical-model fields, and the dth document kind admits these blocks. Planning kinds that are not DAK kinds (planning step, RACI, risk register, barrier-to-solution map, stakeholder analysis, form inventory) have no schema until the architect group and the handbook owners have reviewed them.

Terms

  • Terms come from the source’s own glossary first. See folio-assistant-core’s glossary-terms skill (“Source glossary first”).
  • Deprecating a term is a change set, decided later by an editor. The agent records the old term, the new term, the reason and every place the old term appears (e.g. “CDE-HRH” replacing “MDS-HRH”), and changes nothing in the text. The text changes only after an editor-started agent review decides the change set. Quoted source text always stays as published.

A new DTH from an existing WHO publication

When the DTH already exists as an L1 publication, stages 0-2 are done by dth-l1-to-l2-ingest, which writes the handbook’s workplan first.

Processes that run this skill

This skill has its own process: DTH authoring.

BPMN diagram: DTH authoring


folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev