Skip to content

output.md

Latest commit

 

History

History
332 lines (246 loc) · 21.8 KB

output.md

File metadata and controls

332 lines (246 loc) · 21.8 KB
Raw

Taste profile and notification-system handoff — H16

Source and access

  • Sources: OBJ-01 through OBJ-04
  • Source medium: Physical craft objects, represented by structured written observations
  • Downstream target: Digital notifications for a community tool-lending app
  • Access status: Provisional. The supplied descriptions support analysis of repetition, hierarchy, density, interruption, finish, and emphasis.
  • Unavailable: Direct object inspection, scale, full form, construction, tactility, wear, affordance, additional views, and use states. No claims are made about those axes.

Accessibility, correctness, and operational clarity outrank extracted style and fidelity throughout this contract.

1. Evidence ledger

Counts describe cited occurrences or explicitly identified recurring units. Exclusion or design weight is recorded separately; it never changes a count to zero.

Trace ID Source coordinate Extracted observation Recurrence count Classification Transfer weight
OBJ-01 Body Alternating bands recur 6 bands/cycles recurring Family evidence for rhythm
OBJ-01 Rim relative to body Rim is visibly thicker 1 one-off Family evidence for threshold hierarchy
OBJ-01 Body fiber field One indigo fiber interrupts natural straw 1 one-off Family evidence for controlled interruption
OBJ-02 Cup body Shallow dimples recur across rows 18 rows recurring Family evidence for rhythm and restrained texture
OBJ-02 Lip relative to body Lip is smooth and bright 1 one-off Family evidence for threshold hierarchy
OBJ-02 Near base One dark repair rivet interrupts the surface 1 one-off Family evidence for meaningful interruption
OBJ-03 Lantern body Triangular folds recur in panels 8 panels recurring Family evidence for rhythm
OBJ-03 Near opening Seams become denser near the opening 1 density transition one-off Family evidence for increased hierarchy near an active threshold
OBJ-03 Panel field One panel is pale blue; the rest are cream 1 one-off Family evidence for controlled interruption
OBJ-04 Surface Mirror-bright crimson finish 1 outlier Urgent emphasis only
OBJ-04 Surface ornament Gold flourishes 1 outlier Rejected from transfer
OBJ-04 Added ornament Feathers 1 outlier Rejected from transfer
OBJ-04 Overall arrangement Exaggerated asymmetry 1 outlier Rejected from transfer

Per-source count summaries:

  • OBJ-01: 6, 1, 1
  • OBJ-02: 18, 1, 1
  • OBJ-03: 8, 1, 1
  • OBJ-04: 1, 1, 1, 1

2. Transferable taste profile

Taste thesis

A measured recurring structure establishes calm and trust, important thresholds receive restrained reinforcement, and one meaningful interruption carries the signal. [TP-01, TP-02, TP-03]

Taste trace

Principle Source evidence Observation Inferred principle Recurrence weight Confidence Downstream consequence
TP-01 — Measured rhythm OBJ-01: 6 alternating bands; OBJ-02: dimples across 18 rows; OBJ-03: folds across 8 panels Each core source organizes many small units into a legible cadence Repetition should create order without becoming ornament 3 of 3 core sources; recurring units 6, 18, and 8 High Use consistent anatomy, spacing, stacking, and repeated metadata placement
TP-02 — Reinforced threshold OBJ-01: thicker rim; OBJ-02: smooth bright lip; OBJ-03: denser seams near opening Each core source differentiates an edge, opening, or transition from its main field Attention should increase near boundaries where state or action changes 3 of 3 core sources; one threshold observation per source High Strengthen titles, action regions, unread boundaries, and state transitions without changing the whole component
TP-03 — Singular interruption OBJ-01: one indigo fiber; OBJ-02: one dark rivet; OBJ-03: one pale-blue panel A largely regular field contains one conspicuous exception One isolated signal is more effective than many competing accents 3 of 3 core sources; one interruption per source High Permit one primary status accent or action emphasis per notification; suppress competing highlights

