Back to Details

k2f-legal-notice

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

K2F Legal Notice — AI-Native Aesthetic Design

K2F 法律通知 — AI 原生美学设计

Purpose

目的

Teach agents to blueprint legal notices before layout: notice type, recipient-facing obligations, scannable scope and systems blocks, and formal hierarchy—without inventing jurisdiction, custodians, scope, or privilege markings the user or counsel did not supply.
指导 Agent 在布局前为法律通知书制定蓝图：明确通知类型、面向接收方的义务、易于浏览的范围与系统区块，以及正式的层级体系——同时不得臆造用户或律师未提供的司法辖区、保管人、范围或保密特权标记。

Built on K2F

基于 K2F 构建

This skill produces legal notices as 
.K2F
packages. Follow the k2f skill for authoring: unpack or init a workspace, edit the semantic tree, run pack/verify, then export. K2F keeps agents on meaning (notice role, sections, emphasis)—not pixel coordinates—while the engine compiles layout, typography, and theme into consistent export-ready output.
Before you build, install the core skill: 
npx skills add suzheng/k2f --skill k2f
.
此 skill 会生成 
.K2F
软件包。遵循 k2f skill 进行创作：解包或初始化工作区，编辑语义树，运行 pack/verify，然后导出。K2F 让 Agent 专注于含义（通知角色、区块、强调方式），而不是像素坐标；同时由引擎将布局、排版和主题编译为一致且可直接导出的输出。
构建前，安装核心 skill：
npx skills add suzheng/k2f --skill k2f
。

When to Use

使用场景

  • First issuance of a litigation or preservation hold to named custodians.
  • Periodic reaffirmation (refresh) when scope, systems, or custodians changed.
  • Release when counsel confirms preservation may end.
  • Reformatting draft hold language into a consistent, institution-grade notice for attorney review.
  • 首次向指定保管人发出诉讼保全或证据保全通知。
  • 当范围、系统或保管人发生变化时，定期予以重申（刷新）。
  • 当律师确认可以结束保全时，解除通知。
  • 将草拟的保全通知文本重新格式化为统一、达到机构级质量的通知，供律师审阅。

Workflow

工作流

Step 1. Generate the content_and_design.md

第 1 步：生成 content_and_design.md

Single blueprint for semantic content and aesthetic intent. Label blocks the k2f skill can map to sections and emphasis later.
Sub-steps
  1. Notice frame — Classify issue, refresh, or release. State effective date, matter short name, issuing entity, and signer (from user or house style). For refresh, anchor to original issue date; for release, state end date and post-release retention instruction (user-sourced). Flag forum/jurisdiction only if user provided—do not invent preservation triggers or sanctions rules.
  2. Routing block — Date, To (custodian or role), From (authorized signer), Re line (
    LITIGATION HOLD NOTICE — [matter]
    or release equivalent). Record intended privilege / confidentiality marking as 
    USER OR COUNSEL TO CONFIRM
    —external custodian notices often differ from internal work-product headers.
  3. Why this recipient — One plain sentence: why they are on the notice (role, project, data access). Avoid prejudicial narrative, admissions, or strategy; enough context to understand relevance.
  4. Core obligation (hero) — Issue/refresh: effective immediately, preserve listed categories. Release: hold released as of [date]; normal retention resumes per stated instruction. This line is the visual and semantic anchor.
  5. Scope layer — Numbered bullets: document categories, subjects, counterparties, date ranges (preserve from [event] through present). Start specific; mark 
    COUNSEL VERIFY — breadth
    when scope is provisional. Refresh: call out adds, amends, or removals since last version.
  6. Systems & locations layer — Separate block listing channels (email, chat, drives, BYOD, paper, voicemail, calendars). Keeps scope about what and systems about where.
  7. Prohibited conduct — Short, imperative list (no delete, modify, destroy, auto-delete, inbox-zero). Issue/refresh only.
  8. Operational boundaries — Legal contact for questions; acknowledgment method and deadline (e.g., three business days); duration until written release; periodic reaffirmation if applicable. Clarify: business discussions may continue; do not discuss the notice, litigation, or legal strategy with colleagues unless directed.
  9. Safety line — “If unsure whether something is covered, preserve it” (issue/refresh).
  10. Signature block — Signer name, title, contact; match house template order.
  11. Design intent — Formal, custodian-grade clarity over ornament:
    • Tone: direct, authoritative, calm; no marketing or apology language.
    • Hierarchy: Re line and effective immediately strongest; numbered scope next; DO NOT visually distinct (weight or label, not shouty color); systems as secondary scan list; contact/acknowledgment in a closing band.
    • Density: moderate—short paragraphs, bullets for scope and systems; one screen-width idea per block; release notices may be a single dense paragraph plus retention line.
    • Palette: restrained neutrals, high body contrast, minimal accent on dates and deadlines; WCAG AA; no decorative graphics that compete with obligations.
