§ Work · W2

A quality score for a product traded on one number: method, platform and paper

Two lots of the same product with nearly the same headline measurement can perform very differently in use, and the trade gives buyers no way to see that before they buy. An industry group wanted that difference made visible. NoArt Systems first checked that the people who would use a score recognized the problem, then turned that intent into a published measurement method, a platform that scores items and issues certificates anyone can verify, and a methods paper that states what the score shows and what it does not.

The pattern holds wherever a market trades on one easy measurement: a second number is worth adopting only if every reader can reproduce it, see what drives it, and see what it does not claim.

Generalized from one piece of work. The client, the product, the partners and every figure are removed.

§ 01

Situation

Items that pass the same specification were not worth the same.

The product is bought and sold mainly on one headline measurement, checked as pass or fail against a contract specification. Buyers know the cost of that: two lots with nearly the same headline number can perform very differently in use, and nothing in the trade shows the difference before the purchase.

An industry group wanted buyers and sellers to see what the headline measurement misses: one score that compares items on overall quality and shows what drives the difference. It had a clear hypothesis that such a score could work, and provided access to a large proprietary dataset of historical test results. What it needed was the specialized capability to turn that hypothesis into a tested method, a working platform, and evidence that the score means what it claims.

Turning that hypothesis into a method starts with one question: how do measurements in different units add up to one number? Think of scoring a decathlon: ten events, timed in seconds or measured in meters, and you cannot add seconds to meters. So every event is first converted onto one common points scale, and only the points are added. A quality score has the same problem and the same answer: each measurement is first turned into credit on one common scale, and only then weighted and added.

The analogy also shows where the hard part lies. A decathlon's points tables are settled; a quality score has to decide for itself what each measurement is judged against, how much each one counts, and what to do when one is missing. Because buyers and sellers would rely on the result, each of those answers also had to be one that either side could check for itself. That set the shape of the work.

§ 02

Approach

Understand the problem first, then specify the method before the software, publish every rule, and let the evidence set the limits of the claims.

The work began with discovery, not design. A short round of market research asked one question first: do the people who would use a score recognize the problem? It looked at how buyers decide today: on the headline measurement, then on long test reports that are hard to compare, and on internal scorecards that differ from firm to firm. The split runs through the buying firm: the people who buy decide on one number, while the people who use the product judge it on others.

The findings were written up as an internal mock announcement of the score's launch, with answers to the hardest questions a skeptic would ask. That working document set down who the score is for, what it must not try to do, which decisions would be hard to reverse, and which claims the evidence could not yet support, and the rest of the work was checked against it. It set the scope: add to the headline measurement rather than replace it, keep the score small enough to teach, and earn trust before making any claim about price.

Only then was the method specified in full, building on the client's hypothesis: which measurements count, how each one earns credit, how the credits are weighted, and when an item gets no score or is rejected outright. The test data are far from normally distributed, and several measurements are strongly skewed, so a method built on averages and standard deviations would misplace many items. Credit is therefore read from an item's actual position in the reference population, or from a fixed rule on an absolute scale, and turned into value through non-linear utility functions, each studied for its own measurement: more of a good property earns less and less extra credit, some properties have a range that is simply right, and past a limit a value earns nothing. The main weights start from a survey of what market participants value; where the adopted weights depart from it, the paper says so. An item with a missing measurement is not scored, so nobody gains by leaving one out.

The method is one published specification, and anyone can recompute a score independently from it and the population's published reference points. The full dataset is processed offline, never on the website. Every chart and number in the paper is produced directly from the real test data, and the scoring is re-checked on every release.

Before circulation, the paper went through rounds of structured internal review, each from the standpoint of a different reader: buyer, seller, client and outside expert. Each finding was checked against the code, the data or the cited source, and accepted or rejected with a written reason. Uncomfortable findings are stated in the paper's summary, not left in an appendix.

§ 03

From test record to a score anyone can check

Six steps, each with the rule that keeps it honest, and the review loop that tested them.

Fig. W2 — Chain of evidence Record → Method → Score → Certificate
  1. Test records

    A large proprietary dataset of test results, processed offline, never on the website. Only aggregates and de-identified examples are published.

  2. Reference population

    Recent, complete items only, on a rolling window. Missing values are never filled in.

  3. Published method

    Measurements, credit curves, weights and refusal rules in one versioned specification; earlier versions are kept for comparison.

  4. Open scoring

    Anyone can recompute a score independently from the published method; re-checked on every release.

  5. Score and drivers

    One continuous number, the drivers behind it, and its position in the population. No medals or tiers.

  6. Signed certificate

    An item tested independently of the submitter, signed, and verifiable by anyone without an account.