OBJ-04 does not establish a family principle because it is a single seductive outlier.

Family-wide principles versus source-specific details

Layer Retained meaning
Family-wide Measured recurrence (TP-01), threshold hierarchy (TP-02), and singular interruption (TP-03) are supported independently by OBJ-01, OBJ-02, and OBJ-03.
Source-specific Six bands, 18 rows, eight panels, a thick rim, bright lip, dense seams, particular colors, a repair rivet, and individual material effects are evidence coordinates—not reusable specifications.
Bounded outlier OBJ-04 contributes only a tightly constrained increase in urgent-notification emphasis. It does not join the default family language.

Signature principles

  1. Keep component rhythm regular and predictable. [TP-01; OBJ-01, OBJ-02, OBJ-03]
  2. Increase hierarchy where the user crosses a state or action boundary. [TP-02; OBJ-01, OBJ-02, OBJ-03]
  3. Give each notification one dominant signal. [TP-03; OBJ-01, OBJ-02, OBJ-03]
  4. Let recurring structure carry character; do not add decorative craft references. [TP-01, TP-03]

Productive tensions

  • Rhythmic, not mechanically busy. [TP-01]
  • Emphasized at the boundary, not heavy everywhere. [TP-02]
  • Distinctive, not multicolored. [TP-03]
  • Dense near action, not cramped. [TP-02]
  • Crafted in pacing, not costumed in appearance. [TP-01, TP-03]

Invariants

  • The same anatomy and spacing rhythm must remain recognizable across surfaces. [TP-01]
  • Each notification has at most one dominant accent. [TP-03]
  • Actions and state changes receive stronger hierarchy than passive metadata. [TP-02]
  • OBJ-04 never influences default notifications, layout geometry, icon shape, or decorative styling.
  • Errors, identity, consent, fees, security, permissions, recalls, and risk statements remain literal and unambiguous.
  • Accessibility, correctness, and operational clarity override all stylistic rules.

Degrees of freedom

The implementer may choose the typeface, exact neutral palette, responsive breakpoint, container width, semantic icon library, border radius, and delivery surface, provided the invariants and accessibility requirements remain intact. No exact physical measurements or source colors are implied.

3. Bounded-outlier rule

Accepted influence

OBJ-04 may influence only the emphasis amplitude of a genuinely urgent notification:

  • Increase the contrast and saturation of the app’s existing semantic critical token.
  • Apply that token to the existing status indicator and urgent label.
  • On arrival, permit one restrained, non-geometric intensity pulse.

This translates the outlier’s conspicuousness into urgency without transferring its appearance.

Rejected influence

The following are prohibited:

  • Using OBJ-04 in routine, success, informational, reminder, or ordinary action-required notifications.
  • Copying crimson, gold, gloss, mirror effects, flourishes, feathers, carnival references, or mask imagery.
  • Introducing asymmetrical layout, irregular alignment, a special silhouette, or a new icon shape.
  • Adding gradients, metallic effects, ornamental borders, particles, decorative animation, or repeating pulses.
  • Increasing the number of accents or actions.

Executable check

If the urgent treatment were reduced to the normal semantic palette and its single pulse removed, would its geometry, icon, typography, spacing, and decoration match the corresponding default component?

The answer must be yes.

4. Transfer and originality guardrails

Principle Source manifestation Abstract digital behavior Literal copy to avoid
TP-01 Bands, dimple rows, folded panels Consistent spacing intervals, repeated anatomy, orderly stack cadence Weaving, dimples, folds, panels, or patterned backgrounds
TP-02 Reinforced rim, differentiated lip, denser opening Stronger title/action hierarchy and clearer state-transition boundaries Rim-like borders, vessel openings, seam graphics, material shine
TP-03 One different fiber, rivet, or panel One status accent, unread marker, or primary action Indigo fiber, repair-rivet imagery, isolated colored “panel”
Bounded outlier Conspicuous one-time finish and asymmetry Higher urgent contrast plus one intensity pulse Crimson-and-gold styling, gloss, feathers, masks, asymmetry

