K2F Legal Notice — AI-Native Aesthetic Design

Purpose

Built on K2F

.K2F

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. 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.

• 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.

• 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.

• 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.

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