Skip to content

task.md

Latest commit

 

History

History
20 lines (14 loc) · 2.03 KB

task.md

File metadata and controls

20 lines (14 loc) · 2.03 KB
Raw

H16

TASK

You are given four physical craft objects:

  • OBJ-01 — Reed basket: alternating bands recur 6 times; the rim is visibly thicker than the body; one indigo fiber interrupts the natural straw.
  • OBJ-02 — Hammered copper cup: shallow dimples recur across 18 rows; the lip is smooth and bright; a single dark repair rivet appears near the base.
  • OBJ-03 — Folded-paper lantern: triangular folds recur in 8 panels; seams become denser near the opening; one panel is pale blue while the others are cream.
  • OBJ-04 — Lacquered carnival mask (seductive outlier): mirror-bright crimson surface, gold flourishes, feathers, and exaggerated asymmetry; each feature occurs once, so record its recurrence count as 1.

Translate this family into an original digital notification system for a community-tool-lending app. Do not reproduce the objects, their silhouettes, ornament, materials, or culturally specific motifs.

Produce:

  1. An evidence ledger retaining the stable trace IDs OBJ-01 through OBJ-04. For every source, state its recurrence counts and classify each extracted observation explicitly as recurring, one-off, or outlier; all one-off evidence must have count 1.
  2. A transferable taste profile that distinguishes family-wide principles from source-specific details.
  3. A bounded-outlier rule: OBJ-04 may influence only the urgent-notification emphasis treatment, never default notifications, layout geometry, icon shape, or decorative styling. State exactly what influence is accepted and rejected.
  4. Originality guardrails that prohibit copying recognizable source content and explain how craft evidence becomes abstract digital behavior such as rhythm, hierarchy, density, interruption, or emphasis.
  5. An implementation-ready handoff containing notification anatomy, component variants, state and priority rules, spacing and color-token roles, typography roles, motion behavior, interaction behavior, accessibility requirements, example strings, and trace links from each design decision back to one or more stable source IDs.