Thinking, Made Readable
Iris turns notes, readings, and rough AI output into a report someone can trust.
Most AI output has the facts, but not the room tone: no stakes, no order, no visible confidence. Iris reads the mess, finds the point, and gives the reader a page with pace, evidence, and room for careful doubt.
ThesisAn Iris report earns its design by making a conclusion easier to read, check, and act on.
Key findings
The notes are not the story.
Iris can start from code notes, product critique, research clips, timelines, half-formed thoughts, or a rough requirement.
The first pass asks what the reader needs to see. A buried conclusion may become the title. Caveats may become assumptions. A long list may become one figure when the relationship matters more than the wording.
The page keeps the signal and lets the clutter fall away. It names what is observed, what is inferred, and where the report still owes the reader caution.
The authoring path chooses the reading before it chooses the layout.
Source notes, side notes, and tables share the same quiet material.
| Element | Best use | Visual rule |
|---|---|---|
| Evidence note | A source record, caveat, confidence note, or measured fact. | Same accent rule, same muted body type. |
| Side note | A nearby qualification, short quote, or "why this matters" note. | Same skeleton, different label. |
| Matrix | A comparison across conclusions, risks, decisions, or layers. | Short headers and top-aligned cells. |
The prose should sound edited, not generated.
Cut filler, false neutrality, and sentences that announce their own importance.
A polished page can still speak plainly. It says what the material supports, where it stops, and what the reader can do next.
The voice follows the reader's language. Chinese pages should read like Chinese thinking. English pages should avoid product fog. Technical pages can stay precise without turning every sentence into a term sheet.
Assumptions
- The source material has already been read with care.
- The reader needs a decision, not a prettier transcript.
Anti-patterns
- Do not pad the page with summary voice.
- Do not make a weak source sound certain.
Follow-through
- Write the report directly in HTML.
- Check the first screen, evidence margin, and mobile view.