Additional guardrails:

  • Do not reproduce any object, silhouette, material, joinery, ornament, culturally specific motif, or recognizable composition.
  • Do not use texture overlays that simulate straw, hammered metal, folded paper, lacquer, or feathers.
  • Do not encode the literal source counts 6, 18, or 8 into grids, animation loops, or notification quantities.
  • The repair rivet supports “meaningful interruption”; it does not authorize faux damage, repair imagery, or distressed styling.
  • A reviewer should be able to explain the design through rhythm, hierarchy, density, interruption, and emphasis without naming any physical object.

5. Implementation-ready handoff

All numeric values below are original target-medium specifications, not measurements extracted from the sources.

Notification anatomy

Slot Implementation rule Trace
Container Use one consistent shell across toast, inline, inbox, and banner surfaces TP-01; OBJ-01, OBJ-02, OBJ-03
Status One semantic status indicator; reuse the app’s established icon set TP-03; OBJ-01, OBJ-02, OBJ-03
Label Optional short category or priority label above the title; urgent label must say Urgent TP-02; OBJ-01, OBJ-02, OBJ-03; urgent amplitude bounded by OBJ-04
Title One line preferred; states the event or required outcome TP-02; OBJ-01, OBJ-02, OBJ-03
Body One to three short lines explaining object, time, place, or consequence TP-01; OBJ-01, OBJ-02, OBJ-03
Metadata Secondary row for due time, branch, reservation ID, or lender TP-01; OBJ-01, OBJ-02, OBJ-03
Actions One primary action; at most one secondary action TP-03; OBJ-01, OBJ-02, OBJ-03
Dismiss Separate accessible control when dismissal is allowed TP-02; core sources support boundary clarity; behavior is a target requirement
Live-region text Semantic message must remain complete without color, motion, or icon recognition Core hierarchy trace: OBJ-01, OBJ-02, OBJ-03; accessibility override

Component variants

Variant Use Treatment Trace
routine Availability, pickup confirmation, return confirmation Neutral shell; one restrained semantic status accent TP-01, TP-03; OBJ-01, OBJ-02, OBJ-03
action-required Due soon, reservation expiring, approval needed Same shell; stronger title and action-region hierarchy TP-02; OBJ-01, OBJ-02, OBJ-03
success Completed checkout, return accepted Same shell; semantic success token only on status and primary feedback TP-03; OBJ-01, OBJ-02, OBJ-03
error Failed booking, permission problem, identity or payment issue Persistent, literal explanation and recovery action TP-02; core-source hierarchy plus target correctness override
urgent Immediate safety recall or time-critical operational risk Same geometry as action-required; critical token has higher contrast and one arrival pulse Family shell: OBJ-01, OBJ-02, OBJ-03; emphasis amplitude only: OBJ-04

Priority rules

  1. Urgent: Use only for immediate safety or operational risk. Persistent until acknowledged or resolved; may use assertive announcement. [OBJ-04 only for emphasis; TP-02 for clarity]
  2. Action required: A user action has a deadline or blocks a lending workflow. Persistent in the notification center; polite announcement. [TP-02; core sources]
  3. Routine: Informational or completed state. May appear as a transient toast and remain in notification history. [TP-01; core sources]

Priority is determined by consequence and time sensitivity, never by desired visual drama.

State rules

State Behavior Trace
unread Show one unread/status accent; do not additionally highlight title, border, and background TP-03; OBJ-01, OBJ-02, OBJ-03
read Remove unread emphasis while retaining semantic text and icon TP-03; core sources
actioning Disable the submitted action, preserve label width, and show textual progress TP-01, TP-02; core sources
resolved Replace request language with explicit completion status; remove obsolete actions TP-02; core sources
error Keep visible until recovery or explicit dismissal; state what failed and what to do TP-02; core sources plus correctness override
dismissed Remove from transient surface; retain in history when auditability matters TP-02; core sources plus operational requirement
offline State that the action is queued or unavailable; never imply success prematurely Core-source clarity trace: OBJ-01, OBJ-02, OBJ-03; correctness override

