@instruments/taxonomy 1.2.0 → 1.3.1

package/dist/search-corpus-source.d.ts

@@ -1,6 +1,4 @@
-export declare const MATERIALGRAPH_SEARCH_CORPUS_COMMIT: "53df40868bfb09bfe69bc66c455c051e34005ae1";
-export declare const MATERIALGRAPH_SEARCH_CORPUS_PATH: "packages/products/src/benchmark/fixtures/benchmark-cases-2026-07-31.1.json";
-export declare const MATERIALGRAPH_SEARCH_CORPUS_SNAPSHOT: "2026-07-31";
+export declare const SEARCH_CORPUS_SNAPSHOT: "2026-07-31";
 /**
  * The fixture evidences searched language and admission need. Taxonomy authors the concept boundary;
  * neither an individual phrase nor the 244-query fixture as a whole is treated as that definition.

package/dist/term.d.ts

@@ -39,7 +39,13 @@ export type SourceBasis =
  | "standard";
 export interface TermProvenance {
     basis: SourceBasis;
-    /** The upstream file, corpus or standard. Free text, but always specific enough to re-read. */
+    /**
+     * The upstream standard, reference or source. A public standard or vocabulary is named outright
+     * and can be re-read by anyone. A private source is written as its kind and an opaque id, e.g.
+     * "PRICE_TIERS in a materials-retrieval system (src-05)": the id is stable, so every term citing
+     * one source can be shown to cite the same thing, and re-reading it means the steward resolving
+     * the id at the `snapshot` date. The date lives in `snapshot` and is never repeated here.
+     */
     source: string;
     /** ISO date the source was read. Absent only for `authored`. */
     snapshot?: string;
@@ -95,9 +101,9 @@ export type TermStatus = "active" | "deprecated";
  * value that appears regularly, `rare` one that barely does, and `unattested` a value the corpus
  * never uses. Set `usage` only where the named corpus can actually speak to the term: omitting it
  * says "not measured here", which is honest, whereas `unattested` against an unrelated corpus
- * would read as a claim about the term rather than about the corpus. The usage figures behind these derive from Material Bank's warehouse and
- * from the DesignShop capture; publishing a raw number would publish a figure from someone else's
- * business. The band carries the signal a reader actually needs - is this term common or rare  -
+ * would read as a claim about the term rather than about the corpus. The usage figures behind these
+ * derive from a materials-marketplace catalogue and a furnishings retailer's room schemes; publishing a raw
+ * number would publish a figure from someone else's business. The band carries the signal a reader actually needs - is this term common or rare  -
  * and nothing more.
  */
 export type UsageBand = "dominant" | "common" | "occasional" | "rare" | "unattested";