Rules & constraints
  • Counsel gate: blueprint is for attorney review; distribution to custodians requires explicit user/counsel approval.
  • Scope gate: propose scope from user inputs; flag too-broad (operational burden) vs too-narrow (preservation gap)—never silently widen or narrow without marking 
    VERIFY
    .
  • Custodian gate: named individuals only from user/matter context; departed custodians on refresh → note IT-level preservation, not only individual notice.
  • Urgency gate: if suit served or imminent, state same-day issuance in blueprint; do not bury urgency in prose.
  • Honesty gate: no fabricated systems, custodians, legal citations, or acknowledgment URLs.
Common failure modes
  • Essay-style scope → re-layer into numbered bullets plus systems block.
  • Missing DO NOT / auto-delete → custodians assume normal deletion is fine.
  • Prejudicial or strategic detail in the opening → shorten to neutral one-liner.
  • Refresh without reaffirmation opener or scope delta → custodians cannot tell what changed.
  • Release without retention instruction → ambiguous whether archives stay frozen.
  • Wrong-side privilege banner on external notice → mark for counsel correction.
  • Acknowledgment buried with no deadline → compliance tracking fails.
Quality checklist
  • Notice type (issue / refresh / release) and effective dates are explicit.
  • Recipient rationale, scope, systems, and contacts are complete or marked TBD.
  • Prohibitions and preserve-if-unsure language present for issue/refresh.
  • Refresh notes scope/custodian changes; release states retention after hold.
  • Design intent names emphasis for Re line, core obligation, scope, DO NOT, and acknowledgment.
  • Counsel-review reminder included; no invented legal or operational facts.