Review loop

Internal review from each reader's standpoint every finding checked against code, data or source accepted or rejected in writing routed to the method, the platform or the paper.

Figure W2. The chain of evidence behind the score: each step carries the rule that keeps it reproducible, and the review loop runs across all six. Generalized from client work.

Terms used on this page

Item
One tested unit of the product, known only through its test record: a set of measurements, not proof of a particular shipment.
Reference population
A set of recent items, chosen by published rules, with every measurement present; every new item's score is ranked against it.
Credit curve
How one measurement turns into credit: a non-linear utility function of the item's position in the population, or a fixed rule on an absolute scale.
Weight
How much one measurement, or a group of them, counts in the score; the main weights start from a survey of what market participants value.
Driver
The amount one measurement adds to an item's score or takes away from it.
Refusal rule
A condition under which an item gets no score, or is marked rejected whatever its score, rather than simply scored low.
Certificate
A signed record of one item's score that anyone can verify, and that can be amended or revoked without rewriting its history.
§ 04

Where this sits in the scope of practice

The work mapped to the services it drew on.

  • 04

    Data Products & Decision Systems

    The core of the work: a scoring method, a benchmark built from a real population, and a platform shaped around a decision buyers make on every purchase, with every rule published so the score can be audited.

  • 05

    Architecture, Requirements & Technical Due Diligence

    Discovery before design: whether the problem was recognized and how buyers decide today, written up as an internal mock announcement with answers to hard questions. Then the client's intent turned into a specification with acceptance rules, a decision log, and versioned releases, and one platform that carries every workflow end to end: scoring an item, comparing items, exploring the population and its trends, simulating how much testing a buyer needs, and requesting, issuing and verifying a certificate. Behind it, the data work: mining a large dataset of test results, descriptive analysis of how quality is distributed and moves over time, and predictive modeling of whether quality carries through to price, each result validated on data the model had not seen, so that it holds up for the most skeptical auditor.

  • 01

    AI Strategy, Readiness & Build-vs-Buy

    A deliberate decision not to use a learned model: a transparent formula and methodology that every buyer and seller can reproduce.

§ 05

Deliverables

What NoArt Systems handed over.

  • D1 Discovery brief Market research on whether the problem is recognized and how buyers decide today, written up as an internal mock announcement with answers to hard questions: who the score is for, its limits, and the claims not to make yet.
  • D2 Measurement method specification Measurements, credit curves, weights with a documented origin, and refusal rules; versioned, with earlier versions kept for comparison.
  • D3 Scoring platform Self-serve scoring with a driver breakdown, population and comparison views, and a calculator that shows every weight and curve.
  • D4 Certification operating model A proposed model for certifying items globally: which testing providers may certify, how their independence from the seller is kept, and how a certificate is issued, verified, corrected or withdrawn with its history intact. Its workflow was successfully piloted end to end.
  • D5 Sampling simulator How much a result moves by chance, and how much testing a buyer needs before relying on it.
  • D6 Methods paper, full and short editions Every chart and number produced from the real test data, with its claims limited to what was measured and its limitations stated.
  • D7 Review trail A register of every review finding, each checked against the code, the data or the cited source, and accepted or rejected with a written reason.
§ 06

What the method makes visible

Items with nearly the same headline number spread across most of the quality range.

Illustration — one band, many scores Headline → Score
  • Headline measurement, all items
  • One narrow band a buyer treats as the same product
  • Quality score of the items inside that band
  • Median of each distribution

Stated as structure, without numbers: the shapes follow the real results, with counts and values removed.

Items that meet the same headline specification separate widely once the other measurements are counted, and most of that spread comes from a few measurements the specification does not cover. The paper reports this as a measurement, not a price. It also marks what the evidence already supports and what is still to be tested, chiefly whether the score tracks performance in use.

Every score can be traced to a published rule and independently recomputed by anyone, and every certificate can be verified as genuine without an account. A buyer can check the arithmetic from the published reference points onward without trusting the client. The reference points themselves rest on a single source of test data, which no outside party can yet re-derive, and the paper names that as its main limitation.

§ 07 — Contact

Tell us what you are building — or what you are trying to figure out.

In your note, include the initiative, the decision point, the timeline, and whether you need advisory, architecture review, a hands-on build, vendor oversight, or roadmap support. We respond directly.