№ 191 / Field notes
Traceable annotation
Carry the actual question into an annotation so its meaning survives the transition from text to plan.
IN EVERYDAY WORDS
Carry the actual question into an annotation so its meaning survives the transition from text to plan. Connect the request to its plan location.
The look
A leader joins the visitor’s own note to the pinned kitchen opening. Keep the type and annotation in a listing presentation as the visual subject.
Say this to a designer
On my type and annotation in a listing presentation, connect the request to its plan location. Show “Margin note” and “Pinned note”. Carry the actual question into an annotation so its meaning survives the transition from text to plan.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- The visitor controls “Attach the note” with touch, pointer or arrow keys.
- entrance
- Begin with the recognizable state “Margin note” in view.
- path
- A leader joins the visitor’s own note to the pinned kitchen opening.
- timing
- Follow the visitor’s input directly. For a replay, traverse the full study in about two seconds.
- easing
- Use linear tracking for scrubbing and a gentle ease at both ends of a timed replay.
- hold
- Hold “Pinned note” while the viewer inspects the result or opens the brief.
- exit
- Keep the complete original wording available to read, select and speak at every stage.
The vocabulary
- Attach the note
- Carry the actual question into an annotation so its meaning survives the transition from text to plan.
- Reference endpoints
- “Margin note” and “Pinned note” define the two checkable states of this effect.
Make it fit your project
Good places to use it: type and annotation in a listing presentation, field notes example.
Apply this to the type and annotation in a listing presentation when the visitor needs to see the change from “Margin note” to “Pinned note”.
Watch for: Keep the complete original wording available to read, select and speak at every stage.
When motion is off: Show the two named states “Margin note” and “Pinned note” on demand. Keep automatic movement off.
Implementation and accessibility
- Connect the request to its plan location.
- Start in “Margin note”. Bind the control “Attach the note” to one reversible value between zero and one.
- A leader joins the visitor’s own note to the pinned kitchen opening.
- Keep the complete original wording available to read, select and speak at every stage.
- Inspect the two endpoints and the midpoint on a narrow touch screen. Verify the result using the keyboard.
- Give “Attach the note” an accessible name and keyboard controls.
- Expose the before and after descriptions as text.
- Load the active study’s assets on demand. Stop rendering while its stage is off screen.
Give it to your AI
Download the working source and example assets. Match this reference number in the included catalog to its renderer.
Replace [ELEMENT] with the part of your project you want to change. The prompt includes the design brief, motion direction, definitions, and implementation steps.
Read the full prompt
Use AI Acceleration Design Ref #191 (Traceable annotation, version 1) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/191. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: Carry the actual question into an annotation so its meaning survives the transition from text to plan. DESIGN REF #191 · Traceable annotation In everyday words: Carry the actual question into an annotation so its meaning survives the transition from text to plan. Connect the request to its plan location. The look: A leader joins the visitor’s own note to the pinned kitchen opening. Keep the type and annotation in a listing presentation as the visual subject. Say this to a designer: On my type and annotation in a listing presentation, connect the request to its plan location. Show “Margin note” and “Pinned note”. Carry the actual question into an annotation so its meaning survives the transition from text to plan. Motion direction (starting points to adapt): Trigger: The visitor controls “Attach the note” with touch, pointer or arrow keys. Entrance: Begin with the recognizable state “Margin note” in view. Path: A leader joins the visitor’s own note to the pinned kitchen opening. Timing: Follow the visitor’s input directly. For a replay, traverse the full study in about two seconds. Easing: Use linear tracking for scrubbing and a gentle ease at both ends of a timed replay. Hold: Hold “Pinned note” while the viewer inspects the result or opens the brief. Exit: Keep the complete original wording available to read, select and speak at every stage. Design vocabulary: Attach the note: Carry the actual question into an annotation so its meaning survives the transition from text to plan. Reference endpoints: “Margin note” and “Pinned note” define the two checkable states of this effect. Reduced motion: Show the two named states “Margin note” and “Pinned note” on demand. Keep automatic movement off. Implement: 1. Connect the request to its plan location. 2. Start in “Margin note”. Bind the control “Attach the note” to one reversible value between zero and one. 3. A leader joins the visitor’s own note to the pinned kitchen opening. 4. Keep the complete original wording available to read, select and speak at every stage. 5. Inspect the two endpoints and the midpoint on a narrow touch screen. Verify the result using the keyboard. Adapt the reference to my branding and content. Preserve existing functionality and semantic HTML. Reduced motion: Show the two named states “Margin note” and “Pinned note” on demand. Keep automatic movement off. Accessibility: Give “Attach the note” an accessible name and keyboard controls. Expose the before and after descriptions as text. Performance: Load the active study’s assets on demand. Stop rendering while its stage is off screen. Avoid: Keep the complete original wording available to read, select and speak at every stage. Show me the working result, verify keyboard, mobile, loading/error and reduced-motion behavior, and explain any tradeoff. Do not publish or change unrelated elements.
Permanent reference #191 · version 1. Pairs with #193, #003.