Skip to content
GREEN FUTURETECH.
Explore
Garment serialREACHEDCut bundleREACHEDFabric rollREACHEDYarn lotBEYOND THE BREAKCotton baleBEYOND THE BREAKGin lotBEYOND THE BREAK

GFT instruments / Cotton provenance

Pull the thread.
Find the break.

Pull the thread through a simulated custody chain. The illustrative default reaches the fabric roll, then stops at a missing yarn reference. Repair a record and see what reconnects.

DEFAULT SCENARIO / ILLUSTRATIVE CHAIN2 of 5 parent links followed • Stops at fabric roll
Operate the instrumentProcedural visualisation. Schematic, not a facility.
Thread

2 of 5 links followed. Stops at the fabric roll.

Operate the illustrative custody records

An instrument for the decision / illustrative records

Can this garment be traced back to its cotton?

A label is the start of a trace.

Follow the recorded chain backwards. The default example stops at the fabric roll because its yarn input was not recorded. Repair that reference or remove another field to see how the boundary moves. Change the inputs, read the result, keep the assumptions visible.

Choose a starting condition
SIMULATION
No supplier data
Read from the garment towards cotton

Trace stops at the fabric roll.

CHAIN INTERRUPTED
BREAKGarment serialREACHEDCut bundleREACHEDFabric rollREACHEDYarn lotBEYOND BREAKCotton baleBEYOND BREAKGin lotBEYOND BREAKBREAKGarment serialREACHEDCut bundleREACHEDFabric rollREACHEDYarn lotBEYOND BREAKCotton baleBEYOND BREAKGin lotBEYOND BREAK
Reached from garmentBroken local linkBeyond trace boundary

Two of five parent links can be followed from the garment. A missing fabric parent prevents the next step.

Inspect the event, then test a change

Every handover needs a record.

Select a custody stage

This selects a record. It does not change the trace result.

Fabric roll / captured fields

Untick a field to simulate its absence. The displayed values are fictional. A tick checks presence, not authenticity.

Edit the identifiers

Try a wrong parent reference. Filled fields alone cannot repair a mismatched link. No real supplier identifiers are needed.

Method / a chain is stronger than a filled form

Follow references,
then check context.

Six records, five parent joins, read from the garment upward. Each step below lights a different part of the chain.

Garment serialCut bundleFabric rollYarn lotCotton baleGin lotNO PARENT REFERENCE
  1. Garment serialDEMO-SERIAL-A
  2. Cut bundleDEMO-CUT-A
  3. Fabric rollDEMO-ROLL-A
  4. Yarn lotDEMO-YARN-A
  5. Cotton baleDEMO-BALE-A
  6. Gin lotDEMO-GIN-A
Join
events = 6parent links = 5
gin.parent_id = nonereach(gin) means: a recorded lot, not a farm
usable(e) = id ∧ operator ∧ location ∧ time
cut.parent_id = DEMO-ROLL-Afabric.id = DEMO-ROLL-A ✓ match
time(fabric) = 2026-01-13time(cut) = 2026-01-14 ✓ parent ≤ childlink = usable(child) ∧ usable(parent) ∧ child.parent = parent.id ∧ time(parent) ≤ time(child)
fabric.parent_id = (missing) ✗reach(gin) = reach(bale) ∧ link(bale, gin)traversed = 2 of 5
review fields: material, evidencea gap is counted, the link stays
40 + 1 = 41 fields4 + 1 = 5 links

01 / Records

Six ordered records, one parent each.

This model holds an ordered record for each stage: gin lot, cotton bale, yarn lot, fabric roll, cut bundle and garment serial. Each stage has an output identifier. Every stage after the gin also has a parent identifier naming the material it used.

INSPECT RECORD CHAIN6 stages / 5 parent links

Fabric roll: output=DEMO-ROLL-A • parent_id=MISSING (break)

02 / Boundary

The gin is the upstream boundary.

The gin is the upstream boundary of this exercise. It has no parent field here, so reaching it cannot establish farm origin.

TEST UPSTREAM BOUNDARYGin lot vs farm origin
farm: not recorded

Gin lot (DEMO-GIN-A): recorded boundary. Has output ID, operator, place and UTC time, and no parent field.

03 / Usable

Usable means four core fields.

A locally usable event has an output identifier, accountable operator, location and valid event time. The model treats these as core fields for a credible handover.

TOGGLE CORE FIELDS4 of 4 present • USABLE

usable(e) = id ∧ operator ∧ location ∧ time (all 4 core fields present)

04 / Join

The child must name its parent.

A child links to its parent only when both events are usable and the parent reference matches the parent's output identifier. These are deliberately explicit GFT simulation rules, informed by GS1 event dimensions. They are not an EPCIS validation schema.

TEST PARENT JOIN
cut bundle (child)parent_idDEMO-ROLL-Afabric roll (parent)output idDEMO-ROLL-A

