Place a design against its peers.

FleetEdge Design Benchmarks · Beta

Beta — access by request · The product is running: the screens below are the product’s own study on the public corpus, in beta. Every panel carries its own mark in the screen — ready or waits, live or typed absent — and a panel’s mark governs its claims. The office’s private tier is planned, and the product says so on its own face.

A design, validated the way a naval architect would defend it: a cohort study (the boats a figure is computed over — a real entry list, a class, a fleet — named on every figure) of the design under study against the classes it meets — the census first, the certificate as the ground, the served record read against the rating, every read composed by source, no verdict minted, and the claim boundary drawn — issued as an edition.

For naval architects, sailmakers, and lofts. Access by request.

Method: Event Retrospection Story: Formula X against the classes she meets, at the 2025 Worlds The public corpus; the office’s private tier planned

Scope: the public corpus today — every ORC-certificated boat of the classes you pick
The office’s private tier: planned; a certificate you upload today lands in the governed public intake
Your study: yours in the browser, resumed where it stood; nothing about an office’s private boats is on this plane yet
Access: by request — the product opens once your access is granted.

One study, several postures.

A design benchmark validates a design by a few methods, and the product names them in its own words. Its postures: retrospective by default; prospective, which states a hypothesis before the read; and a design what-if, which evaluates a change. Behind the question compared to what? it offers five study designs: the design under study against a reference cohort built from the classes she meets; an event cohort — everyone who raced an event she raced; a design cohort — her certificate alone, no comparison; a race micro-cohort of her actual rivals under an event, which arrives with the event contract; and a perturbation study — a governed what-if against fixed peers — which waits on the plane’s evaluation route. A second journey, the Design Launch, serves a design launch or a campaign triage.

The walkthrough below runs the first posture on the first design: Event Retrospection — the design under study against the classes she meets, read back from an event the cohort shared.

Event Retrospection: Formula X at the 2025 Worlds.

The subject is Formula X, an Xr-41. The comparison is seven boats she met, picked from the classes she meets — X-41, X-41 Mod, Italia 11.98, Farr 40 OD — read back from the Garmin ORC World Championships 2025 (the site’s published event page). The question, from the product’s own frame: where does Formula X give time away against the classes she meets? Nine chapters follow the product’s own rail; the figures stay in the screens.

Ask and pick.

The door names the subject and proposes the comparison — the classes she has raced against, pre-picked from her record and edited by hand — and sets the posture: retrospective, at boat grain. Every line on the rail is a door, never a control; the study so far sits beside the work and each step ticks as it is answered.

Design Benchmarks, the door: the rail with two journeys and the study's eight steps, the subject named and the comparison classes picked, and the question of how to establish the study subject with its four doors
Design Benchmarks (beta) · the door — the study subject named, the classes she meets, the posture; every line on the rail a door, never a control · captured 9 September 2026 (publication of 3 September 2026)

Who is in the study.

Eight boats, every one holding an ORC certificate, every one an entrant at the Worlds. On the served rank she placed first among them over her races and sailed faster than her rated pace at the event; each comparison boat sailed slower than its own. The census reads before any map — who is in, who is set aside and why, what each measure can be read over.

Design Benchmarks, the census: the design under study and the seven comparison boats, each with its class, certificate, rating, served rank over its races, and pace against rated
Design Benchmarks (beta) · who is in the study — the design under study and the comparison cohort, every boat with its certificate, its served rank and its pace against rated · captured 9 September 2026

The event contract.

The contract is in place before any observed read: seven races over four race dates, the wind band on every race — light to moderate air — and the gates: the official entrants as served, all certificated, all scored on the served rank lane. Beneath it the product’s own line: a served-rank reading is FleetEdge’s analytics over published results; the official result is never claimed here.

Design Benchmarks, the event contract: the conditions card with the wind band on every race and race date, and the gates listing the entrants as served, certificated and scored, with the line that the official result is never claimed
Design Benchmarks (beta) · the event contract, in place — the conditions race by race, and the gates: the entrants as served, certificated, scored; the official result never claimed · captured 9 September 2026

The atlas.

