jschoubben
418261213c
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…
mesh/delivery superseded: a newer head of the same pull request
ADR 0290 rule 9: once the import is checked record by record, hq keeps no copy. The records and efforts are removed; every link or path to them reads "ADR NNNN" or "research NNN"; a design's decisions: lists "ADR NNNN". 02-DECISIONS keeps a pointer README with the reading order's six topics, which the knowledge base reads through the records module; 01-RESEARCH keeps a pointer README. The checks drop the rules that judged records (the knowledge base holds each at propose; checks/README.md says where) and refuse a record written here again. Playbooks 01 and 02 and the skills write and read records with the knowledge base's verbs.
15 lines
776 B
Bash
15 lines
776 B
Bash
#!/bin/sh
|
|
# mesh-check-toolchain: go
|
|
#
|
|
# This repository's own check (ADR 0238): the second layer of a pull request's merge check,
|
|
# `mesh/repo-check`, run by the build seat in the mesh's Go toolchain, which carries Python for it. No
|
|
# module is built from here, so no gate runs (`mesh/merge-gate` says the change touches none). The four
|
|
# checks every merge here must pass (AGENTS.md): the documents' structure (and that no decision record or
|
|
# research effort is written here: they live in the knowledge base, ADR 0290), the reading order, the cycle,
|
|
# and the words (ADR 0244: no retired word in running prose, no word defined twice).
|
|
set -eu
|
|
python3 00-META/checks/records.py
|
|
python3 00-META/checks/index.py
|
|
python3 00-META/checks/cycle.py
|
|
python3 00-META/checks/words.py
|