How it learns
A check isa label.
01
Why this is different from other pattern AI
Most tools generate geometry. Geometry has no truth value attached — a pattern that will not sew looks exactly like one that will, until someone cuts fabric. Because Gradestudio stores construction rather than coordinates, the solver can answer a question no geometry system can: was this correct? An answer to that question is a label. Labels are what learning is made of.
02
The four things that produce a label
- 01A size run solved and measured against a declared tolerance
- 02A seam walked against its correspondence
- 03A pattern imported from another system and re-parameterised — which turns a dead file into a readable construction
- 04A pattern maker accepting or overruling a proposed fix, which is the rarest signal of all: a professional's judgement on what correct enough means in practice
03
What we store, exactly
The full telemetry schema, published, field by field. If a field is not on this page, we do not collect it. The same list lives in the repository as docs/telemetry-schema.md, and the constructor that emits an event will refuse any shape that is not this one.
ruleenumseam_walk · notch_match · dart_close · tolerance · grade_hold
Which construction rule was evaluated. An identifier for the kind of check — a seam walk, a notch match, a dart close, a tolerance measure, a grade holding at a size — never the geometry it was evaluated on.
outcomeenumpass · flag · accepted · overruled
Whether the check passed, flagged, or was accepted or overruled by the pattern maker. `accepted` and `overruled` are the rarest signal: a professional's judgement on what correct enough means in practice.
magnitudeenum0-2mm · 2-5mm · >5mm
How far a flagged check was out, bucketed. A bucket cannot be reverse-engineered into a dimension. Exact millimetres are never stored.
garmentenumbodice · sleeve · skirt · trouser · dress · outerwear · other
The class of garment the check ran on, so a lesson about a sleeve cap is not applied to a trouser crease. A class, never a style name.
What is never stored
- Coordinates, control points, path data, or any other geometry
- Measurement values — chest, ease, a seam length, a grade increment
- A style name, a piece name, a client name
- An account identifier, an email, a studio name
- The pattern file, a thumbnail, a hash of the file
The same schema, in the repository: docs/telemetry-schema.md
04
Why we ship generation last
Generation into raw geometry produces a plausible pattern that doesn't sew — which this industry has already been sold twice. Generation into a substrate that verifies everything it produces is a different product. The delay is the feature.