The cloth is woven from this chapter's 4 exhibits: each weft is one exhibit's own data, normalised; each warp group is a section. The probe reads the exhibit's own value where it crosses. Procedural visualisation, not a measurement.
EX 05
EX 07
EX 08
The chapter as a draft: 7 sections, 3 exhibit wefts, one shuttle.
Lead exhibit · 05TimelinederivedExplicit sewing representations appear throughout the research window
01 / 08
Read-out
Method and source
Derived visual positions from cited first-submission dates: decimal year = calendar year + elapsed days since 1 January / days in that calendar year. Cluster positions are display locations within the named month, not additional publication dates; the source register preserves every exact date. These are publication events, not adoption measurements or capability scores.
Unit: decimal year of first arXiv submission. Status: derived. Sources: S02, S03, S04, S08, S09, S10, S11, S14, S16, S18, S27.
The chapter's warpBar: share of the reading · square: an exhibit
The research record supports a precise but limited conclusion: structured garment generation was already active before the recent interest in agents, and later systems added interfaces, representations and refinement loops rather than following a single march from pictures to production. GarmentCode addressed parametric sewing-pattern construction in June 2023, while Sewformer addressed image-to-pattern reconstruction in November 2023.[S02][S03] Text-guided sewing patterns, multimodal pattern tokens, generated programs, parameter files, material inference, fit-aware data and schema-aware synthesis then developed along partly independent paths.[S04][S08][S09][S10][S11][S16] None of these publication events measures how many apparel firms use a method, whether a factory accepts its output or whether a buyer approves the resulting garment. GFT should therefore read the chronology as a map of testable techniques, not as evidence of market adoption or production readiness.
The historical window is a baseline rather than a market census
Related · chapter 017 paragraphs step it
Related exhibit 01 · chapter 01Stacked compositionsourcedThe cotton gap explains the industrial problem, not an AI return
01 / 02
Read-out
Method and source
Approximate inherited sector baseline from Cameroon Trade Hub (R06, publication date unrecorded) and stated 2030 national policy target from SND30 via Ecofin Agency (R07, publication date unrecorded). The 2030 column represents a national policy target rather than an achieved operating share or a forecast return from design software.
Unit: percent of cotton fibre. Status: sourced. Sources: R06, R07.
The inherited programme baseline describes apparel generative AI in 2023 and 2024 as mainly design-side image generation across style, silhouette, colour and surface pattern.[R30] That description is useful because it records what the source programme emphasised when framing its digital strategy. It is not a count of tools, firms, users or factory installations. The inherited entry also lacks a complete journal citation, so it cannot carry a stronger claim about the whole research field or any national market.[R30] The correct use of R30 is therefore narrow: retain the programme's image-led starting point, then test that starting point against opened research records.
The opened record immediately complicates an image-only origin story. GarmentCode's first submission introduced a domain-specific language for hierarchical, component-oriented sewing-pattern construction, with meaningful design parameters and body measurements separated from low-level geometry.[S02] Sewformer's first submission then addressed recovery of sewing patterns from daily photographs, using synthetic image-and-pattern pairs for training and evaluation.[S03] Both first submissions predate the 2024 text-guided and multimodal systems reviewed below.[S04][S08] A chronology that begins with images and discovers patterns only after agents arrive would erase these earlier structural contributions.
This distinction changes the adoption question. The useful question is not when AI became capable of making a garment, because that phrase hides unlike tasks. It is which representation a particular method receives, which artefact it emits, what its authors evaluated and which decisions remain unresolved.[S02][S09][S20] A parametric construction language, an image-reconstruction network and an appearance generator can all be described as garment AI while addressing different engineering boundaries. Counting them as one market would produce a denominator with no coherent meaning.
The chronology also has a selection boundary. This chapter reviews a purposeful set of technical and governance sources, not a systematic census of publications, products or deployments. First-submission dates show when a research claim entered the public record; they do not show when code became usable, when a revision changed the method or when any manufacturer adopted it.[S07][S20] Publication density cannot substitute for an adoption survey, and a source's presence in this paper cannot substitute for local qualification.
Exhibit 5 places the first submissions used in this chapter on one time axis. Its purpose is to make coexistence visible: parametric structure and image-to-pattern reconstruction appear early, while material, fit, schema and agentic methods join later. The axis records publication events only.
The timeline shows accumulation, not a relay race in which each approach replaces the last. Image2Garment still estimates geometry, but adds material attributes and physical-parameter prediction; EASE makes local material allowance an explicit design variable; DressAgent edits patterns through repeated simulation and judgement.[S11][S18][S27] These are different responses to different missing variables. The chart cannot establish that later methods are better at a shared task, because their inputs, outputs and evaluation settings differ. Nor can the spacing between publication events reveal commercial diffusion.
For a greenfield maker, the practical baseline is consequently wider than image ideation but weaker than a deployment claim. The research menu already includes inspectable structure, so a buyer need not treat a rendered garment as the only available interface.[S02][S09] At the same time, the menu contains research artefacts whose local code, data, licences and operating behaviour still need inspection. The chronology justifies a structured evaluation, not a purchase forecast.
2.22 min · 5 paragraphs · read with a related exhibit
Text guidance reached explicit sewing representations
DressCode joined natural-language guidance to two distinct outputs: SewingGPT generates sewing patterns with text guidance, while a separate Stable Diffusion branch generates tile-based physically based rendering textures.[S04] Its stated target is CG-friendly garments through natural-language interaction, with pattern completion and texture editing supporting the design process.[S04] That combination matters because a sewing representation and a surface appearance can be produced within one research framework without becoming the same artefact. A texture can describe the rendered surface while leaving panel dimensions, seam allowances and production tolerances unresolved.
The paper's production language therefore needs an artefact boundary. A text prompt expresses intent. A generated sewing representation encodes candidate construction information. A rendered result presents an appearance for review.[S04][S09] The three can be linked in a workflow, but approval of one does not automatically approve the others. A designer may accept the rendered collar proportion while a technician rejects the corresponding panel relationship. Conversely, a structurally valid pattern may produce an appearance that the designer did not intend. The research output becomes useful only when the review route preserves those separate decisions.
Garment3DGen illustrates a different route. It starts from a base mesh and an input image, uses image-to-three-dimensional generation as pseudo ground truth, then deforms the template mesh while preserving mesh quality and topology for draping and simulation.[S05] This is not DressCode's explicit text-to-sewing-pattern route. A simulatable mesh can be valuable for visualisation without supplying an editable flat pattern or a factory tech pack.[S04][S05][S22] The word garment in both titles does not make their outputs interchangeable.
Three input-output cards make the distinction operational. DressCode receives text and emits sewing patterns plus rendering textures, leaving factory specification outside its demonstrated CG-friendly objective.[S04] Garment3DGen receives an image and base mesh and emits a textured simulation asset, leaving explicit sewing-pattern export outside the abstract's claim.[S05] Sewformer receives a daily photograph and predicts a sewing pattern after training on synthetic pairs, leaving the transfer from its evaluated setting to a maker's product and material records unresolved.[S03] Each card identifies a research contribution and a boundary; none supplies a comparative production score.
¶ 04 · 3 sources
Garment3DGen receives an image and base mesh and emits a textured simulation assetS05
This is why the chapter does not rank the methods by a single maturity number. A common score would require a common task, denominator and acceptance rule. The opened abstracts do not provide that shared protocol across text-guided pattern generation, template-mesh deformation and photo-based reconstruction.[S03][S04][S05] GFT can legitimately ask which artefact is needed next, then test the candidate for that artefact. It cannot infer factory readiness from the richness of a rendered result.
Multimodal models widened the interface to pattern systems
Step 1 of 5Record first submission
Exhibit 07 · illustrativeVersion dates change the meaning of a chronology
Record first submission
Record first submission. Starting point. Leads to Identify revision read (do not backdate features). · illustrative
The December 2024 cluster did not converge on one interface.
Identify revision read
Identify revision read. From Record first submission (do not backdate features). Leads to Capture artefact statement (code, data or none stated). · illustrative
Capture artefact statement
Capture artefact statement. From Identify revision read (code, data or none stated). Leads to Run local reproduction (only after execution). · illustrative
Run local reproduction
Run local reproduction. From Capture artefact statement (only after execution). Leads to Record local acceptance (only after defined review). · illustrative
Record local acceptance
Record local acceptance. From Run local reproduction (only after defined review). End point. · illustrative
Method and source · Exhibit 07
Illustrative GFT evidence workflow. S07 supplies the first-submission and revision-history example; S20 motivates contextual empirical evaluation. No arrow asserts that local reproduction or acceptance has occurred for HAIGEN or any other method in this chapter.
Unit: proposed evidence sequence. Status: illustrative. Sources: S07, S20. Illustrative figures are teaching examples, not measured factory results.
2.3 · the bodyExhibit 07 above; its figures are illustrative where marked.
The December 2024 cluster did not converge on one interface. AIpparel introduced custom tokenisation for sewing patterns and fine-tuned large multimodal models on text, images and pattern annotations for generation and editing.[S08] Design2GarmentCode translated images, textual descriptions, sketches or combinations into parametric pattern-making programs.[S09] ChatGarment fine-tuned a vision-language model to emit JSON containing garment descriptions and continuous numerical attributes, then used a programming parametric model to create sewing patterns.[S10] All three widen the input interface, but their intermediate artefacts expose different inspection points.
That difference determines where deterministic processing begins. In Design2GarmentCode, the learned model emits a program in a structured pattern-making representation; the program, rather than a raw image, becomes the object that can be inspected and executed.[S09] In ChatGarment, the learned model emits a JSON record, and the downstream parametric model constructs the pattern from its fields and values.[S10] AIpparel's abstract establishes prediction and editing of a custom pattern token sequence, but does not by itself establish the same downstream program-execution boundary.[S08] A procurement review should therefore name the generated representation and the decoder, compiler or interpreter that follows it.
Exhibit 6 extends this input-output reading across the principal methods in the chapter. It deliberately omits a common performance column. The table is a classification of documented artefacts, not a league table assembled from incompatible experiments.
The comparison shows why model names are poor units of procurement. One team may need an editable parameter file, another a pattern token for research, and another a complete refinement workflow.Exhibit 6 makes those choices visible without pretending that a texture, token, JSON object, program and agent trace can be ranked on one unexamined scale. The next step is a matched local task with the same brief, material and acceptance conditions, not a synthesis of unrelated headline results.[S20]
Dates need equal care. AIpparel was first submitted on 5 December 2024 and the version read was revised on 5 April 2025; Design2GarmentCode was first submitted on 11 December 2024 and revised on 9 April 2025; ChatGarment was first submitted on 23 December 2024 and revised on 3 April 2025.[S08][S09][S10] The first date locates the research origin. The revision date identifies the abstract actually read. Assigning every feature in the revised abstract to the original submission would create a false capability history.
¶ 05 · 3 sources
Design2GarmentCode was first submitted on 11 December 2024 and revised on 9 April 2025S08, S09, S10
HAIGEN supplies a longer revision example: its first submission was on 1 August 2024, while the version read for this chapter was revised on 27 July 2026.[S07]Exhibit 7 turns that distinction into a record-keeping rule. Publication, revision, local reproduction and local acceptance are separate events with separate evidence.
The flow prevents two common distortions. First, an old first-submission date must not be used to imply that the original version contained every later refinement. Second, a recent revision must not be mistaken for a recent factory deployment. The local reproduction and acceptance nodes remain empty until the maker has run and reviewed the method under its own conditions.[S20]
2.42 min · 6 paragraphs · read with a related exhibit
Materials and fit became explicit research targets
Later research also exposes variables that an attractive garment image leaves unstated. Image2Garment addresses the absence of material properties in geometry-only prediction by inferring material composition and fabric attributes, then mapping those attributes to physical fabric parameters through a predictor trained on a small dataset of material-physics measurements.[S11] FIT addresses a different omission: appearance-driven virtual try-on can depict a garment as well fitted without adequately representing the person's and garment's sizes.[S13]EASE addresses yet another: local material allowance is often a byproduct of geometry or simulation rather than an independent design variable.[S27] These contributions should not be collapsed into a general claim that models now understand garments.
¶ 01 · 3 sources
Image2Garment addresses the absence of material properties in geometry-only prediction by inferring material composition…S11
An input-output card keeps the first boundary clear. Image2Garment receives a single image and produces simulation-ready garment estimates that include inferred material information and predicted physical parameters.[S11] Its research contribution is the connection between visual attributes and simulation inputs. Its limitation for a maker is equally specific: an inferred composition or parameter is not a measurement certificate for the fabric actually purchased. The small measurement dataset grounds the research method, but does not turn every subsequent image-based estimate into a local material observation.[S11]
¶ 02 · 1 source
Image2Garment receives a single image and produces simulation-ready garment estimates that include inferred material…S11
FIT receives the virtual try-on problem as its research boundary rather than treating it as solved by image realism. The authors introduce synthetic try-on triplets accompanied by body and garment measurements, including ill-fit cases created through programmatic garments and physics simulation.[S13] The output is a dataset and a fit-aware baseline model, not a physical fit approval for a wearer. Its importance lies in evaluation design: deliberately mismatched sizes make a previously hidden failure visible. It does not follow that every commercial try-on system has the same failure or that the new baseline resolves comfort, movement or buyer acceptance.[S13]
EASE begins with a parametric body surface and represents ease as spatially varying, anisotropic per-triangle scales. It then optimises sewing patterns intended to preserve the specified ease while satisfying geometric and seam constraints.[S27] This makes ease an editable input rather than merely an outcome observed after simulation. The capability does not establish which ease distribution a Cameroonian wearer population prefers, nor whether a chosen fabric and activity will feel comfortable. Those remain product and physical-validation questions rather than transferable accuracy claims.[S27]
The three cards therefore answer different questions. Image2Garment asks how an image might inform material and simulation parameters. FIT asks whether size information and ill-fit examples enter try-on evaluation. EASE asks how a designer can specify and transfer local allowance.[S11][S13][S27] A combined accuracy league table would erase these distinctions. It would also hide the difference between inferred material properties, synthetic fit data and an explicit design representation.
For GFT, the chronology supports a more modest inference: research has made missing variables easier to name and test. A local evaluation should carry each variable into its own evidence field, with the source of the value, the evaluated case and the unresolved physical check recorded separately.[S20] Material estimation can propose a swatch test, fit-aware data can inspire matched and mismatched cases, and explicit ease can inform a specification review. None of these research results replaces the corresponding local evidence.
73.3%Error-free digital assemblyFully resolved test patterns divided by all test patterns
01 / 03
Read-out
Method and source
Sourced from AutoSew full-text sections 8.1 and 8.2. Total and multi-edge metrics concern stitch correspondences on the authors' test set. Garment sewn percentage is fully resolved test patterns divided by all test patterns. The abstract rounds total F1 to 96 percent. These are digital benchmark results, not physical sewing yield or GFT performance.
Unit: percent, with different denominators. Status: sourced. Sources: S12.
2.52 min · 6 paragraphs · read with a related exhibit
Structure and agentic refinement address different failure modes
PatternGSL and GarmentWeaver make structure the immediate object of generation, while DressAgent makes iterative refinement central. These are complementary research directions, not successive labels for the same capability. PatternGSL defines a template-free specification language containing panel boundaries, parameterised seams and explicit stitch topology, then decodes predicted specifications with lightweight deterministic validity handling.[S14] GarmentWeaver responds to flat long sequences that entangle garment structure with detailed parameters by constructing hierarchical targets and applying feasibility-aware regularisation.[S16] DressAgent addresses inverse design through planning and a closed loop of pattern editing, physical simulation, and visual or measured judgement.[S18]
The failure modes differ. PatternGSL targets a representation gap between surface reconstruction and structured garment construction.[S14] GarmentWeaver targets redundant components, inaccurate local details and poor simulation compatibility associated with its authors' account of flat sequence models.[S16] DressAgent targets the difficulty of recovering layered outfits from an image, including layer order, coarse pattern estimation and fine-grained refinement.[S18] A schema can make an invalid relationship easier to detect; an agent can propose another edit after inspecting a simulated result. Neither mechanism alone establishes that the final garment satisfies a production brief.
There is also a control distinction. Deterministic validity handling applies defined rules during decoding, whereas an agentic loop chooses further actions on the basis of tools, critiques and memory.[S14][S18] The first can reject or repair a specified class of structural conditions without proving design intent. The second can improve alignment with a reference under its evaluated protocol without gaining authority to approve a pattern. A local pilot should inspect both the structural error log and the agent's action history rather than compressing them into a single success label.[S20]
Public-availability statements require the same precision as technical claims. The PatternGSL abstract says that code and data-processing scripts will be released, which is a promise recorded at the accessed version, not evidence that this lane installed them.[S14] The GarmentWeaver and DressAgent abstract pages read for this chapter contain no code-release statement.[S16][S18] That absence does not prove that no artefact exists elsewhere; it means availability remains unverified in the source boundary used here. By contrast, the Sewformer and ChatGarment abstracts explicitly state that code and other artefacts are available.[S03][S10] Even those statements do not prove that a particular revision runs, that its licence permits the intended use or that its output passes a local CAD readback.
A claim ledger should consequently use separate labels: code stated as available, code promised, no release statement in the source read, package retrieved, package executed and output accepted. The first three describe publication evidence. Retrieval and execution describe subsequent work. Acceptance describes a decision under local requirements. Treating a project link or a future-release sentence as a verified installable package would skip most of that evidence chain.[S20]
The recent agent wave therefore changes the research menu without invalidating earlier structure. A generated program can be the object an agent edits; a schema can constrain what that edit may contain; simulation can supply evidence for another iteration.[S09][S16][S18] The adoption question is whether the combined chain works on the maker's cases with acceptable corrections and approvals. This chapter did not execute these systems, so it reports their stated mechanisms and availability language only.
Commercial documentation establishes a narrower fact than factory success
Step 1 of 5Research abstract
Exhibit 08 · illustrativePublic availability and local suitability require separate checks
Research abstract
Research abstract: Publicly inspectable evidence increases 1.5, Verification in intended workflow increases 0.5. Quadrant: Unresolved on both axes · illustrative
Vendor documents answer different questions from research abstracts, and both differ from local acceptance.
Code statement
Code statement: Publicly inspectable evidence increases 3, Verification in intended workflow increases 1. Quadrant: Unresolved on both axes · illustrative
Terms reviewed
Terms reviewed: Publicly inspectable evidence increases 5, Verification in intended workflow increases 2. Quadrant: Visible but not locally verified · illustrative
Illustrative GFT teaching model informed by S20's evaluation logic, S22's documented CAD controls and S31's vendor-specific use conditions. Coordinates are didactic positions for generic evidence states, not measured scores for a method or product. Unknown licence, runnable-code, export and acceptance fields remain unknown and are not plotted.
Unit: illustrative evidence-state coordinates. Status: illustrative. Sources: S20, S22, S31. Illustrative figures are teaching examples, not measured factory results.
2.6 · the bodyExhibit 08 above; its figures are illustrative where marked.
Vendor documents answer different questions from research abstracts, and both differ from local acceptance. CLO's technical documentation lists Standard DXF, AAMA and ASTM options, together with controls for units, grading, notches, seam allowances and the relationship between cutting and sewing lines.[S22] This establishes documented exchange functionality at the page's stated update. It does not establish that a file generated by a research model will reopen correctly in the maker's receiving CAD release, nor that grading and annotations will survive a particular round trip. Those are testable interoperability questions, not implications of a format list.[S22]
Adobe's Firefly FAQ states that outputs from features without the beta label may be used in commercial projects, with beta features subject to their stated conditions.[S31] That is a vendor-documented use condition for the identified service context. It does not prove that a generated garment design is non-infringing, that every partner model has identical terms or that the design is manufacturable. A procurement record must identify the actual feature, model, plan and terms reviewed rather than transferring one FAQ sentence to an entire toolchain.[S20][S31] This is evidence discipline, not a legal clearance or legal advice.
Exhibit 8 separates public inspectability from verification in the intended workflow. The points are generic evidence states, not scores assigned to any named research system or vendor. A method whose licence, runnable package or buyer acceptance is unknown must remain unknown rather than receiving a favourable coordinate by assumption.
The matrix deliberately leaves a large distance between a public statement and an accepted outcome. Reading an abstract can establish a claimed mechanism. Reviewing terms can establish what a particular document permits. Reopening an export can establish that specified geometry and annotations survived the tested exchange. Buyer acceptance records a different decision again.[S20][S22][S31] The exhibit cannot show how frequently any organisation has completed these steps because the source base contains no such census.
The pack should also preserve refusal conditions. If the vendor cannot supply an export specimen, the team cannot claim exchange readiness. If data-handling terms remain unresolved, proprietary blocks and buyer material should remain outside the service. If the support commitment does not identify the release tested, a later update requires a new check. These are proposed GFT controls derived from the evidence gaps, not assertions about any vendor's current performance.
¶ 05
2.74 min · 1 sub-steps · read with a related exhibit
A claim ledger prevents research results becoming sales promises
Related · chapter 1310 paragraphs step it
Related exhibit 53 · chapter 13FlowillustrativeExpansion requires every critical handoff to pass
01 / 08
Read-out
Method and source
GFT proposed qualification route informed by NIST contextual evaluation and lifecycle monitoring, plus vendor-documented CAD exchange controls. Arrows show required pass conditions. A failure returns to the relevant owner; it does not advance. Physical material and fit requirements are product-specific. No threshold, local result or automatic scale-up is asserted.
Unit: illustrative evidence and decision sequence. Status: illustrative. Sources: S19, S20, S22. Illustrative figures are teaching examples, not measured factory results.
The main risk in a fast-moving research review is not only technical error. It is a change of meaning as a claim travels. An author's demonstrated benchmark becomes a vendor's general capability statement, then a sponsor's assumed factory result. NIST's generative AI profile instead calls for contextual evaluation, empirical capability checks, source verification and lifecycle monitoring.[S20] Applied here, that discipline requires every statement to retain its evidence state and intended boundary. A research result can justify a test. A vendor document can justify a narrower procurement question. Neither can silently become a locally accepted result.
A useful ledger begins with the publication event. Record the method title, first-publication date, exact version read, revision date and stable source location. The first date supports the chronology; the version identifies what was actually reviewed.[S07][S08] Add the publication venue as stated by the source, but do not treat a conference reference or journal reference as local reproduction. PatternGSLData and GarmentWeaver, for example, can occupy the same research timeline while having different revision histories and availability statements.[S14][S16]
The technical entry should then record the input, output, intermediate representation and deterministic downstream component. DressCode's texture branch should not be merged with its sewing-pattern branch, and ChatGarment's JSON should not be confused with the pattern constructed from it.[S04][S10] The evaluation entry needs the dataset or setting, unit of evaluation, comparator and limitation stated at the level actually read. Where only an abstract was reviewed, the ledger should say so. It should not invent a sample size, protocol detail or confidence interval that the opened text did not supply.
Availability forms another group of fields. Record whether the source states that code is available, promises a future release or makes no release statement, and preserve the sentence and access date.[S03][S14][S16] Separately record whether the team retrieved the artefact, checked its licence, installed it, executed it and retained the output. A link is not an execution log. An execution log is not a garment approval. This separation makes reproducibility work visible instead of allowing the word available to carry unsupported assurance.
The local entry belongs to the maker rather than the paper's authors. It should identify the illustrative or real product brief, approved block, material record, model configuration, operator role, corrections, receiving-CAD result, physical checks and final reviewer.[S20][S22] If those fields have not been populated, the honest status is not ready or not adopted. It is untested in the intended workflow. That status can coexist with a strong published result because the two claims answer different questions.
This worked example also clarifies what an adoption estimate would require. The research unit would need a defined population of organisations, a sampling method, an observation date and a distinction between awareness, trial, routine use and production release. The numerator would need verified instances of the chosen adoption state, and the denominator would need eligible organisations rather than papers or products. The sources opened for this chapter supply no such market sample. They support a chronology of methods and a set of local test questions, not an industry adoption rate.[S02][S20][S31]
2.8 Each evidence state should permit a different action
A claim ledger is useful only if it changes decisions. GFT can allow a documented research mechanism to enter a test backlog when its input and output match a defined need. It can allow vendor-documented functionality to enter a procurement comparison when the exact release and terms are captured. It should require local execution, correction records and receiving-workflow evidence before calling a method operationally suitable.[S20][S22] Local acceptance should remain a separate decision by the accountable reviewer, with unresolved material, fit, rights or geometry issues returned to their owners rather than averaged away.
The same rule applies to chronology. An early first submission proves precedence for the documented research idea, not present superiority. A recent revision proves what the current record says, not that the capability existed at the earlier date. A code promise indicates intent at the accessed version, not reproducibility. An agent trace can show which edits and simulations occurred, but it cannot authorise a cutting order.[S07][S14][S18] Keeping these meanings separate is more useful than declaring one wave of methods victorious over another.
For GFT's greenfield apparel context, the defensible recommendation is to maintain a versioned research register and use it to select bounded tests. Include structured sewing methods from 2023 alongside later multimodal, material, fit, schema and agentic approaches.[S02][S03][S11][S13][S16][S18] Require common local tasks before comparing outcomes, and require local acceptance before describing adoption. The present evidence justifies curiosity with controls. It does not justify a market-share figure, a universal factory-readiness claim or an investment, legal or tax conclusion.
Check the record
The chapter keeps its sources within reach.
Every knot is a source this chapter cites; select one to read its record, or filter the register by grade. Publication dates and inherited-source limits stay explicit. Read the paper's full evidence summary.
18 sources · 136 citation marks on this pageMost cited: S20, 15 times
Grade AGrade BGrade CKnot size: citations on this page
All 18 records shown
R30 · Grade C · inherited record
Design Journal (Taylor and Francis)
Inherited evidence R30
Generative AI in apparel 2023-2024 mainly design-side image generation (Midjourney, Stable Diffusion) across style, silhouette, colour and pattern.
Publication date unrecorded. Inherited source-text record. The original publication has not been independently reopened for this web edition.
DressCode: Autoregressively Sewing and Generating Garments from Text Guidance
We first introduce SewingGPT, a GPT-based architecture integrating cross-attention with text-conditioned embedding to generate sewing patterns with text guidance.
2024-01-29. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
PatternGSL: A Structured Specification Language for Template-Free and Simulation-Ready 3D Garments
PatternGSL preserves the physical rigor of pattern-based models while removing template dependence, elevating sewing structure as a first-class target for generative modeling.
2026-06-23. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Move the shuttle along the rack to preview any chapter: its sections, exhibits and reading time. Draft web edition. This research is not investment, legal or tax advice; illustrative models are not measured factory results.
The paper's rack · 14 boltsBolt length: reading time
1.1
1.3
1.5
1.7
1.9
1.11
1.13
01Part I: Production readiness is the test
A convincing image cannot authorise a cutting order
GFT should buy creative assistance selectively and release garments only through an accountable specification process.
1.1Local value requires producible garments
1.3A design image omits the instructions a factory needs
1.5The greenfield programme defines the adoption sequence
1.7Research prototypes and released products answer different questions