dsh-safety-brief-check

Boundary: this plugin checks one 安全技术交底记录 for what a record can be held to — that the columns your form requires are filled, that everyone briefed appears as having signed, that the briefing is dated no later than the work, that the briefed trades cover the trades doing the work, and that the record identifies its location and briefer. It does not judge whether the briefing content was adequate, whether it was targeted at the right hazards, or whether a signature is genuine.

⚠️ One error, and two annulled mandatory provisions the pack refuses to misuse

SB-002 is the only error-level rule, and it rests on an administrative regulation: 《建设工程安全生产管理条例》第二十七条 requires the briefing to be given "并由双方签字确认", with 第六十四条第（一）项 as its penalty. Everything else is capped at warn or info.

The pack records two corrections that a reader would otherwise get wrong:

1. JGJ 59-2011's clause 3.1.3 — this plugin's closest fit — is a recommendatory assessment clause. The standard's only mandatory provisions were 4.0.1 and 5.0.3, and both were annulled by 住房和城乡建设部公告 2022 年第 164 号 (effective 2023-06-01). So SB-006 (three-party signatures) is warn, and its note says why.

2. GB 50656-2011's clause 10.0.6 lost its mandatory status by the same公告, and its "班前安全操作规程交底" wording sits in the 条文说明, not in a clause. So this pack does not cite that standard at all — a test asserts the number never appears.

National law has no provision on pre-shift meetings. 《安全生产法》's 119 articles contain no occurrence of 班前; neither the law, an administrative regulation, a departmental rule nor a national standard addresses it. Provincial documents (Shandong's 班前"晨会" guidance, for instance) exist but are local, not national — so any pre-shift check ships unconfigured and the pack says so.

Stated limits: the signature check compares name lists only and cannot tell whether a signature is the person's own; the content check is a literal word-occurrence test and cannot tell whether a briefing was any good — JGJ 59-2011's own scoring table deducts points for "针对性不强", a judgement no string operation can make.

Compatibility

