## Reference images

Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language.

- Component: https://kage-design-assets.t3.tigrisfiles.io/components/hypervibe/0f025394-2dff-4c9b-be5f-8e394ec4a30f-1791699114-5.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/hypervibe/0f025394-2dff-4c9b-be5f-8e394ec4a30f-1791699070438-full.webp
- Component on Kage: https://kage.design/component/hypervibe-feature-grid-3

## Before you start
Ask what autonomous or coordinated workflows the user's product enables and what proof best demonstrates them. Then adapt this section pattern to the user's product.

Create an orchestration feature section with a small section index, a bold two-line heading, and a paragraph describing the workflow from trigger to result. Place a wide product visual beneath the text, followed by two equal-width supporting cards with smaller visuals and concise captions. Align every element to a consistent centered rail. Use #050505 background, #12130f visual panels, off-white headings, #85837e body text, and a restrained orange accent. Use 16px radii, 1px low-contrast borders, 24px gaps, and enough vertical space for the visual to read as evidence rather than decoration. Make cards responsive and preserve semantic headings.

### Never
- Never use logos, product names, copy, illustrations, or imagery from the reference.
- Never copy the reference agent names, screenshots, or workflow language.
- Never imply autonomy beyond what the user's product actually supports.