Rights and model risks need versioned records

The World Intellectual Property Organization (WIPO) describes traditional cultural expressions as integral to the cultural and social identities of indigenous and local communities, embodying know-how and skills and transmitting core values and beliefs.[S24] Its fashion guidance promotes dialogue between Indigenous Peoples and fashion companies to shape fair and equitable interaction and warns against harmful uses without consent.[S23] These institutional explanations support careful engagement; they do not identify a representative authorised to approve a particular Cameroonian motif, such as Grassfields ndop resist-dyed geometry. The fashion page is dated 2 November 2023; the traditional-cultural-expressions page displays no publication date. Both were reopened on 30 October 2026; neither is a new statute.[S23][S24]

GFT proposes a cultural-reference record whenever the design brief intentionally draws on an identifiable tradition or community expression. It should describe the reference, its source, the intended garment application and the proposed public account of its origin. The maker should then establish who should be consulted and what evidence supports that identification.[S23][S24] A photograph credit, a retailer's description or a model's fluent summary should not be substituted for that investigation. Where authority remains contested or unclear, the unresolved position should be visible to the release reviewer.

Similarity screening has a limited role in this proposed workflow. It can be used as a search aid to identify visual references for further review.[S20] GFT should not assign it authority to decide cultural permission. A low similarity result should not close an engagement question, and a high similarity result should prompt examination of the actual expression, context and intended use.[S23][S24] The review should preserve the search scope and limitations so that an incomplete search is not later described as comprehensive clearance.

For a culturally referenced shirt surface, GFT recommends linking any consultation record directly to the specific artwork revision and placement map shown during dialogue.[S23][S1103] A general discussion about a collection should not automatically approve every generated variation or colourway. The record should distinguish permission to study a reference, approval to adapt it, approval to manufacture, and agreement about public attribution.[S23] Proposed benefit arrangements, restrictions and review opportunities should be retained where relevant. These are recommended questions for a responsible process, not invented terms attributed to any community.

GFT's proposed engagement record should also make room for refusal, limited permission and a request for further discussion. A design programme should not record only favourable outcomes or treat participation in a meeting as endorsement. The responsible role should document the response accurately and identify which changes (such as altering motif proportions, crossing seam joins or changing garment category) require renewed contact.[S23][S24] Reusing an approval requires matching its scope.

The same record should govern the language accompanying the garment. GFT recommends reviewing claims such as authentic, traditional or community-approved against the actual agreement and evidence.[S20][S23] A designer's interest in an expression is not evidence of provenance for the product. The maker should preserve the distinction between inspiration, authorised collaboration and independently verified origin. If no adequate account can be supported, the public description should be revised or the cultural reference removed through the documented review process.

Community engagement also needs appropriate information handling. The proposed record should capture the decision and authorised terms without placing restricted stories, images or correspondence in an unrestricted asset library.[S20][S24] GFT recommends agreeing what may be retained and shown to technical partners, then carrying those limits into subsequent generation and publishing workflows. A later supplier should receive only the material and permissions required for its role.

CLO's exchange documentation lists Standard DXF, AAMA and ASTM options that include units, grading, notch handling and cutting or sewing lines, while its CONNECT fabric documentation requires entering weight and thickness alongside visual maps.[S22][S32] These pages establish documented interface fields, not a verified exchange between the maker's chosen software versions or laboratory-validated fabric physics. GFT therefore recommends a sample export, material metadata check and receiving-system inspection as procurement evidence.[S22][S32] This chapter defines what evidence procurement should retain and who must inspect it.

The proposed procurement pack in Exhibit 47 converts broad assurances into inspectable requests. Its reviewer labels are responsibilities, not GFT appointments or headcount. Its hold conditions are proposed gates for the intended workflow, not allegations about any supplier.

GFT recommends retaining the supplier's response in its original dated form (including exported DXF files, contract schedules and policy snapshots) alongside the maker's assessment.[S20][S22] A demonstration recording should identify the configuration and permitted sample material. An answer that references a beta feature, a different model or another account class should remain pending for the intended use.[S31] Procurement should distinguish evidence received from evidence inspected and evidence accepted. A complete folder is not an accepted workflow if nobody with the relevant responsibility has reviewed its contents.