Surface	Status
Harness	Peer range >=0.1.2-rc.1 <0.2.0 || >=0.2.0-0 <0.3.0 — verified to accept both 0.2.0-rc.2 and 0.2.1-alpha.1. engines.dsh is deliberately not declared: it has no reader and cannot reject a host
Node	`^22.19.0
Platforms	All (plain ESM; no native code, no network, no model call)
Tool mode	Works in native, ptc and both; for a batch of records use ptc

What it does

Registers the safety_brief_check tool. It reads one record — its header fields, its recipient and signer lists, and its trade lists — applies a versioned rule pack, and returns a report.

Rule	Check	Severity	Basis
SB-001	the record fills the columns your form requires (off by default)	info	GB 50870-2013 8.2.3
SB-002	every recipient appears among the signers, and nobody signs twice	error	国务院令第393号 第二十七条
SB-003	the briefing date is not later than the work date	warn	第二十七条（推论）
SB-004	the briefed trades cover the trades doing the work	warn	JGJ 59-2011 3.1.3-3-2)
SB-005	the record names its location and its briefer	warn	GB 50870-2013 8.2.1
SB-006	the record carries a place for all three signatures	warn	JGJ 59-2011 3.1.3-3-4)
SB-007	the briefing text touches 危险 / 操作规程 / 应急	warn	GB 50870-2013 8.2.3

Install

dsh plugin --profile <name> add dsh-safety-brief-check
dsh --profile <name> --dump-config | grep 'dsh-safety-brief-check'

Configuration

Key	Type	Default	Description
rulesFile	string	rules/safety-brief-check.yaml	Rule-pack path, relative to the package root
disabledRules	string[]	[]	Rule ids to stop running; each appears in skipped
onlyRules	string[]	[]	Run only these rule ids; empty runs every rule
skipNotes	string	""	Note appended to every skipped reason
timeoutMs	number	120000	Cooperative tool timeout budget

Rule-level parameters worth knowing:

• SB-001 requiredFields — the columns the record must carry, e.g. [工程名称, 交底部位, 交底日期, 交底人, 被交底人]. Empty means the rule does not run.
• SB-004 requireTradeMatch — set to false to stop comparing the briefed trades with the work trades.
• SB-005 requireHeader — set to false if your record legitimately carries no header.
• SB-006 parties — the signature parties the standard names, [交底人, 被交底人, 专职安全员].
• SB-007 terms / contentColumns — the words the briefing text should touch, and the columns to read them from. Empty terms means the rule does not run.

Material format

The tool accepts JSON or YAML. One record is one flat mapping; name and trade lists may be an array or a delimited string:

工程名称: 某某厂房工程
交底部位: 二层结构
交底日期: 2026-03-10
施工日期: 2026-03-12
交底人: 张工
被交底人: 李四、王五、赵六
签字: 李四、王五、赵六
工种: 钢筋工、木工

被交底人: [李四, 王五]      # the array form also works
签字: 李四，王五；          # and Chinese punctuation splits the same way

Names are compared with whitespace removed, so 李 四 and 李四 are the same person. A missing signature and a repeated signature produce different findings, because they need different fixes. An unreadable date is reported as unreadable rather than skipped, so a badly formatted cell can never hide the chronology check.

Rule sources

Rule data lives in rules/safety-brief-check.yaml. Every rule carries a document, a document number, a clause in the source's own numbering, a verbatim excerpt and the URL the excerpt was read from. The loader enforces that an excerpt is a real quotation of at least eight characters, and that a check resting on a general principle or a local policy can never be declared error.

The clauses quoted come from:

• 《建设工程安全生产管理条例》 (国务院令第393号, in force 2004-02-01, unamended) — 第二十七条, 第六十四条第（一）项
• 《建筑施工安全检查标准》 (JGJ 59-2011) — 第3.1.3条第3款第2）3）4）项 and 附录B's scoring entry
• 《建筑施工安全技术统一规范》 (GB 50870-2013) — 第8.2.1条, 第8.2.3条, 第8.2.4条

Two corrections shaped this pack and are recorded in its header:

1. The industry standard's clause is recommendatory. JGJ 59-2011's mandatory provisions were 4.0.1 and 5.0.3, both annulled by 住建部公告 2022 年第 164 号; so rules citing 3.1.3 are warn.
2. GB 50656-2011 clause 10.0.6 lost its mandatory status by the same公告, and its pre-shift wording is in the 条文说明 rather than a clause — so the pack does not cite that standard at all.

The full clause-verification report, including the sources that were checked and rejected, is in rules/evidence/clause-verification.md.

Troubleshooting

• SB-001 reports itself as skipped. Its field list is empty. Fill in the columns your form uses.
• SB-004 reports nothing. Neither the material nor the call supplied a list of the trades doing the work. Pass workTrades, or accept that this comparison is not being made.
• SB-002 flags a name that did sign. The two columns may spell the name differently (a space, a different character). The comparison strips whitespace but is otherwise exact.
• SB-003 fires on a record that is correct. If the briefing followed the work — a hazard found mid-job — the pack's note says that is legitimate and should be explained in the record. The finding is a prompt to check, never a determination.
• The plugin installs but the tool never appears. Check that main resolves to lib/index.mjs and that pnpm run build produced it; a wrong main makes the loader skip the entry silently.
• dsh plugin add refuses the package as incompatible. The peer range covers 0.1.x and 0.2.x; if your runtime sits outside it, grant an explicit exemption: dsh plugin --profile <name> allow-version dsh-safety-brief-check@0.1.0 --dsh-version <runtime> --accept-risk
• check reports manifest-peers as failed. The static checker compares against a hard-coded peer range that predates the 0.2 line. The runtime enforces peer compatibility at install time, so the declared range is the correct one; this is a known upstream issue in dsh-plugin-dev.

Development

pnpm install
pnpm run typecheck   # tsc --noEmit
pnpm test            # vitest, paired fixtures per rule
pnpm run build       # tsdown -> lib/index.mjs + lib/index.d.mts
node ../scripts/sync-shared.mjs dsh-safety-brief-check   # refresh src/shared from ../_shared

License

Apache License 2.0 © 2026 dsh-safety-brief-check contributors.