Check schemes

Status: Product decision confirmed (2026-08-07, option B); platform main path shipped (storage / admin page / plugin read-only / agent draft write / questionnaire source switch / stock migrate); Q&A injection boundary still in the acceptance list.

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

Voice: UI and help use “check scheme”, “based on standards”, “published”, and similar user language; table names, APIs, and paths appear only in §7.

Related:

• 产品规格.md §3.2.2 standards library, §3.2.3 asset library, §3.2.4 check schemes, §4.2.4 compliance
• 规范库.md (article source of truth; this capability cites it, does not replace it)
• 资料库.md (expert original tables, blank checklists)
• 合规实践检查表转机读包.md (expert table → machine pack → this capability)
• 工作流与合规.md

---

1. Goal

• Inside a workspace, provide check schemes alongside the standards library and asset library: store machine-readable inspection packs after experts operationalize laws/policies (user language; implementation includes mindlink-compliance-pack and similar).
• Let compliance questionnaires pick a scheme and generate check items; later this can extend to HR “standard pack” machine content (first phase is compliance-first).
• Must name which published standards-library entries it is based on; must not treat a check scheme as the legal text itself.

1.1 Non-goals

• Do not replace the standards library as article source of truth; do not replace Excel/Word originals in the asset library.
• Do not inject check-scheme bodies into agent Q&A by default as “what the law says”.
• First phase has no site-wide public “scheme marketplace” (workspace isolation).

---

2. Split from neighboring capabilities

| | Standards library | Check schemes | Asset library | Knowledge documents | |--|-----------|-------------|-----------|-------------| | In one sentence | What you must follow | How experts suggest you inspect | Originals and blank forms | How to use, FAQ | | Typical content | Law / policy / theory body | Machine inspection pack Markdown | xlsx/docx checklist originals | Wiki | | Effect | Source of truth | Operationalized (must cite the source) | Raw material / apply | Explanation | | Drives check items | No (citation display only) | Yes (questionnaire pick) | No | No | | Q&A injection | Published articles | Default not injected as law | Metadata optional | Yes |

Standards library (what the text says)
    ↑ required citation
Check schemes (how to inspect · machine pack)
    ↑ optional source
Asset library (expert original tables / blank forms)

---

3. Product decisions (confirmed, 2026-08-07)

Forbidden:

• Silently replacing standards-library articles with a check scheme.
• Publishing a scheme with no human confirm, or writing compliance check items into the business store directly.
• Questionnaire UI that only says “against the law” without showing cited standards.
• Writing a check scheme into knowledge documents or standards-library bodies as if it were legal source of truth.

---

4. User-visible capabilities

4.1 Scheme entries

• Title, short description
• Machine body (Markdown; includes compliance machine fences and similar)
• Domain tags (e.g. compliance)
• Based on standards (required, may be several: standard ID + version; at publish, targets must still be published and not repealed)
• Optional source asset (asset-library entry ID + version)
• Status, version, creator, times

4.2 Members and admins

• Members: browse published schemes; may create/edit their own drafts (or by workspace policy).
• Admins: review publish, repeal, handle others’ drafts; import / export archives.

4.3 Agents and plugins

• Agents: after skill conversion, call the write tool to land a draft; then guide the user to “Manage check schemes” to publish.
• Compliance plugin: list/read published schemes → questionnaire pick → preview generated check items → after human confirm, write the business store.

---

5. End-to-end flow

Path A (practice table):
Upload expert checklist to the asset library (optional cited standards)
  → Agent parses into a machine pack by skill
  → Human confirm → write a “check scheme” draft (with cited standards)

Path B (coarse split from a standard):
Published standards-library article → workspace_standard_get reads the body
  → Coarse-split a machine pack by clause (must mark human-filled evidence/scoring)
  → Human confirm → write a “check scheme” draft (based_on_standards points at that standard)

Shared next steps:
  → Admin publishes the check scheme
  → Compliance “questionnaire” picks that scheme (shows cited standards)
  → Generate check items (record scheme version + standard version)

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

---

6. Relation to the old decision

• 2026-08-06 had said: machine packs go into the standards library (same entry or a separate practice entry).
• 2026-08-07 corrected to option B: machine packs go into check schemes; the standards library keeps article source of truth only.
• Transition: questionnaires may still fall back to machine entries in the standards library, and prompt migrate into check schemes; product copy and skills follow this page.

---

7. Implementation mapping (shipped)

Machine-pack field contract remains in ../../sdk/platform-plugin/contracts/API.md §3.3 and compliance mindlink.compliance.check_pack/v1.

---

8. Acceptance

• [x] Cannot publish a check scheme with no “based on standards”.
• [x] Practice entries in the standards library that contain a machine pack can migrate into check schemes (then repeal/delete the original).
• [ ] Q&A injection does not impersonate articles with check-scheme bodies (system prompt already guides; retrieval injection boundary still to strengthen).
• [x] Questionnaires prefer a scheme and show cited standards; parsing the body prefers the check scheme.
• [x] Agent writes drafts only; must confirm; no auto-publish.
• [x] Stock practice packs migrate from the standards library into check schemes (admin confirms by hand).
• [x] Admins can import/export check-scheme archives (incremental; published not overwritten).

---

9. Revision history