@@ -110,8 +116,8 @@ export interface TermUsage {
 /**
  * Why a term carries no usage band when the corpus plainly has something to say about it.
  *
- * The distinguishing case is `style.modernism`. DesignShop tags a dominant share of its room
- * schemes `Modern`, but that is the crosswalk row that DECLINES: `Modern` reads as either
+ * The distinguishing case is `style.modernism`. A furnishings retailer tags a dominant share of
+ * its schemes `Modern`, but that is the crosswalk row that DECLINES: `Modern` reads as either
  * `style.modernism` or `style.contemporary` and the source never recorded which. Attributing the
  * usage would smuggle in the guess the crosswalk refused to make.
  *
@@ -302,7 +308,7 @@ export type RelationPredicate =
  * the standing counterexample.
  */
  | "serves"
-/** This style or idiom draws on that place idiom or period. */
+/** This style, idiom or scheme draws on that place idiom, period, building typology or season. */
  | "evokes"
 /** This style descends from that style. */
  | "influenced-by"

package/dist/v1.d.ts

@@ -1,7 +1,7 @@
 import type { ElementPlacement, ExternalMapping, PeriodSpan, RelationPredicate, SearchedWithout, StyleKind, TermProvenance, TermUsage, UsageWithheld } from "./term.js";
 export declare const TAXONOMY_BASE_URI: "https://taxonomy.materialinstruments.com";
-export declare const TAXONOMY_SNAPSHOT: "2026-09-01";
-export declare const TAXONOMY_VERSION: "1.2.0";
+export declare const TAXONOMY_SNAPSHOT: "2026-09-11";
+export declare const TAXONOMY_VERSION: "1.3.1";
 export type CanonicalConceptUri = `${typeof TAXONOMY_BASE_URI}/id/${string}`;
 export type LifecycleStatus = "active" | "deprecated";
 export interface Lifecycle {
@@ -135,7 +135,7 @@ export declare const TAXONOMY_CORPUS_METADATA: {
     readonly lexicalEntryCount: number;
     readonly nodeCount: number;
     readonly revision: string;
-    readonly snapshot: "2026-09-01";
-    readonly version: "1.2.0";
+    readonly snapshot: "2026-09-11";
+    readonly version: "1.3.1";
 };
 export {};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@instruments/taxonomy",
-  "version": "1.2.0",
+  "version": "1.3.1",
   "description": "Canonical data-only interiors and architecture knowledge graph and lexical corpus.",
   "license": "SEE LICENSE IN LICENSE",
   "repository": {

package/dist/crosswalks/designshop.d.ts

@@ -1,30 +0,0 @@
-import type { CanonicalisationInput, CanonicalisationVerdict } from "../canonicalisation.js";
-import type { CrosswalkMapping } from "./mapping.js";
-export declare const DESIGNSHOP_CROSSWALK_VERSION: "designshop-2026-08-31.1";
-export declare const DESIGNSHOP_SOURCE_SYSTEM: "designshop";
-export declare const DESIGNSHOP_SOURCE_FIELDS: readonly ["product_category", "material", "pattern", "finish", "format", "construction", "scheme_style", "product_style", "mood", "space", "requirement"];
-export type DesignShopSourceField = (typeof DESIGNSHOP_SOURCE_FIELDS)[number];
-type Mapping = CrosswalkMapping;
-/**
- * Source-specific rows. Source fields are deliberately retained: DesignShop's `material:Mosaic`
- * resolves to a format, and pretending the source field was already canonical would preserve its
- * category error instead of its evidence.
- */
-export declare const DESIGNSHOP_CROSSWALK: Readonly<Record<DesignShopSourceField, Readonly<Record<string, Mapping>>>>;
-export interface DesignShopCanonicalisationInput extends Omit<CanonicalisationInput, "sourceSystem" | "sourceField"> {
-    sourceField: DesignShopSourceField;
-}
-/** Unknown values are unresolved, never declined. Declines require an explicit curated row. */
-export declare const canonicaliseDesignShop: (input: DesignShopCanonicalisationInput) => CanonicalisationVerdict;
-export interface DesignShopAppearanceTestVector {
-    expectedAssertions: readonly string[];
-    facets: readonly {
-        sourceField: DesignShopSourceField;
-        sourceValue: string;
-    }[];
-    id: string;
-    market: "residential" | "commercial";
-}
-/** Shared fixtures prove axes compose instead of welding material identity to appearance. */
-export declare const DESIGNSHOP_APPEARANCE_TEST_VECTORS: readonly DesignShopAppearanceTestVector[];
-export {};

package/dist/crosswalks/materialgraph.d.ts

@@ -1,38 +0,0 @@
-import type { CanonicalisationInput, CanonicalisationVerdict } from "../canonicalisation.js";
-import type { BundleRole } from "../match.js";
-import type { CrosswalkMapping } from "./mapping.js";
-export declare const MATERIALGRAPH_CROSSWALK_VERSION: "materialgraph-2026-08-27.1";
-export declare const MATERIALGRAPH_SOURCE_SYSTEM: "materialgraph";
-export declare const MATERIALGRAPH_SNAPSHOT: "2026-08-27";
-/**
- * The two dictionaries this crosswalk covers. Both were `ms_`-prefixed until MaterialGraph renamed
- * them on 2026-08-27; the bare names are the current ones.
- */
-export declare const MATERIALGRAPH_SOURCE_FIELDS: readonly ["role", "character"];
-export type MaterialGraphSourceField = (typeof MATERIALGRAPH_SOURCE_FIELDS)[number];
-/**
- * Two `role` values that are not product properties at all, and where they actually go.
- *
- * A role IN A SCHEME is what `match.ts` already calls a `BundleRole`: `accent` means present and
- * deliberate but the scheme survives without it, `constitutive` means remove it and the thing stops
- * being what it is. A feature surface is the second by definition. Publishing these as a mapping to
- * the bundle role rather than as terms is what stops the same slab being permanently labelled a
- * feature surface because one scheme once used it as one.
- */
-export declare const MATERIALGRAPH_COMPOSITIONAL_ROLES: Readonly<Record<string, BundleRole>>;
-export declare const MATERIALGRAPH_CROSSWALK: Readonly<Record<MaterialGraphSourceField, Readonly<Record<string, CrosswalkMapping>>>>;
-export interface MaterialGraphCanonicalisationInput extends Omit<CanonicalisationInput, "sourceSystem" | "sourceField"> {
-    sourceField: MaterialGraphSourceField;
-}
-/** Unknown values are unresolved, never declined. Declines require an explicit curated row. */
-export declare const canonicaliseMaterialGraph: (input: MaterialGraphCanonicalisationInput) => CanonicalisationVerdict;
-/**
- * The upstream dictionaries, vendored as id tuples so this file can be checked against them.
- *
- * Verbatim from materialgraph packages/schema/src/registry/value-dictionaries — `role` in
- * `material-semantics-core.ts`, `character` in `material-semantics-aesthetics.ts`, both at the
- * 2026-08-27 snapshot, after the rename that dropped their `ms_` prefixes.
- */
-export declare const MATERIALGRAPH_ROLE_VALUES: readonly ["wall_finish", "flooring", "ceiling", "joinery", "upholstery", "drapery", "accent", "worksurface", "casegoods", "feature_surface", "trim", "other"];
-export declare const MATERIALGRAPH_CHARACTER_VALUES: readonly ["quiet", "expressive", "restrained", "bold", "rustic", "crafted", "refined", "formal", "casual", "natural_reading", "synthetic_reading", "soft_reading", "hard_reading"];
-export declare const MATERIALGRAPH_SOURCE_VALUES: Readonly<Record<MaterialGraphSourceField, readonly string[]>>;

package/dist/crosswalks/miu.d.ts

@@ -1,13 +0,0 @@
-import type { Application, MaterialFamily, Sector } from "../authoring.js";
-export declare const MIU_MATERIAL_FAMILIES: readonly ["wood", "wood_veneer", "engineered_wood", "bamboo", "cork", "natural_stone", "terrazzo", "ceramic_porcelain", "glass", "metal", "concrete", "plaster", "clay", "brick", "paint_coating", "wallcovering", "laminate", "solid_surface", "mineral_composite", "resin", "linoleum", "vinyl", "rubber", "carpet", "rug", "textile", "leather", "acoustic_felt", "acoustic_composite", "recycled_composite", "paper_cardboard", "biobased_composite", "greenery_planting", "lighting", "hardware", "digital_media", "water_feature", "mixed_material", "color_palette_only", "unknown"];
-export type MiuMaterialFamily = (typeof MIU_MATERIAL_FAMILIES)[number];
-export declare const MIU_FAMILY_TO_CANONICAL: Readonly<Record<MiuMaterialFamily, MaterialFamily | null>>;
-export declare const MIU_PROJECT_SECTORS: readonly ["hospitality", "food_and_beverage", "workplace", "residential", "multifamily", "retail_and_showroom", "healthcare", "wellness", "education", "civic", "cultural", "community", "sports_recreation", "entertainment", "industrial", "logistics", "maker", "transportation", "landscape_public_realm", "mixed_use", "master_planning", "temporary_exhibition", "religious", "senior_living", "student_housing", "unknown"];
-export type MiuProjectSector = (typeof MIU_PROJECT_SECTORS)[number];
-export declare const MIU_SECTOR_TO_CANONICAL: Readonly<Record<MiuProjectSector, Sector | null>>;
-export declare const MIU_SURFACE_APPLICATIONS: readonly ["flooring", "floor_inlay", "stair_tread", "stair_riser", "wall_finish", "wall_panel", "wainscot", "baseboard", "trim", "ceiling_finish", "ceiling_cloud", "column_wrap", "door_finish", "frame_finish", "shower_wall", "shower_floor", "backsplash", "vanity_top", "toilet_partition", "commercial_kitchen_floor", "kitchen_wall", "food_service_counter", "laundry_floor", "pool_deck_surface", "reception_desk", "bar_front", "bar_top", "back_bar", "banquette_base", "cabinet_front", "shelving", "display_fixture", "closet_system", "workstation_casework", "checkout_counter", "upholstery", "loose_furniture", "built_in_seating", "banquette_upholstery", "drapery", "window_treatment", "rug", "carpet_tile", "bedding", "privacy_curtain", "acoustic_fabric_panel", "lighting_fixture", "acoustic_treatment", "partition", "operable_wall", "signage", "wayfinding", "hardware", "plumbing_fixture", "decorative_screen", "art_installation", "green_wall", "facade_cladding", "soffit", "exterior_screen", "paving", "decking", "outdoor_furniture", "planter", "pool_coping", "shade_structure", "railing", "fence_screen", "unknown"];
-export type MiuSurfaceApplication = (typeof MIU_SURFACE_APPLICATIONS)[number];
-export declare const MIU_SURFACE_APPLICATION_TO_CANONICAL: Readonly<Record<MiuSurfaceApplication, Application | null>>;
-export declare const miuFamilyToCanonical: (value: string) => MaterialFamily | null;
-export declare const miuSectorToCanonical: (value: string) => Sector | null;
-export declare const miuSurfaceApplicationToCanonical: (value: string) => Application | null;

package/dist/downstream-check-policy.d.ts

@@ -1,34 +0,0 @@
-/**
- * Whether a cross-repository check may skip, or must fail for want of its subject.
- *
- * A check that no-ops when it cannot find what it inspects reads green forever, and this
- * one has already rotted that way once: the materialgraph sync test asserted nothing for
- * twelve days after a file split, unnoticed, because it only ran where a sibling checkout
- * happened to exist and never in CI.
- *
- * Blanket-failing is not the fix either. CI legitimately has no sibling repo, so a hard
- * requirement would break every run for a condition nobody can satisfy there.
- *
- * So the strictness is opt-in and explicit. By default an absent checkout skips, which is
- * honest about what CI can see. A context that is *meant* to be able to run the check —
- * a release gate, a verification pass, a developer who wants to know — sets the
- * environment variable, and then a missing checkout is a failure rather than a shrug.
- */
-export declare const REQUIRE_DOWNSTREAM_CHECK_ENV = "TAXONOMY_REQUIRE_DOWNSTREAM_CHECKS";
-export type DownstreamCheckDecision = {
-    kind: "run";
-} | {
-    kind: "skip";
-    reason: string;
-} | {
-    kind: "fail";
-    reason: string;
-};
-export declare const decideDownstreamCheck: (input: {
-    /** Whether the thing being inspected is actually on disk. */
-    subjectPresent: boolean;
-    /** What is being looked for, named in the failure so it is actionable. */
-    subjectLabel: string;
-    /** The raw environment value; any non-empty value other than "0"/"false" means strict. */
-    requireFlag: string | undefined;
-}) => DownstreamCheckDecision;

package/dist/env.d.ts

@@ -1,6 +0,0 @@
-/**
- * Whether cross-repository checks must fail rather than skip when their subject is
- * missing. Undefined in almost every context, including CI — see
- * `downstream-check-policy` for why that default is the honest one.
- */
-export declare const readRequireDownstreamChecks: () => string | undefined;

package/dist/estate/rows/architizer.d.ts

@@ -1,2 +0,0 @@
-import type { Row } from "../decomposition.js";
-export declare const ARCHITIZER_ROWS: readonly Row[];

package/dist/estate/rows/designround.d.ts

@@ -1,2 +0,0 @@
-import type { Row } from "../decomposition.js";
-export declare const DESIGNROUND_ROWS: readonly Row[];

package/dist/estate/rows/designshop.d.ts

@@ -1,2 +0,0 @@
-import type { Row } from "../decomposition.js";
-export declare const DESIGNSHOP_ROWS: readonly Row[];

package/dist/estate/rows/materia.d.ts

@@ -1,2 +0,0 @@
-import type { Row } from "../decomposition.js";
-export declare const MATERIA_ROWS: readonly Row[];

package/dist/estate/rows/materialgraph.d.ts

@@ -1,2 +0,0 @@
-import type { Row } from "../decomposition.js";
-export declare const MATERIALGRAPH_ROWS: readonly Row[];

package/dist/estate/rows/samplize.d.ts

@@ -1,2 +0,0 @@
-import type { Row } from "../decomposition.js";
-export declare const SAMPLIZE_ROWS: readonly Row[];