№ 007 / Opening sequence
Make the scattered pieces useful
Show how the evidence supports the next action.
- Known
- Source: Website tool ·
- Given
- Can you send me the property details?
- Unknown
- Visitor identity · not inferred
Try it. Nothing is sent.
IN EVERYDAY WORDS
Loose pieces of information move into a useful summary, and you can still see where each one came from.
The look
Small labeled source records gather into an orderly customer brief. Source IDs stay beside the resulting information.
Say this to a designer
Animate these source notes into a clear brief. Start with separate labeled pieces, move them into their corresponding positions in a deliberate sequence, and keep each source ID attached. Use spacing and alignment to show the structure. Leave unknown information visibly marked as unknown, then reveal the next-action draft.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- The visitor enters the explanation or requests a demonstration of the assembled brief.
- entrance
- Show a small set of separate source notes with readable labels.
- path
- Move each note toward its matching row in the final brief, straightening it as it arrives.
- timing
- Try a 900-millisecond assembly with about 150 milliseconds between note starts. Reveal the next-action draft after the sources settle.
- easing
- Ease out so each piece gently aligns with the others.
- hold
- Stop all note movement so the assembled brief, sources, and unknowns can be inspected.
- exit
- Carry the completed brief forward as one object. Keep source relationships available.
The vocabulary
- Choreography
- The planned order and relationship of several movements.
- Stagger
- A small delay between related objects starting to move.
- Alignment
- Placing elements along shared edges or guides so their relationship is clear.
- Provenance
- Where information came from and the evidence that supports it.
Make it fit your project
Good places to use it: customer brief, research summary, document synthesis, workflow explanation.
Explain how several records contribute to one usable output.
Watch for: Do not animate guesses into facts or make a staged example look like a live integration.
When motion is off: Present source records beside the final brief with written connections.
Implementation and accessibility
- Label each input with its source ID and date.
- Keep a distinct slot for unknown or missing evidence.
- Move records into the relevant part of the final brief.
- Retain source links beside the resulting statements.
- Reveal a next-action draft and its evidence; keep external execution separate.
- Use a readable list or table as the underlying structure.
- Label the example and its evidence status.
- Do not communicate confidence only by color.
- Use a small fixed set of objects.
- Pause once the readable brief is assembled.
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 #007 (Make the scattered pieces useful, version 2) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/007. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: Show how the evidence supports the next action. DESIGN REF #007 · Make the scattered pieces useful In everyday words: Loose pieces of information move into a useful summary, and you can still see where each one came from. The look: Small labeled source records gather into an orderly customer brief. Source IDs stay beside the resulting information. Say this to a designer: Animate these source notes into a clear brief. Start with separate labeled pieces, move them into their corresponding positions in a deliberate sequence, and keep each source ID attached. Use spacing and alignment to show the structure. Leave unknown information visibly marked as unknown, then reveal the next-action draft. Motion direction (starting points to adapt): Trigger: The visitor enters the explanation or requests a demonstration of the assembled brief. Entrance: Show a small set of separate source notes with readable labels. Path: Move each note toward its matching row in the final brief, straightening it as it arrives. Timing: Try a 900-millisecond assembly with about 150 milliseconds between note starts. Reveal the next-action draft after the sources settle. Easing: Ease out so each piece gently aligns with the others. Hold: Stop all note movement so the assembled brief, sources, and unknowns can be inspected. Exit: Carry the completed brief forward as one object. Keep source relationships available. Design vocabulary: Choreography: The planned order and relationship of several movements. Stagger: A small delay between related objects starting to move. Alignment: Placing elements along shared edges or guides so their relationship is clear. Provenance: Where information came from and the evidence that supports it. Reduced motion: Present source records beside the final brief with written connections. Implement: 1. Label each input with its source ID and date. 2. Keep a distinct slot for unknown or missing evidence. 3. Move records into the relevant part of the final brief. 4. Retain source links beside the resulting statements. 5. Reveal a next-action draft and its evidence; keep external execution separate. Adapt the reference to my branding and content. Preserve existing functionality and semantic HTML. Reduced motion: Present source records beside the final brief with written connections. Accessibility: Use a readable list or table as the underlying structure. Label the example and its evidence status. Do not communicate confidence only by color. Performance: Use a small fixed set of objects. Pause once the readable brief is assembled. Avoid: Do not animate guesses into facts or make a staged example look like a live integration. 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 #007 · version 2. Pairs with #004, #003.