Checklists to machine packs

Status: Product decision confirmed; skill and “open Compliance → prompt to install” shipped (2026-08-06); write target is “check schemes” (option B); platform check-scheme main path + questionnaire source switch + stock migrate shipped (2026-08-07). Pending: compliance-side independent validate/preview, Excel/Word experience polish.

Truth: User-visible requirements in docs/产品规格.md §3.2.2 / §3.2.3 / §3.2.4 / §4.2.4.

Voice: Use “internal-audit checklist”, “machine pack”, “check scheme”, “standards library”, “asset library”, “skill”, and similar language people understand; mindlink-compliance-pack, plugin_invoke, and similar are implementation mapping only.

Plugin SDK: skills shipped with a plugin: [../../sdk/platform-plugin/README.md](/docs/sdk-platform-plugin) §7.5.

Related:

• 检查方案.md (official home of machine packs; must cite standards)
• 规范库.md (article source of truth; this flow cites it, does not package practice as law)
• 资料库.md (where expert practice original tables live)
• 工作流与合规.md
• [../../sdk/platform-plugin/contracts/API.md](/docs/sdk-platform-api) §3.3 (RubricItem / load list)
• Sample: plugins/compliance/samples/iway6-internal-audit-g1.pack.md

---

1. Goal

Let a workspace turn practice checklists written by experienced specialists (Word / Excel / Markdown, and so on) into a machine-readable standard pack that compliance can use, hang it on a check scheme, cite standards-library articles, then pick it in a questionnaire and generate check items — without letting the practice table or machine pack replace official/customer standard bodies.

---

2. Split (must keep)

Forbidden:

• Using a practice machine pack to silently replace official article source of truth in the standards library.
• Building a machine pack as a standards-library entry that “looks like a law” and treating it as source of truth (old path repealed).
• Publishing a check scheme with no human confirm, or writing compliance check items into the business store directly.
• After enabling the compliance plugin, silently binding that skill to every agent (prompt, then install to the Skills center, and do not narrow-bind per agent).

---

3. User flow

Upload expert table to the asset library (or a conversation attachment)
  → Agent parses and maps to a machine-pack draft by skill
  → Compliance validate/preview check-item count and samples (pending)
  → Human confirm → write a “check scheme” draft (must cite standards)
  → Check scheme review and publish
  → Compliance “questionnaire” picks that published scheme (shows cited standards) → generate check items

Columns such as “review result / finding / remediation / recheck” belong to workflow execution and do not go into the machine pack.

---

4. Skills and plugins (implementation intent)

Machine-pack fields and load-list contract: ../../sdk/platform-plugin/contracts/API.md §3.3 and compliance mindlink.compliance.check_pack/v1.

---

5. Landing order

1. ~~Skill body + sample; opening Compliance prompts install to the Skills center.~~ (2026-08-06)
2. ~~Product decision corrected: machine packs go to check schemes; standards library keeps articles only.~~ (2026-08-07, see 检查方案.md)
3. ~~Check-scheme storage / API / admin page / plugin read-only.~~ (2026-08-07)
4. ~~Agent workspace_check_scheme_write / workspace_check_scheme_list.~~ (2026-08-07)
5. ~~Compliance questionnaires prefer “check schemes” (fall back to standards library when there is no scheme).~~ (2026-08-07)
6. ~~Stock practice entries leave the standards library (admin “Migrate from standards library”).~~ (2026-08-07)
7. Pending: compliance-side independent validate / preview pack.
8. One-click Excel/Word experience polish.

Note: Product language for “enable” = the workspace opens Compliance (not editing mindlink.json).

Transition: questionnaires may still fall back to machine entries in the standards library, and prompt migrate into check schemes; do not tell users that entry is official law.

---

6. Revision history