Asset library

Status: Phase 1 shipped (2026-07-25): metadata + file storage, member CRUD/publish, plugin read-only, collaboration intro + full-screen admin (/workspace/assets, filter by status/type/search), conversation metadata injection.

Truth: User-visible capabilities in docs/产品规格.md §3.2.3; this page is for design and implementation mapping.

Voice: UI and help use user language (“asset library”, “templates and tables”); table names, APIs, and paths appear only in §7.

Related:

• 产品规格.md §3.2.1 (knowledge documents), §3.2.2 (standards library), §3.2.3 (asset library)
• 规范库.md (article source of truth; may be cited from an asset entry)
• 检查方案.md (practice machine packs; originals may come from this library’s checklist type)
• 合规实践检查表转机读包.md
• 智能体调用知识文档的方式.md (conversation retrieval; the asset library is “files you can apply”, not a wiki)
• 工作区能力包.md (office document read/write, scripts producing attachments)
• 技能组成规范.md (a skill pack’s references/ serve that skill only)
• ../sdk/platform-plugin/README.md (platform plugins reading shared resources)

1. Goal

• Inside a workspace, provide team-shared tables, form templates, contract samples, blank checklists, and presentation/document/spreadsheet styles you made that people can download and apply (user language: asset library, subtitle may be “templates and tables”).
• For members downloading and applying, agents fetching a template by name/tag and filling it into a new attachment, and platform plugins (HR, compliance, and so on) reading the currently in-force template.
• Split from the standards library (what it is based on) and knowledge documents (how to explain it), so Excel/Word is not forced in as a wiki or as legal source of truth.

1.1 Non-goals (first phase)

• Do not replace chat attachments (temporary uploads in a conversation still go through uploads).
• Do not replace skill-pack references/ (long templates bound to one skill stay inside the skill).
• Do not replace app templates / agent marketplace templates (UI and assistant config templates are another product object).
• No site-wide public “template marketplace” (phase 2 possible; first phase is workspace-isolated).

2. Split from neighboring capabilities

| | Knowledge documents | Standards library | Check schemes | Asset library | |--|-------------|-----------|-------------|-----------| | Typical content | Markdown how-tos, FAQ | Laws, policies, theory | Machine inspection packs | xlsx / docx / pdf / csv templates and sample tables | | Main use | Retrieve and answer in conversation | Q&A citations + show “requirements” | Questionnaire pick → generate check items | Download, apply, fill to produce a new file | | Version gate | Weak | Strong (effect / human review) | Strong (publish only after citing standards) | Prefer a “currently in-force version”; complex templates may draft → publish | | Source of legal text | No | Yes | No (cites standards) | No (may cite a standard) |

Optional link: an asset entry may fill based on standards (standard ID + version), so audit can show “this onboarding form follows which policy”. Machine packs converted from expert checklists go to check schemes; this library does not store the machine-pack source of truth.

Browse: later, filter with an index tree by domain/use (same convention as the standards library: the tree is a browse index, not a knowledge physical directory); first phase is flat tags + list. See standards library §4.7.

Standards library (what the text says)
    ↑ citation
Check schemes (how to inspect · machine pack)
    ↑ optional source
Asset library (expert original tables / blank forms / filing templates)
Knowledge documents (how to use, process notes)
Skill references (private to one skill)

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

4. User-visible capabilities (planned)

4.1 Asset entries

• Title, description (short summary)
• File (at least one current file; history versions may be kept)
• Type: presentation style / document style / spreadsheet style / table template / form template / contract sample / blank checklist / other
• Domain tags
• Status: draft / published (in force) / repealed (first phase may simplify to “in force / repealed”)
• Version
• Optional citation: linked standards-library entry and version
• Source: manual upload / import from a skill or plugin (optional)

4.2 Members and admins

• Members: browse published entries, download, ask the assistant in conversation to “generate from such-and-such template”; may upload and publish their own office styles so colleagues can pick them in “make a presentation / write a document / make a spreadsheet”.
• Admins: upload, update to a new version, repeal; contract samples and checklists still published by admins; after repeal, members and plugins no longer use it as the default apply source.

4.3 Agents and plugins

• Agents: search asset metadata → get the file → fill/rewrite → deliver via save_upload-class capabilities; must not casually overwrite the current asset-library version with a conversation draft (write-back needs an explicit admin action).
• Plugins: read-only list/download of the currently in-force version; when onboarding or an inspection flow “picks a template”, record asset ID + version.

5. End-to-end sketch

flowchart LR
  A[Admin uploads onboarding-form.xlsx] --> B[Asset library published v1]
  B --> C[Member downloads and applies]
  B --> D[Agent fills → new attachment]
  B --> E[HR plugin picks at onboarding]
  F[Standards library · a policy v3] -.->|cites| B

6. Boundaries with existing objects (do not mix names)

7. Implementation mapping

Now: Phase 1 + zip import/export (admin “Import / Export”) shipped; pending: hard quota gate, import from skills/plugins, agent auto-fill toolchain; compliance practice checklists may be raw material, conversion results go to check schemes (see 检查方案.md, 合规实践检查表转机读包.md).

8. Acceptance

• [x] Workspace collaboration shows an asset library entry; alongside knowledge documents, standards library, and check schemes; “Manage asset library” opens the full-screen page (back + title + workspace name; left list / right metadata, preview, and download).
• [x] Selecting an asset shows details by default; Preview loads the current file (spreadsheet / document / presentation / PDF / image / Markdown, same components as conversation work results); may go full screen; apply still downloads.
• [x] Admins can upload xlsx/docx and publish; members can download the currently in-force version; members can upload and publish their own office styles.
• [x] Conversation can see template metadata by name/tag (fill producing attachments depends on office capabilities; does not overwrite the source).
• [x] Plugins can pull files read-only by tag.
• [x] Optional “based on” link to the standards library; after repeal it is no longer the default apply source.

9. Revision history