The five-axis read places every boat in words, never a number. Formula X reads upper quartile on stability (how much righting moment the boat carries relative to its displacement), on beam to length and on displacement to length; below the median on Sail Drive (the rig’s drive potential on a 0–100 scale); lower quartile on HEI (the Hull Efficiency Index — a drag-derived read of hull form, ranked against its cohort); and leaning strongly the other way on every bias — a powered, stable platform with a less slippery hull. The X-41 sisters read the other way round.

Design Benchmarks, the five-axis read: the eight radar axes for the design under study and three comparison boats, a position word per quality axis and a direction word per bias, never a number
Design Benchmarks (beta) · the atlas — the five-axis read: a position word per quality axis, a direction word per bias, never a number · captured 9 September 2026

The structural scatter draws the triangle — drag efficiency against righting moment — with the design under study marked at its stable, less-slippery corner and the cohort midpoint drawn. The stack rank and the archetype (one of the fleet’s eight recurring design types) list complete the atlas: one dimension at a time against the comparison’s median, and the eight grouped by the registry’s words as a representation, never a performance order.

Design Benchmarks, the structural scatter: the plot of hull efficiency against righting moment to displacement, the design under study labeled, the cohort midpoint drawn, the points sized by each boat's pace against the rating
Design Benchmarks (beta) · the structural scatter — drag efficiency against righting moment, the design under study marked, the cohort midpoint drawn · captured 9 September 2026

The certificate.

Up to four certificates side by side, the color on every row the difference from the reference boat: identity, hull, stability, performance from the certificate — and the rows this plane does not publish, typed absent by name.

Design Benchmarks, compare certificates: the design under study beside two comparison boats, the certificate's rows for identity, hull, stability and performance with each cell colored by its difference from the reference boat, and the rows not published to this plane typed absent
Design Benchmarks (beta) · the certificate — up to four side by side; the color is the difference from the reference boat; the rows this plane does not publish typed absent · captured 9 September 2026 (publication of 3 September 2026)

The variance ledger reads a class’s sisters across every served row and tags each — class-invariant, modal-core, individuating. The four X-41 sisters agree on five of twenty-three fields, and the twin census finds no twins. A class is a name; a boat is a certificate.

Design Benchmarks, the variance ledger: the four sisters of one class across the certificate's rows, each row tagged class-invariant, modal-core or individuating, and the twin census beneath finding no twins
Design Benchmarks (beta) · the variance ledger — one class name, four certificates: which fields the sisters share and which individuate them; the twin census beneath · captured 9 September 2026

The event and the observed conversion.

Her corrected times against her rated pace, every boat side by side: faster than rated at the event and over her served records alike. The sister that runs fastest over her season sailed slower than rated at this Worlds. The records and their confidence sit beside every read; a boat with no served record is typed absent.

Design Benchmarks, the observed record: for the design under study and three comparison boats, the pace against rated in words, the record and confidence counts, and each boat's best place and pace at the event
Design Benchmarks (beta) · the observed record — her corrected times against her rated pace, every boat side by side; the records and their confidence beside · captured 9 September 2026

Race insights lay the Worlds out race by race — each race’s course, wind and current beside the archetype read — the all-conditions read and the dominant condition. Race data is a bonus, never required: a boat with no observed record is a typed absence on every read.

Design Benchmarks, race insights: the championship opened race by race, each race with its date, course, wind and current beside the archetype race read, under the product's own line that the official result is never claimed
Design Benchmarks (beta) · race insights — the Worlds race by race, each race’s wind and current beside the archetype read · captured 9 September 2026

The composition and the agreement.

What produced each read, by source: the placement, an augmentation over named inputs; the certificate’s rows, ORC-native; the observed record, event-observed; the rows not published, typed absent. Two medians, one population. No verdict is minted between the certificate and a placement; whether the observed record supports the structural read is the agreement’s question, read after the event contract, and never a validation of the model.

Design Benchmarks, the benchmark composition: every boat's reads grouped by source, the placement as an augmentation, the certificate's rows, the observed record, and the rows not published typed absent, with the line that no verdict is minted between the certificate and a placement
Design Benchmarks (beta) · the composition — what produced each read, by source; two medians, one population; no verdict between them · captured 9 September 2026 (publication of 3 September 2026)

The story.