Spacing and geometry tokens

Use a base rhythm of:

  • space-1: 4px
  • space-2: 8px
  • space-3: 12px
  • space-4: 16px
  • space-6: 24px

Rules:

  • Container padding: 16px.
  • Status-to-content gap: 12px.
  • Title-to-body gap: 4px.
  • Body-to-metadata gap: 8px.
  • Content-to-actions gap: 12px.
  • Action gap: 8px.
  • Stacked-notification gap: 8px.
  • Minimum interactive target: 44 × 44px.
  • Use the same grid for urgent and non-urgent variants.

The repeated interval system translates TP-01; controlled tightening around metadata and actions translates TP-02. Sources: OBJ-01, OBJ-02, OBJ-03. OBJ-04 has no geometric influence.

Color-token roles

  • notify-surface: neutral notification background.
  • notify-text: highest text contrast.
  • notify-text-muted: metadata only.
  • notify-border: quiet separation from surrounding content.
  • notify-info, notify-success, notify-warning: semantic status accents.
  • notify-critical: urgent and error semantics only.
  • notify-focus: keyboard focus indicator independent of status color.

Use semantic colors from the app’s existing accessible system. Do not sample or imitate indigo, copper, pale blue, crimson, gold, straw, cream, or lacquer. Limit accent color to the status indicator, links, focus indication, and primary action. [TP-03; core sources]

For urgent messages, only notify-critical may receive the bounded increase in contrast/saturation associated with OBJ-04.

Typography roles

  • Priority label: 12px, medium weight, sentence case.
  • Title: 16px, semibold, 1.3 line height.
  • Body: 14px, regular, 1.45 line height.
  • Metadata: 12px, regular, 1.4 line height.
  • Actions: 14px, semibold.
  • Use the product’s established typeface.
  • Do not use decorative, display, handwritten, engraved, or craft-simulating fonts.

Title/action hierarchy translates TP-02; consistent role repetition translates TP-01. Sources: OBJ-01, OBJ-02, OBJ-03.

Motion behavior

  • Routine entrance: 160ms opacity transition with at most 4px vertical translation.
  • Exit: 120ms opacity transition.
  • Do not stagger announcements in a way that delays access to content.
  • Urgent arrival may animate only the critical token’s intensity once over 600ms.
  • No looping, shimmer, sparkle, bounce, rotation, scale pulse, or ornamental motion.
  • Under reduced-motion preferences, remove translation and the urgent pulse; use immediate state changes or a short fade.

Routine cadence traces to TP-01 and the core sources. The urgent one-cycle intensity increase is the only accepted OBJ-04 influence.

Interaction behavior

  • Focus moves only when the user explicitly opens a notification surface; a toast must not steal focus.
  • Hover and keyboard focus pause dismissal timers.
  • Only low-priority, non-actionable toasts may auto-dismiss, after at least eight seconds.
  • Action-required, error, and urgent messages remain until acknowledged, resolved, or explicitly dismissed.
  • Primary action appears first in reading order; no more than two actions.
  • Dismissal must not imply task completion.
  • Repeated events should update or group an existing notification when their object and required action match.
  • Every icon-only control requires an accessible name.
  • Destructive or risk-bearing actions require explicit labels; icon meaning alone is insufficient.

These rules apply TP-01 to repeated events, TP-02 to transitions, and TP-03 to action emphasis. Sources: OBJ-01, OBJ-02, OBJ-03.

Accessibility requirements

  • Meet accessible text, component, focus, and non-text contrast requirements.
  • Do not communicate state or priority by color alone.
  • Preserve logical reading and focus order.
  • Use polite live-region announcements for routine and action-required updates.
  • Reserve assertive announcements for immediate safety or operational risk.
  • Avoid duplicate visual and assistive-technology announcements.
  • Support text zoom and reflow without clipped titles, actions, or metadata.
  • Provide reduced-motion behavior.
  • Keep urgent, error, identity, consent, fee, security, permission, recall, and risk language literal.
  • Announce progress, success, and failure after an action.
  • Maintain keyboard access and visible focus for every action.

