Talk about your next project
Harmonic case study

The lesson

Lead with the standard bar in the category, then show the deeper proof your product made possible.

The move

The page opens with the title “How Manifest went beyond ‘no loss of funds’ with Aristotle,” tags for Rust security and order-book verification, and a summary that Aristotle proved 28 things about Manifest’s code and found a rounding bug. It then explains “Beyond no loss of funds,” using the category’s usual proof standard as the starting point before naming what Manifest wanted checked. The middle of the story walks through “A trade that hit its target, then failed,” then moves into “The results,” with 28 proved results, 8 areas covered, and 2 findings, both corrected. The page closes with “What the proof covers,” which states the limits and conditions of the work, followed by a short product flow under “Find what your tests and audits miss.”

Why it works

  • Our readThe first screen states the customer, the technical domain, the number of proved results, and the bug found, so the value is clear before the reader reaches the details.
  • Our readThe “Beyond no loss of funds” section uses a familiar security baseline, which helps a technical buyer understand why the case matters.
  • Our readThe results table names each proof area and what was proved, giving readers a usable map of the work instead of a vague success story.

What not to copy

Don't copy Manifest's Solana order-book details, Lean statements, Token-2022 context, or the exact rounding example. Keep the structure of a known category baseline, a concrete defect, a quantified proof summary, and a plain statement of coverage and limits.

More from Harmonic

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.