Sub-model: textile article-type classifier (CA/44/2018 boundary)#21
Merged
raahulrahl merged 1 commit intomainfrom Apr 28, 2026
Merged
Sub-model: textile article-type classifier (CA/44/2018 boundary)#21raahulrahl merged 1 commit intomainfrom
raahulrahl merged 1 commit intomainfrom
Conversation
Lands the article-type classifier sub-model that the parent textile_reach_v1 file was deferring to for edge-case disambiguation. submodels/eu/textile/article_type_textile_skin_contact_v1.yaml (710 lines) Encodes the "textile in skin-contact similar to clothing" boundary from REACH Annex XVII Entry 72 — a category the Commission's June 2018 explanatory guide CA/44/2018 fleshes out with examples (bed linen, towels, soft-toy plush surfaces, watch straps with textile content, headset cushions) but the regulation text leaves narrative. Lookup shape: - Article-description-keyed: "given a free-text article description and category, what's its skin-contact classification (clothing / clothing_accessory / footwear / textile_skin_contact_similar_to_clothing / textile_non_skin_contact / leather_natural_only / hide_or_fur_natural_only / mixed / not_textile)?" - Use-condition lookup: returns the product.skin_contact_class (direct_prolonged / direct_short / indirect / none) for representative use scenarios. What this unblocks: The parent textile_reach_v1 file's article_class and skin_contact_class inputs can now be resolved automatically for the majority of dossiers, instead of requiring manual human classification at intake. Edge cases (mixed-material articles, non-conventional uses) still surface as INSUFFICIENT_DATA pending human review. Index updates: - regulations/README.md sub-models section gains the new row. - submodels/README.md status table gains the new row. Sub-models live outside the validators' walked tree, so existing CI is unaffected. `make check` is green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lands the article-type classifier sub-model that
textile_reach_v1was deferring to for edge-case disambiguation around the "textile in skin-contact similar to clothing" boundary.File
submodels/eu/textile/article_type_textile_skin_contact_v1.yaml(710 lines).The Commission's June 2018 explanatory guide CA/44/2018 fleshes out the Entry 72 article-class boundary with examples (bed linen, towels, soft-toy plush surfaces, watch straps with textile content, headset cushions) but the regulation text leaves it narrative. This sub-model captures the guide's worked examples in machine-readable form.
Lookup shapes:
clothing/clothing_accessory/footwear/textile_skin_contact_similar_to_clothing/textile_non_skin_contact/leather_natural_only/hide_or_fur_natural_only/mixed/not_textile.product.skin_contact_class(direct_prolonged/direct_short/indirect/none) for representative use scenarios.What this unblocks
textile_reach_v1'sarticle_classandskin_contact_classinputs can now be resolved automatically for the majority of dossiers, rather than requiring manual classification at intake. Edge cases (mixed-material articles, non-conventional uses) still surface asINSUFFICIENT_DATApending human review.Index updates
regulations/README.mdsub-models section gains the new row.submodels/README.mdstatus table gains the new row.Validation
Sub-models live outside the validators' walked tree —
make checkunaffected and green.🤖 Generated with Claude Code