The hierarchy is compatible with OBJ-01, OBJ-02, and OBJ-03; these requirements override stylistic fidelity.

Example strings

Variant Example Trace
Routine Cordless drill is ready for pickup. Collect it from Neukölln Tool Library by Friday at 18:00. TP-01, TP-02; core sources
Action required Return due tomorrow. Return the tile cutter by 17:00, or request an extension. TP-02, TP-03; core sources
Success Return recorded. The pressure washer was returned at 14:32. TP-01, TP-02; core sources
Error Extension not requested. Your reservation has already been accepted by another member. Choose a new return time. TP-02; core sources plus correctness override
Urgent Urgent — stop using the angle grinder. Safety recall: disconnect it from power and return it to the library. Core anatomy: OBJ-01, OBJ-02, OBJ-03; urgent emphasis only: OBJ-04

Production sequence

  1. Implement the shared semantic anatomy and spacing rhythm. [TP-01]
  2. Add title, action, and transition hierarchy. [TP-02]
  3. Restrict each state to one dominant semantic accent. [TP-03]
  4. Implement routine, action-required, success, and error states without any OBJ-04 influence.
  5. Add urgent emphasis as a token-level contrast increase and one pulse only.
  6. Add keyboard, live-region, reflow, contrast, and reduced-motion behavior.
  7. Test with long tool names, translated strings, multiple notifications, offline actions, and failed recovery.
  8. Run the validation checks below.

Standalone downstream prompt

Design and implement an original notification system for a community tool-lending app. Base it on three traced principles: measured recurring anatomy and spacing (TP-01, supported by OBJ-01, OBJ-02, OBJ-03); stronger hierarchy at action and state boundaries (TP-02, same sources); and one dominant signal per notification (TP-03, same sources).

Provide routine, action-required, success, error, and urgent variants using one shared geometry and the product’s existing semantic icons and colors. OBJ-04 may affect only urgent emphasis by increasing the existing critical token’s contrast/saturation and allowing one non-geometric arrival pulse. It must never affect default notifications, layout geometry, icon shape, or decoration.

Do not depict or imitate baskets, cups, lanterns, masks, bands, dimples, folds, rivets, feathers, craft materials, source colors, ornament, silhouettes, or culturally specific motifs. Accessibility, correctness, and operational clarity outrank style. Keep errors, identity, consent, fees, security, permissions, recalls, and risks literal.

Validation checks

  • Every notification uses the same base anatomy and spacing rhythm.
  • Every notification has no more than one dominant accent.
  • Actions and state transitions are more prominent than metadata.
  • Routine and default states contain no influence from OBJ-04.
  • Urgent and non-urgent variants have identical geometry and icon shape.
  • The only OBJ-04 differences are critical-token amplitude and one optional pulse.
  • No source object, silhouette, material, motif, ornament, or literal color scheme is recognizable.
  • Literal source counts are not reused as digital layout or animation counts.
  • Color and motion are never the sole carriers of meaning.
  • Reduced-motion, keyboard, focus, live-region, zoom, reflow, and contrast behavior pass.
  • High-stakes language is literal and does not hide consequence or recovery.
  • A reviewer can explain the result using rhythm, hierarchy, density, interruption, and emphasis without naming a physical craft object.

Unknowns and confidence

Confidence is high for the explicitly described recurrence, threshold, interruption, and outlier relationships. The profile remains provisional because physical form, dimensions, construction, tactility, wear, affordance, and use were not available. Those missing axes must not be reverse-inferred from this handoff.

Boundary audit

Read exactly:

  1. task.md
  2. taste-extractor/SKILL.md
  3. taste-extractor/references/taste-profile.md

No other file, path, or external resource was inspected.