✓ MATCH: cut.parent_id (DEMO-ROLL-A) = fabric.id (DEMO-ROLL-A)

05 / Order

Time cannot run backwards.

The parent's timestamp must be no later than the child's. Together the four tests make one local link.

CHRONOLOGY SCRUBBERparent ≤ child • VALID
2026-01-13fabric roll (parent)2026-01-14cut bundle (child)

time(fabric) 2026-01-13 ≤ time(cut) 2026-01-14 • Chronology holds

06 / Stop

Traversal stops at the first failed test.

Traversal starts at the garment and stops at the first failed test. A healthy link further upstream remains visible but cannot bypass the break. This distinction matters: counting filled rows could produce a comforting total while the garment's actual path remains disconnected. Repair the nearest break, recalculate, then inspect any further interruption that becomes reachable.

INSPECT 5 CUSTODY LINKSStops at Link 3

Link 3 (Fabric -> Yarn): FIRST FAILED TEST (stops trace at 2 of 5 links)

07 / Context

Then check context.

Material descriptions and evidence references are also counted. Their absence triggers a review gap but does not alone sever an identifier link. This prevents the tool from confusing record connectivity with documentary completeness. A linked chain with missing evidence is still a chain needing investigation.

TEST REVIEW FIELDSLink kept • Gap counted
Identifier link status: CONNECTED

2 documentary review gaps flagged; custody identifier link remains connected

08 / Accounts

The accounts must balance.

The field reconciliation is captured fields plus missing fields equals applicable fields. The root parent is excluded. The link reconciliation is valid local links plus broken local links equals all modelled parent links. These checks detect accounting mistakes; they do not reveal fraudulent entries.

RECONCILIATION BALANCE40 + 1 = 41 fields
fields40 + 1 = 41
links4 + 1 = 5

Reconciled: 40 captured + 1 missing = 41 applicable fields (root parent excluded)

Assumptions register / visible by design

The examples are fictional;
the rules are explicit.

Default values, station ties and verification status of each assumption
Input or ruleThread tie & basisStatus & weightTest it
Custody stagesGin, bale, yarn, fabric, cut and garment. A simplified production path specified for this instrument.If it fails: Six stations and five parent links exist only inside this scope.Illustrative scopeReference only
Identifiers, people and sitesDEMO-prefixed records, fictional teams and locations. No named supplier or facility is represented.If it fails: A wrong parent reference severs a link even when every field is filled.Illustrative
Event datesConsecutive example dates in January 2026, one event per stage. Chosen to make chronology readable, not to model lead time.If it fails: A parent event dated later than its child severs the link.Illustrative
Material descriptionCotton in a single-source stream. There is no blend fraction or mass allocation.If it fails: A blank description is counted as a review gap. It does not sever the link.Illustrative
Missing fabric parentThe initial scenario clears the fabric roll's parent field. Every other example field starts present.If it fails: The fabric roll cannot name its yarn lot, so the trace stops at the fabric roll.Illustrative fault
Core event dimensionsIdentity, event time, place and business context inform the model. Operator and parent checks are this instrument's rules.If it fails: A missing identifier, operator, location or time makes an event unusable.GS1 context ↗
Passport-style review fieldsMaterial and evidence references prepare a discussion about provenance. Actual requirements depend on the relevant product rules.If it fails: Counted as review fields. No legal deadline or mandatory field list is asserted.Commission context ↗Reference only
A usable eventAn output identifier, accountable operator, location and valid event time.If it fails: Without these four fields no link can start or end at that event.GFT model ruleReference only
A connected parentBoth events usable, the parent reference equals the parent's output identifier, and the parent's time is no later than the child's.If it fails: Fails on the first of the four tests that does not hold.GFT model ruleReference only
TraversalStarts at the garment and stops at the first failed test. Healthy links upstream cannot bypass it.If it fails: The depth reported is the number of links followed before the first failure.GFT model ruleReference only
Blends, splits and mass balanceNot modelled. The chain is single-parent and identity-preserved.If it fails: Real spinning and cutting create many inputs and outputs. This chain cannot show them.Open, not modelledReference only
Authentication and certificationNot tested: physical segregation, signatures, certificate issuers, registry queries, farm-level origin.If it fails: A complete chain is an information design result, not certification.Open, not modelledReference only

Use the break to allocate work

Recover a record
before buying a platform.

Choose who is reading the break
Garment serial2026-01-15Cut bundle2026-01-14Fabric roll2026-01-13Yarn lot2026-01-12Cotton bale2026-01-11Gin lot2026-01-10

Factory manager

Find the missing handover.

Recover: the yarn lot named by the fabric roll

Assign the nearest break to the team that owns that transformation. Recover the source production record, check the material reference and retain who made the correction. A completed screen is not a substitute for a supported correction. Recheck adjacent stages because a repaired identifier may reveal an older gap.

