CRAZE LAYER

CRAZE should explain the page, not become another chat product.

CRAZE is SUPERCRZY's reading layer. It compresses the page, sharpens the angle, and routes the reader into the right next surface. It should feel like the site thinking one step ahead, not like a generic assistant window.

See core actions See Agent boundary

Core actions

Summary, angle, route, context

Lightweight

Summary Angle Route Context

CRAZE

CRAZE is here to make reading faster, not to replace the reader.

Its job is to collapse the page into a clearer judgment, explain what actually matters, and point toward the right next article, rank lens, topic lane, lab verdict, or agent surface.

Compress the current page into one judgment.
Explain why the page matters in the larger product logic.
Offer one confident next route instead of a loose feed of links.

01 / Context

Know where the reader is.

CRAZE should detect whether the user is reading News, comparing Rank, scanning Topics, reviewing Lab, or exploring Agent. The answer should change with the surface, not feel like a floating chatbot dropped onto every page.

02 / Judgment

Turn pages into usable decisions.

On News it sharpens the implication. On Rank it explains the fit. On Topics it builds a path. On Lab it compresses the verdict. On Agent it clarifies the type before the user enters an experience.

PRODUCT BEHAVIORS

What CRAZE should do across the site

The goal is not to make a louder assistant. It is to make SUPERCRZY feel like it understands what the reader is trying to decide.

News

What matters most here?

Summarize the article, identify the real implication, then recommend the next relevant story.

Rank

Which model should I use?

Convert the leaderboard into workflow-fit recommendations with tradeoffs and alternatives.

Topics

Where is this trend going?

Explain the longer arc and build a reading path without forcing the user to search manually.

Lab

Does this hold up?

Turn tests and product notes into a sharper verdict: who should use it, who should skip it, and why.

Agent

Which agent should I care about?

Map the field by category first, then route toward the right experience instead of collapsing all agents into one comparison.

CRAZE / AGENT BOUNDARY

CRAZE handles understanding. Agent handles deeper action.

CRAZE should stay lightweight on the website: summarize, explain, route, and preserve reading flow. The moment the user needs sustained comparison, execution, or a deeper interactive experience, that is the Agent layer, not CRAZE pretending to be one.

01 Read context

Article, topic, rank table, or lab verdict.

02 Clarify intent

Summarize, compare, choose, monitor, or act.

03 Escalate

Route into Agent, with SuperCrzy Agent as the recommended deeper entry.