用一份蓝图同时定义语义内容与美学意图。标记区块，以便 k2f skill 后续将其映射到章节与强调样式。
子步骤
  1. 通知框架 — 将通知分类为签发、刷新或解除。注明生效日期、案件简称、通知发出主体和签署人（依据用户提供的信息或机构风格）。对于刷新，关联原始签发日期；对于解除，注明结束日期和解除后的保留指示（来源于用户）。仅在用户提供信息时标注管辖法院或司法辖区——不得臆造保全触发条件或制裁规则。
  2. 路由区块 — 日期、收件人（保管人或角色）、发件人（授权签署人）、Re 行（
    诉讼保全通知 — [案件]
    或相应的解除版本）。将预期的保密特权/保密性标记记录为
    由用户或律师确认
    ——面向外部保管人的通知通常不同于内部工作成果页眉。
  3. 为何向此接收方发出通知 — 用一句直白的话说明其为何收到此通知（角色、项目或数据访问权限）。避免偏颇叙述、责任承认或诉讼策略；只提供足以理解通知相关性的背景。
  4. 核心义务（主视觉） — 签发/刷新：立即生效，须保留所列类别。解除：保全通知已于 [日期] 解除；按照既定指示恢复正常保留。本行是视觉与语义上的锚点。
  5. 范围层级 — 使用编号项目符号：文档类别、主题、对手方、日期范围（从 [事件] 至今均须保留）。应从具体内容开始；范围暂定时标记
    律师核验 — 广度
    。刷新时：明确列出相较上一版本新增、修改或删除的内容。
  6. 系统与位置层级 — 单独列出一个区块，列明渠道（电子邮件、聊天、云盘、BYOD、纸质材料、语音信箱、日历）。使范围对应“保留什么”，系统对应“在哪里保留”。
  7. 禁止行为 — 简短、命令式列表（不得删除、修改、销毁、自动删除或执行 inbox-zero）。仅用于签发/刷新。
  8. 操作边界 — 供答疑的法律联系人；确认方式与截止时间（例如三个工作日）；在书面解除前持续有效；如适用，说明将定期重申。并明确：正常业务讨论可以继续；除非另有指示，不得与同事讨论本通知、诉讼或法律策略。
  9. 安全提示语 — “如果不确定某项内容是否在保留范围内，请予以保留”（签发/刷新）。
  10. 签名区块 — 签署人姓名、职务、联系方式；顺序应与机构模板一致。
  11. 设计意图 — 优先保证正式、适合保管人阅读的清晰度，而非装饰：
    • 语气：直接、权威、冷静；不使用营销或道歉式语言。
    • 层级：Re 行和立即生效最为突出；其次是编号范围；DO NOT 应具有清晰的视觉区分度（通过字重或标签，而非刺眼的颜色）；系统作为次要扫描列表；联系人/确认信息置于底部收尾区。
    • 密度：适中——使用短段落和项目符号呈现范围与系统；每个区块只呈现一个屏幕宽度内的核心信息。解除通知可采用一个信息较密的段落，并附上保留指示。
    • 配色：采用克制的中性色，提高正文对比度，仅在日期和截止时间上使用少量强调色；达到 WCAG AA；不使用会与通知义务争夺注意力的装饰性图形。
规则与约束
  • 律师审核关卡：蓝图供律师审阅；向保管人分发前，必须获得用户或律师的明确批准。
  • 范围关卡：根据用户输入拟定范围；标记范围过宽（造成操作负担）或过窄（造成保全缺口）的情况——不得在未标记
    核验（VERIFY）
    的情况下擅自扩大或缩小范围。
    • 保管人关卡：指定个人只能来自用户或案件背景；刷新通知涉及离职保管人时，应注明需要 IT 层面的保全，而不能仅通知个人。
  • 紧急程度关卡：如果诉讼已被受理或即将受理，应在蓝图中注明当日签发；不得将紧急事项埋藏在正文中。
  • 诚实性关卡：不得捏造系统、保管人、法律引证或确认回执 URL。
常见失败模式
  • 散文式范围 → 重新组织为编号项目符号和系统区块。
  • 缺少 DO NOT / 自动删除禁令 → 保管人会误以为正常删除仍被允许。
  • 开头含有偏颇或策略性细节 → 精简为中性的一句话。
  • 刷新时没有重申开头或范围差异 → 保管人无法判断具体变更。
  • 解除时没有保留指示 → 无法确定归档内容是否仍被冻结。
  • 外部通知使用了不当的保密特权横幅 → 标记给律师更正。
  • 确认回执埋藏在正文中且未设置截止时间 → 导致合规跟踪失败。
质量检查清单
  • 明确注明通知类型（签发/刷新/解除）和生效日期。
  • 接收方依据、范围、系统和联系方式已完整填写或标记为 TBD。
  • 签发/刷新通知包含禁止行为和“存疑即保留”的提示语。
  • 刷新通知说明范围或保管人的变化；解除通知说明保全结束后的保留要求。
  • 设计意图明确 Re 行、核心义务、范围、DO NOT 和确认信息的强调方式。
  • 包含律师审阅提醒；未臆造任何法律或运营事实。

Step 2. Use the content_and_design.md and k2f skill to generate a K2F file and export to an appropriate file format.

第 2 步：使用 content_and_design.md 和 k2f skill 生成 K2F 文件，并导出为适当文件格式

Follow k2f to instantiate the notice from the blueprint, apply section roles from design intent, verify, and export the counsel-review deliverable.
遵循 k2f，根据蓝图实例化通知，应用设计意图中的区块角色，执行验证，并导出供律师审阅的交付物。