Demonstration

Review the finished states

Every state below is fabricated and safe to open. Nothing here purchases anything, generates a report, sends an email, or reads or writes a stored job. The report and PDF behind the buttons are the published samples.

Not available here

This page is preview-only

You are on the live site. Open the preview deployment for the branch you are reviewing.

While the review is being built
1 · Sending

Your answers are uploading

The moment before Arete has anything. This is the one point where closing the page loses the submission, and the copy says so.

Open the sending state →
2 · Building

Arete has your answers

The job is accepted and running server-side. The wait line is the server's own, not a timer. Closing the page is now genuinely safe.

Open the building state →
When the review is ready
3 · Ready

Delivered, email accepted

The ordinary finish. The mail provider accepted the message — which is not the same as it arriving, and the wording keeps that distinction.

Open the completed state →
4 · Email not confirmed

Ready, but the email is unproven

No record that the email went out. It may still have — so this says it cannot be confirmed, never that it failed. Your report is here either way.

Open the unconfirmed state →
5 · Bounced

The address rejected it

The emailed copy is definitively not coming. This is the state you should not have to reproduce yourself — it needs a real undeliverable address to occur naturally.

Open the bounced state →
The rest of the journey
Real pages, real content

Dashboard and living report

These are not demonstrations. The dashboard lists whatever this browser has opened; the living report is the published sample, the same one the completed states link to.

Open your Arete dashboard → Open the sample living report →
What I am asking you to decide
Four questions

Ask these of every state

Usability acceptance only. Whether the underlying machinery is correct is an engineering question and is not yours to answer here.

  1. Is the next action obvious? Without reading twice, do you know what to do and which thing to do first?
  2. Is the status understandable? Do you know what is happening, what happens next, and does anything claim more certainty than it has earned?
  3. Does the reading experience feel premium? At your normal text size, one hand, no pinching — does this feel like something worth what it cost?
  4. Is help or recovery easy to find? If this went wrong for you, is there a route out that does not depend on something you may not have?

Anything that fails one of these is a design decision for you. Anything that looks wrong underneath — a status that could be false in reality, an email that would not really send — is mine, and is listed as an engineering check in the slice record rather than something to test on a phone.

One thing the tests cannot tell you

Typography is unverified here

The marketing type suite measures declared sizes with the web fonts blocked, because they are unreachable from the test environment and a hanging request is not a measurement. So it proves the scale is consistent — it proves nothing about how Cormorant Garamond and DM Sans actually render, line lengths, or the weight of a headline on a real screen.

You are looking at the pages with the real fonts loaded. That makes your eye the only check on final typography that exists so far.