Investor

Test the operating process.

Recover: the input lot and its evidence, at every station

Ask to see evidence for the sample chain rather than a total number of tags issued. A supplier can serialise finished garments while retaining weak upstream records. Test whether teams can retrieve the input lot, locate its supporting evidence and explain exceptions before relying on traceability in diligence.

Engineer

Design for exceptions.

Recover: the splits and blends this chain cannot show

Specify identifier ownership, capture points, timestamp handling and correction history before choosing an interface. Real spinning and cutting create many inputs and outputs. A production system must represent split lots, blends, rework, losses and custody changes without forcing them into this single-parent chain.

BOUNDARY NOTE / INFORMATION DESIGN VS PHYSICAL VERIFICATION

Limitations: this simulation does not reconcile mass, test physical segregation, validate signatures, verify certificate issuers, query a passport registry or authenticate the truth of a supplied record. It excludes chemicals, trims, packaging, transport events and farm-level origin. A complete chain is an information design result, not certification, a sustainability score, or legal, tax or investment advice.

Source register / opened for this instrument

Keep standards context
separate from scenario rules.

Choose a source to see the rules it informs

Modified 30 May 2025. Describes event-based visibility and the identity, time, location and business context of an event. The simulator borrows that structure and adds its own simplified traversal rules.

Open the source ↗

Live guidance. Describes product-specific passport information, including origin and materials. This page makes no claim about a textile implementation deadline or a complete mandatory field list.

Open the source ↗

Operator continuity, parent match, chronology and first-failure traversal are this instrument's own explicit rules. Nothing here is an EPCIS validation schema.

Which chain fields each source informs5 of 72 of 72 of 7 lit
  1. GS1IdentityGarment serial IDEvery event has an output identifier.
  2. GS1Event timeCut bundle UTCEvery event has a valid UTC time.
  3. GS1LocationCotton bale siteEvery event has a place.
  4. GS1ECBusiness contextYarn review fieldsMaterial description and evidence reference, counted as review fields.
  5. ECProduct-specific informationGin lot contextOrigin and materials as passport-style review prompts.
  6. GFTAccountable operatorAll 6 operatorsA named team stands behind each handover.
  7. GFTParent matchFabric -> Yarn joinThe child's parent reference equals the parent's identifier.
  8. GFTChronologyFabric <= Cut timeA parent event is never later than its child.
  9. GFTFirst-failure traversalStops at Fabric (#3)The trace stops at the first failed test.

Interactive rule inspector / highlights the matching link

The model stays visible.

Four tests per link, one record per stage. Select a model test below to highlight the custody link and station it governs on the thread.

Active rule on the custody thread

child.parent_id = parent.id

Fails at Link 3 (Fabric roll -> Yarn lot): DEMO-ROLL-A has an empty parent_id field.

Read the full method

Follow the garment's parent reference upstream. Each link needs matching identifiers, accountable operator, location and event time; parent events cannot be later than their child. Missing material descriptions and evidence references are counted separately. This is an illustrative single-parent model, not proof of physical origin.

Method source

GS1 event dimensions, European Commission passport guidance and GFT illustrative model rules. ↗

A planning aid. Not investment, legal or tax advice. Verify inputs and boundaries before an operational decision.

Source receipts, exact short quotations and qualifications are available in the source register JSON. No programme production figure is used in this model, so there is no sourced GFT programme-default preset.

Continue along the spine / papers and companion instruments

Four extensions tied to this thread.

Selected extension • Garment -> Gin chain

Examines custody handovers, identifier granularity and passport data boundaries across the full cotton-to-garment path.

  1. Garment -> Gin chainWP05 / Traceable by Design ↗

    Cotton provenance, custody and product passports.

  2. Factory data spineWP14 / The Industrial Data Spine ↗

    Ownership and governance of factory data.

  3. Station capture nodesEdge architecture instrument ↗

    Plan the capture layer behind the record.

  4. Line shift boundaryOEE line instrument ↗

    Test another production measurement boundary.

Use the result in its boundary

A connected record still needs corroboration.

The instrument demonstrates where information stops. Use it to discuss data collection with suppliers, production teams and technical reviewers before selecting a passport platform.

Read the measurement approach

The gin lot is a boundary, not a farm-origin claim.

The chain ends at a recorded cotton gin lot. It does not identify a farm, authenticate fibre, verify labour conditions or establish legal compliance. Splits, blends, custody transfers, physical segregation and independent evidence require a richer operating system.

Tie off the thread: which boundary do you corroborate first?
GarmentCutFabricYarnBaleGin

Corroborate first at / Fabric roll

Name the yarn lot on the fabric roll.

Ask the weaving team to name the yarn lot used for this roll, corroborate it with the production record and keep who made the correction.

Find a thread.

Type to search.