docs lockstep phase 1: check-lockstep.py, build wiring, WP4.1 audience/glossary #1

Merged
jsutter merged 4 commits from lockstep-phase-1 into main 2026-09-21 16:31:54 +00:00
Owner
No description provided.
Verbatim §1 from program/authoring-audience.md. The four frontmatter keys
land as documentation only — build validation arrives with the lockstep
KNOWN_KEYS gate (docs-lockstep phase 1, unit D).

Assisted-by: deepnet:synthetic/hf:zai-org/GLM-5.3-Flash
ORDER/CONCEPT/FRESHNESS/MESSAGE/DRIFT/DOCS-MANIFEST per docs-lockstep
R6-R11; surfaces come from a tool manifest or synthesize from captures.
12 self-contained fixture cases under tests/lockstep/ with run-all.sh.
DITDOCS_ROOT env redirects the root for fixtures; --validate checks any
manifest against the vendored schemas (jsonschema when present, built-in
mini-validator otherwise).

Assisted-by: deepnet:synthetic/hf:zai-org/GLM-5.3-Flash
KNOWN_KEYS rejects unknown frontmatter and validates doc_type/requires/
introduces/reader/verified (AUTHORING.md §5); gate order link → coverage →
prose → lockstep, lockstage emits docs-manifest.json per manual; the fleet
prose gate runs advisory until manuals.<m>.prose_gate: enforce. Coverage
gains the reverse direction (stale covers entries fail). Captures carry
# ditdocs-capture headers the build hash-verifies (hand edits fail);
capture-cli gains --stamp (header committed captures without re-walking
binaries that drifted past them) and --from-manifest (R4 renderer + mirror).

Assisted-by: deepnet:synthetic/hf:zai-org/GLM-5.3-Flash
All 128 capture files gain # ditdocs-capture <tool>@<version> sha256:<hash>
pinned to the committed VERSION.txt versions (ditc 2.4.4, dito 4.1.12-rc.1,
scribe 0.4.7) — the installed binaries have moved past these captures, so
the headers land via --stamp instead of a re-walk that would surface
uncovered groups (ditc 3.2.0 adds session/mcp, drops skills) ahead of the
content waves that cover them.

Assisted-by: deepnet:synthetic/hf:zai-org/GLM-5.3-Flash
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
deepnet/ditdocs!1
No description provided.