The technical inspection should ask whether the receiving team can open the sample, identify units, recover required annotations and edit the intended objects, while confirming that material records separate measured values from estimates.[S22][S32] GFT proposes recording discrepancies against the supplier's claimed capability and the maker's acceptance conditions. A visually convincing three-dimensional preview should not close a two-dimensional DXF editability requirement.[S10][S22] If a proprietary format is used during generation, the exit review should establish what usable industrial exports remain when access ends and whether those files have actually been reopened.[S22]

Commercial review should examine the relationship between policies, the agreed contract and operational settings. GFT recommends asking how model substitutions are disclosed, which support activities may expose uploaded material, and how an incident should be raised.[S20][S31] Pricing remains unresearched here and requires formal quotes before Chapter 12 and Chapter 13 pilot evaluations. The procurement record should not imply that a trial account's features or permissions apply to a future production arrangement.[S31]

Finally, the maker should assign an owner to each pending request and connect it to a decision consequence. Missing export evidence may block technical qualification while allowing a limited ideation exercise with authorised public material.[S22][S31] Unknown upload terms should block sensitive uploads regardless of a successful export demonstration.[S20] Recording those boundaries explicitly ensures that enthusiasm for a demonstration cannot expand the permission granted.

GFT proposes a response record for a rights concern, an unintended confidential upload, a corrupted pattern export, a misleading material statement or an escaped specification error.[S20][S22][S23] The NIST generative-AI profile includes lifecycle monitoring, incident-related actions and information-security considerations.[S20] The response design here is GFT's apparel-specific proposal; it is not a certification, regulatory acceptance or claim that such an incident has occurred in GFT operations.

The first record should preserve the reported concern, time identified, reporting route, affected style and revision identifiers, and current release state. A report should trigger an immediate trace of the provenance envelope without converting an initial allegation into an established legal finding.[S20][S1103] GFT recommends distinguishing suspected cause, confirmed observations, containment action and unresolved scope. The responsible role should identify the relevant generated outputs, human-edited descendants, specification revisions and external recipients.[S15][S1103] Where the dependency trail is incomplete, that limitation should inform the hold rather than disappear from the report.

Containment should match the event. The proposed workflow suspends the affected upload route, holds the disputed artwork, quarantines the corrupted DXF export or stops use of the affected specification as appropriate.[S21][S22][S23] It identifies which unaffected work can continue and why. For an unintended external disclosure, the team must establish the destination and contractual remediation process; restoring an earlier local model version cannot undo an external transmission.[S20][S31] Required notifications and legal duties need project-specific authority rather than assumptions here.

Correction must produce a new identifiable revision.[S15][S1103] GFT recommends retaining the original evidence in a restricted archive under approved retention rules, recording the corrective change and identifying the test needed to reopen the gate. Replacing a file in place leaves downstream users unable to distinguish superseded instructions from current ones. An export or seam defect requires clean receiving-system readback of the new revision, while a rights concern requires documented resolution or an independently created replacement rather than superficial re-prompting.[S12][S21][S22][S23]

Learning should then return to the workflow. The maker should decide whether to add a permanent regression case, change an upload class, revise a supplier condition or refine technician training from Chapter 10.[S15][S19][S20] Repeated exceptions should be tracked in GFT's proposed risk-matrix tool so recurring control failures remain visible across styles. A small team can allocate these duties across existing roles, provided the record separates who proposes a correction from who accepts its release.

The chapter's boundary remains the accepted design and specification. Broader model operations belong to companion paper WP14 and applicable legal duties belong to companion paper WP17, connected through the same revision identifiers.[S19][S20] Within WP10, these versioned records form a prerequisite for Chapter 12's economic model and Chapter 13's pilot qualification. GFT's recommendation is practical: make the permission decision, processing route and technical release reconstructable before expanding generated design work.