The mismatch shortlist is hypothesis-grade, never a score: where a class’s structural position and its record disagree. The X-41 reads structurally weak and competitively strong; the Xr-41 upper quartile and faster than rated. Then what this benchmark can claim — the cohort’s membership under the rule, the refusals and their counts, the archetype cross-section as a representation — and cannot: any ordering of the archetype words by performance; any official result; anything about an office’s private boats; a what-if as a measurement.

Design Benchmarks, the claim boundary: the mismatch shortlist of classes whose structural position and record disagree, marked hypothesis-grade, and the two columns of what this benchmark can claim and cannot
Design Benchmarks (beta) · the claim boundary — the mismatch shortlist, hypothesis-grade; what this benchmark can claim, and cannot · captured 9 September 2026

Three lead findings carry the story in the same ten fields — the read, the reference, the magnitude, the evidence, the composition, the agreement, the confidence, the counter-case, the claim boundary, the next test — and a lead composes into the edition only with its counter-case placed beneath it.

The edition.

Issued with its reference — the study’s own number and date — the counter-cases beneath each lead and the claim boundary carried whole. This study’s edition was not yet issued at the capture; the product’s rail says so, in its own words.

The study, and the edition.

Aggregate reads over the public corpus — the certificate each boat holds and the published results — every read carrying its source and its rung. There is no verdict between sources: you read the composition and draw the boundary.

The door

Name a boat, upload a certificate into the public intake, pick a design class or pick an event; the comparison proposed from her record and edited by hand; the question and the posture declared.

The census

Who is in, who is set aside and why, what each measure can be read over — read before any map, with the register on every row.

The event contract

An event the cohort shared, in place before any observed read: the races, the conditions, the gates; the official result never claimed.

The atlas

The five-axis read in words, the structural scatter, the stack rank against the comparison’s median, the archetype list as a representation — each an augmentation, named as one.

The certificate and the ledger

Up to four certificates side by side with the reference boat’s color; the variance ledger across a class’s sisters and the twin census beneath.

The observed record and race insights

Her corrected times against her rated pace, side by side, with the records and their confidence; the event race by race beside its conditions.

The composition and the agreement

Every read by source — augmentation, ORC-native, event-observed, typed absent; two medians, one population; no verdict minted between them.

The story and the edition

Three lead findings in ten fields, the counter-cases placed beneath, the claim boundary drawn; the edition issued with its reference.

What is served, layer by layer

Every screen carries its own mark — ready or waits, live, typed absent — and a panel’s mark governs its claims; the office’s private tier is planned and says so.

Built on the FleetEdge platform’s shared core, reading the public corpus at the certificate and the published record; every read names its reference and how it is computed.

Deliberately not here: a verdict between the certificate and a placement — you read the composition. No official result — a served-rank reading is analytics over published results. No private tier yet — every screen shows the public corpus. No design is called better without its conditions attached, and the model’s internals stay internal.

Ask. Read. Verify. Tell. Issue.

For design offices and sail analysts who must say, and defend, what a design is worth — before a client consult, after a launch, across a range.

  1. Ask — name the subject, take or edit the comparison the product proposes, declare the question and the posture.
  2. Read — the census, the event contract, the atlas, the certificate, the observed record — each read with its source and its rung.
  3. Verify — the composition by source and the agreement under the contract; no verdict where the product mints none.
  4. Tell — the lead findings in ten fields, the counter-cases placed, the claim boundary drawn.
  5. Issue — the edition with its reference, the boundary carried whole.

A note on the numbers above.

· Every figure on this page reads from the product screens pictured — the product’s own study on the public corpus, captured 9 September 2026 at the product’s publication of 3 September 2026.

· The counts in the screens are that capture’s own reads; this page restates none, and the words it uses for positions and directions are the product’s own at the capture.

· A served-rank reading is analytics over published results; no official result is claimed on this page or in the product.

· The marks — ready, waits, live, typed absent — are the product’s own vocabulary, declared panel by panel; a panel’s mark governs its claims.

· The office’s private tier is planned; every screen shows the public corpus, and the study is the product’s own demonstration, not an office’s work.

· No design is called better than another here — the product shows its work and draws its claim boundary.

· Beta access is by request.

Design Benchmarks draws on the FleetEdge taxonomy and hull layer: Fleet Archetypes, Hull & Platform, and the Methodology.

See it against your own work.

Scope: the public corpus today · the office’s private tier planned · in beta, access by request.