toga-ai 1.0.564 → 1.0.565

package/knowledge/1.0/apps/library/features/netsuite-item-isfulfillable-sync.md

@@ -6,7 +6,7 @@ project: Library
 client: shared
 type: feature
 status: active
-updated: 2026-07-28
+updated: 2026-08-12
 owners: [bala]
 files:
   - library/app/netsuite.php
@@ -18,6 +18,7 @@ related:
   - ../../worker/features/netsuite-togasupply-per-client-sync.md
   - ../../worker/workflows/isfulfillable-multi-client-backfill.md
   - ../../../2.0/apps/_underscore/features/fulfillable-item-propagation.md
+  - ../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md
 ---
 
 ## Summary
@@ -85,9 +86,27 @@ physical goods from services — `itemtype` would, but the sync has never used `
 `isSerialized`), so this feature intentionally reflects NetSuite's flag **as-is**. **Net effect:
 nearly everything resolves to `fulfillable = 1`.**
 
-- **Open product decision (caveat):** because services come back fulfillable, the storefront makes
-  everything clickable. Whether that is intended vs. needing `itemtype` to hide services is
-  **pending product confirmation**.
+- **Open product decision (RESOLVED for Compass, 2026-08-12):** because services come back
+  fulfillable, the storefront makes everything clickable. A prod evidence review found that
+  `itemtype` **cannot confirm** fulfillability (physical types like DESKTOPS show 0% tracked) but a
+  **tracking ride-along test** cleanly disqualifies fee/software/miscellaneous lines. Compass adopted
+  a **type-derived override** of NetSuite's value — see
+  [Compass isFulfillable data quality & type rule](../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md).
+  Read the write-time-guard gotcha below before implementing it anywhere.
+
+## ⚠ CRITICAL — the existing-item refresh REVERTS any local override
+`getCreateItem`'s refresh (added 2026-07-28) rewrites `isFulfillable` on **existing** items whenever
+NetSuite's value differs from the stored value. NetSuite returns **`T` for service (`NonInvtPart`)
+items**, so **any locally-derived `0` is flipped back to `1` on the next sync run**. A data migration
+alone cannot hold an override — it silently reverts within a day.
+
+Proven from the prod audit log: Compass items **2382 / 2384 / 2385** (`US-IOS-SSC-SHR`,
+`US-IOS-VENUENEXT`, `US-IOS-VIRTUALMGR` — itemType `SERVICES`, assetType `CONSULTING`) were stamped
+**NULL → 1 on 2026-08-04 13:56:00-01** by `apiId 1`, `userId NULL`, inside a 1–2 items/second cron
+sweep that started 13:45 and set every item to `1`.
+
+**Rule: any policy that overrides NetSuite's flag must be enforced at WRITE TIME** — a
+`prePut`/`prePost` guard on Items in `_Model_Client_Item` — **in addition to** the backfill.
 
 ## Verification performed
 - **Prod read-only dry-run:** 20 reachable Compass items; chain walk correct
@@ -106,6 +125,13 @@ nearly everything resolves to `fulfillable = 1`.**
   in `Client_Compass.Apis` (name `Agilant`) — never reproduce the secret value.
 
 ## Change history
+- 2026-08-12 — Prod investigation (no code change): recorded that the **existing-item refresh
+  reverts any local override** (NetSuite returns `T` for services; audit-log proof on Compass items
+  2382/2384/2385, stamped NULL→1 on 2026-08-04), so an override must be enforced by a write-time
+  `prePut`/`prePost` guard, not a migration. Closed the long-standing **open product decision** for
+  Compass — item type cannot *confirm* fulfillability, but the tracking ride-along test disqualifies
+  fee/software/miscellaneous lines; Compass adopted a type-derived override (see the client doc).
+  (bala)
 - 2026-07-28 — Code-review hardening: (1) `getCreateItem` now **refreshes `isFulfillable` on
   existing items** when NetSuite's value differs (not create-only), mirroring the serialized flag;
   diff-only PUT keeps re-syncs no-op. (2) The two other `/items` creation paths
@@ -131,3 +157,5 @@ nearly everything resolves to `fulfillable = 1`.**
 - [Phase 2 — isFulfillable propagation up the SO↔PO chain (2.0)](../../../2.0/apps/_underscore/features/fulfillable-item-propagation.md).
 - [isFulfillable multi-client backfill (worker)](../../worker/workflows/isfulfillable-multi-client-backfill.md)
   — the cross-client catch-up cron and its client-DB / catalog-matching gotchas.
+- [Compass isFulfillable — Data Quality & the Type-Derived Rule](../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md)
+  — measured prod state, the structural reach limit, and the Compass override + its write-time guard.

package/knowledge/1.0/apps/worker/workflows/isfulfillable-multi-client-backfill.md

@@ -6,7 +6,7 @@ project: Worker
 client: shared
 type: workflow
 status: active
-updated: 2026-07-28
+updated: 2026-08-12
 owners: [bala]
 files:
   - worker/crons/toga2/netsuite/backfill_isfulfillable_all_clients.php
@@ -16,6 +16,7 @@ related:
   - ../../library/features/netsuite-item-isfulfillable-sync.md
   - ../../../2.0/apps/_underscore/features/fulfillable-item-propagation.md
   - ../../../clients/compass-usa/profile.md
+  - ../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md
 ---
 
 ## Summary
@@ -46,6 +47,20 @@ recursive up-chain propagation** — it never writes the DB directly and never w
    beta/sandbox endpoint.
 
 ## Gotchas / known issues
+- **⚠⚠ Re-running this backfill CANNOT close the remaining NULLs — they are structurally
+  unreachable (verified prod, 2026-08-12).** The cron only re-PUTs **Agilant source** items and
+  relies on the api2 interceptor to walk up the chain, which requires the client PO to have an
+  Agilant-tier SO behind it (a `PurchaseOrderItems_SalesOrderItems` row). **Vendor-direct POs have
+  none.** In prod `Client_Compass`, **zero** items with `isFulfillable IS NULL` reach the Agilant
+  tier (vs **52,990** line-level reaches for `isFulfillable = 1` items). Per vendor — items ordered /
+  reaching the Agilant tier: OFFICE DEPOT **497/124**; STRATEGIC SYSTEMS **66/0**; FREEDOM GROUPS LLC
+  **61/0**; PRESIDIO **45/0**; COMPASS GROUP **35/0**; ENCOMPASS SUPPLY CHAIN **2/0**. Only ODP
+  partially routes through Agilant NetSuite. **Do not schedule another run expecting these to fill
+  in** — closing the gap needs a different data source (see the
+  [Compass data-quality doc](../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md)).
+- **⚠ Compass Canada was never covered by this run.** `Client_CompassCanada` is **220 items, 100%
+  NULL** as of 2026-08-12 — the storefront Qty Fulfilled cell is dead across the entire Canada
+  tenant. Canada is not in the 17-client list above and has never been stamped at all.
 - **Agilant catalog is matched by NAME, not id.** `Catalogs.name = 'Agilant'` is stable across every
   client, but the `catalogId` **differs per client** — **Quad = 2, all other clients = 1** (verified
   across all 17 client DBs). Hardcoding `catalogId = 2` would silently hit only Quad and miss the
@@ -73,6 +88,11 @@ recursive up-chain propagation** — it never writes the DB directly and never w
   client backfilled from all its Agilant items.
 
 ## Change history
+- 2026-08-12 — Prod audit of the post-run state: recorded that the remaining NULLs are
+  **structurally unreachable by this cron** (vendor-direct POs have no Agilant-tier SO for the
+  interceptor to walk; 0 NULL Compass items reach the Agilant tier, with per-vendor reach counts),
+  and that **Compass Canada was never covered** (220 items, 100% NULL). Post-run Compass state:
+  770 NULL / 25 zero / 697 one, with 12,318 order lines fulfilled but flagged NULL. (bala)
 - 2026-07-28 — Built and ran the multi-client `backfill_isfulfillable_all_clients.php`: direct
   client-DB scoping of Agilant-catalog items (matched by `Catalogs.name`, not id) keyed by
   `c_netsuiteInternalItemId`, NetSuite reads by internal id (cached across clients), re-PUT to api2 so

package/knowledge/2.0/apps/_underscore/INDEX.md

@@ -23,7 +23,7 @@
 | [Record-Changed Event Publishing (_Event::publish to SQS)](features/event-publish-sqs.md) | `_Event::publish()` (in `_underscore/Event.php`) is the PHP side of the real-time event pipeline. | _underscore/Event.php |
 | [FIELD_STORAGE fields — per-row lazy hydration and the platform-wide missing-column 500](features/field-storage-row-hydration.md) | `FIELD_STORAGE` is the 2.0 field type for blob-backed columns (S3 or local folder). | _underscore/Model.php, _underscore/Model/Client/TrackingNumber.php, _underscore/Model/Client/Invoice.php, dbchanges2/Core/HISTORIC/2024/2024-11b - item-fulfillments.sql |
 | [Forecast.Sales NetSuite import engine (real-time webhook)](features/forecast-sale-import.md) | Real-time importer that takes a NetSuite **sale** record and writes its lines into `Forecast.Sales` (the Forecast2 revenue table). | worker2/Component/Forecast/SaleImport/SaleImport.php, worker2/Component/Forecast/Db/Db.php, _underscore/Component/Api/Netsuite/Netsuite.php, worker2/Worker/Netsuite/Invoice.php, worker2/Worker/Netsuite/CashSale.php, worker2/Worker/Netsuite/CreditMemo.php, worker2/Worker/Netsuite/CashRefund.php, worker2/Worker/Netsuite/JournalEntry.php, worker2/Worker/Netsuite/Opportunity.php, worker2/Worker/Netsuite/SalesOrder.php, dbchanges2/Forecast/2026-06-26a - Add journalEntry to Sales transaction type enum.sql, test/@dave/test_invoice_lifecycle.php, test/@dave/test_je_lifecycle.php, test/@dave/test_creditmemo_lifecycle.php, test/@dave/test_cashsale_lifecycle.php, test/@dave/test_cashrefund_lifecycle.php, test/@dave/test_fetchrecord_routes.php, test/@dave/verify_je_classification.php, test/@dave/probe_je_accounts.php, test/@dave/probe_je_shape.php, test/@dave/fixer.php, test/@dave/Junk Drawer/NetSuite/api-message-queue/ue_api_msg_queue_enqueue.js, test/@dave/Junk Drawer/NetSuite/api-message-queue/dev_ue_api_msg_queue_enqueue.js |
-| [isFulfillable Propagation Up the SO↔PO Chain](features/fulfillable-item-propagation.md) | `Items.isFulfillable` is a boolean that gates whether a storefront line's **Qty Fulfilled** cell is actionable. | _underscore/Model/Client/Item.php, _underscore/Model/Compass/Item.php, dbchanges2/Core/2026-07-17 - Items isFulfillable RecordField.sql, dbchanges2/Core/2026-07-17 - RegisterItemIsFulfillableInterceptors.sql, dbchanges2/Client/2026-07-17 - ItemsisFulfillable.sql |
+| [isFulfillable Propagation Up the SO↔PO Chain](features/fulfillable-item-propagation.md) | `Items.isFulfillable` is a boolean that gates whether a storefront line's **Qty Fulfilled** cell is actionable. | _underscore/Model/Client/Item.php, _underscore/Model/Compass/Item.php, toga2-supply/src/pages/Orders/view/OrderView/components/sections/OrderItemsTableSection.tsx, dbchanges2/Core/2026-07-17 - Items isFulfillable RecordField.sql, dbchanges2/Core/2026-07-17 - RegisterItemIsFulfillableInterceptors.sql, dbchanges2/Client/2026-07-17 - ItemsisFulfillable.sql |
 | [Item-Fulfillment Stage Lifecycle (picked/packed/shipped) & Order Status](features/item-fulfillment-stage-lifecycle-and-order-status.md) | Every ItemFulfillment (IF) now carries an explicit **stage** — picked → packed → shipped — resolved through `ItemFulfillmentStages → ItemFulfillmentStatuses` (m | _underscore/Model/Client/SalesOrder.php, _underscore/Model/Quad/SalesOrder.php, _underscore/Model/Compass/SalesOrder.php, _underscore/Model/Compass/SalesOrderStatus.php, _underscore/Model/Client/SalesOrderItem.php, _underscore/Model/Client/Item.php, _underscore/Model/Client/PurchaseOrderItem.php, library/app/api/toga2.php, dbchanges2/Client/2026-06-30a - BackfillNullStageItemFulfillmentsToShipped.sql, dbchanges2/Client/2026-06-30b - SalesOrderStatusesPickedPacked.sql, dbchanges2/Client/2026-06-30c - ItemFulfillmentStageIdNotNull.sql, dbchanges2/Client_CompassCanada/2026-06-30a - ItemFulfillmentLifecycleAndShippedBackfill.sql |
 | [DB-free unit testing for _underscore model interceptors](features/model-interceptor-unit-testing.md) | `_underscore` shipped with **no** PHPUnit setup (no `composer.json`/`phpunit`; only vendored PhpOffice tests existed). | _underscore/Test/bootstrap.php, _underscore/Test/Prudential/ServiceRequestTest.php, test/@Bala/tests/netsuite_salesorder_payload_tests.php |
 | [_Model magic-field access (__get without __isset)](features/model-magic-field-access.md) | `_Model` exposes DB columns as "magic" properties via `__get()`, but it defines **no** `__isset()`. | _underscore/Model/Core/Model.php, _underscore/Model.php, _underscore/Model/Rate/Subscription.php |

package/knowledge/2.0/apps/_underscore/features/fulfillable-item-propagation.md

@@ -6,11 +6,12 @@ project: _Underscore
 client: shared
 type: feature
 status: active
-updated: 2026-07-28
+updated: 2026-08-12
 owners: [bala]
 files:
   - _underscore/Model/Client/Item.php
   - _underscore/Model/Compass/Item.php
+  - toga2-supply/src/pages/Orders/view/OrderView/components/sections/OrderItemsTableSection.tsx
   - dbchanges2/Core/2026-07-17 - Items isFulfillable RecordField.sql
   - dbchanges2/Core/2026-07-17 - RegisterItemIsFulfillableInterceptors.sql
   - dbchanges2/Client/2026-07-17 - ItemsisFulfillable.sql
@@ -18,6 +19,7 @@ related:
   - recursive-item-fulfillments.md
   - ../../../1.0/apps/library/features/netsuite-item-isfulfillable-sync.md
   - ../../../clients/compass-usa/profile.md
+  - ../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md
 ---
 
 ## Summary
@@ -78,6 +80,35 @@ same bridge topology, walked for a different payload (a scalar flag rather than
   too** — the same integrity class as the Compass off-by-one bridge bugs (see
   [MITS PO → SO Item Linking](../../../clients/compass-usa/features/mits-po-to-so-item-linking.md)).
 
+## Reach limit — vendor-fulfilled items can NEVER be reached (structural, verified 2026-08-12)
+The walk only reaches a client item whose PO has an **Agilant-tier SO behind it** (a
+`PurchaseOrderItems_SalesOrderItems` row). **Vendor-direct POs have none**, so an item that is only
+ever fulfilled by an outside vendor **can never receive `isFulfillable` from this pipeline** — no
+amount of re-running the backfill changes that. It is a **structural gap, not a catch-up gap.**
+
+Prod `Client_Compass` (2026-08-12): **zero** items with `isFulfillable IS NULL` reach the Agilant
+tier, versus **52,990** line-level reaches for `isFulfillable = 1` items. Per vendor (Compass items
+ordered / reaching the Agilant tier): OFFICE DEPOT **497/124**; STRATEGIC SYSTEMS **66/0**; FREEDOM
+GROUPS LLC **61/0**; PRESIDIO **45/0**; COMPASS GROUP **35/0**; ENCOMPASS SUPPLY CHAIN **2/0**. Only
+ODP partially routes through Agilant NetSuite. Full analysis + the remediation options:
+[Compass isFulfillable data quality & type rule](../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md).
+
+## Where the flag is consumed (frontend gate)
+`toga2-supply/src/pages/Orders/view/OrderView/components/sections/OrderItemsTableSection.tsx` —
+`isQtyFulfilledClickable` (~lines 21–30) gates the **Qty Fulfilled** cell on:
+
+```
+String(item?.Items?.isFulfillable) === "1" && Number(item?._qtyFulfilled) !== 0
+```
+
+- **`NULL` and `0` behave identically here** — both make the cell dead.
+- The gate also carries a **hardcoded Compass exception**
+  (`hostName === COMPASS && AssetTypes.name === 'FEE' → false`) that duplicates the proposed
+  type-derived data rule; it should be **deleted once that rule lands in the DB** so the logic lives
+  in one place.
+- Because the gate *also* requires `_qtyFulfilled !== 0`, an item that has never been fulfilled is
+  unclickable regardless of the flag's value.
+
 ## Data model / schema (deploy)
 Three `dbchanges2` migrations register the field + hooks; **all must be present in the target
 env or the flag write is rejected:**
@@ -90,9 +121,16 @@ env or the flag write is rejected:**
 
 ## Conflict rule
 Multi-source kits (an item reachable from more than one source) use **LAST-WRITER-WINS**. A
-deterministic `MIN`/`MAX` aggregate was **deliberately deferred** — harmless while values are
+deterministic `MIN`/`MAX` aggregate was **deliberately deferred** on the assumption that values are
 uniformly `1` (see the Phase-1 gotcha: NetSuite flags nearly everything fulfillable).
 
+**⚠ That assumption is no longer safe (2026-08-12).** Prod `Client_Compass` holds **25 items with
+`isFulfillable = 0`** — all bundle headers, **14 with real fulfillments** (worst case `B4NY9UC`:
+11,062 order lines / 2,864 fulfillment rows, its Qty Fulfilled cell disabled). NetSuite marks
+group/kit **headers** `F`, but in TOGa **the header is the line that ships**. Mixed 0/1 values are
+therefore real, and last-writer-wins can land on the wrong one. See the
+[Compass data-quality doc](../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md).
+
 ## Client variations
 - **Compass** (USA/Canada, DB `Client_Compass`) is the built/verified client. Its `_Model_Compass_Item`
   overrides `postPost`/`postPut` for a price override, so it **must** `parent::` up to the base or
@@ -123,12 +161,35 @@ uniformly `1` (see the Phase-1 gotcha: NetSuite flags nearly everything fulfilla
   **resolved/substituted at deploy** — it cannot join across clusters at runtime.
 - **⚠ Compass subclass shadowing.** If a future client subclass overrides Items `postPost`/`postPut`
   without calling `parent::`, propagation silently stops for that client.
-- **Product decision unresolved (caveat, not a bug).** Because NetSuite's `isfulfillable` is `T`
-  for services as well as physical goods (see Phase-1 doc), propagation makes **everything**
-  clickable on the storefront. Whether "reflect NetSuite's flag as-is" is the intended behavior —
-  vs. using `itemtype` to hide services — is **pending product confirmation**.
+- **⚠ Chain-propagation writes are INVISIBLE to the audit log (debugging gotcha).**
+  `propagateFulfillableAcrossChain` issues a **raw `UPDATE Items … WHERE id IN (…)` through `_Query`**
+  (`Item.php` ~lines 562–571), bypassing the model layer and therefore the `Logs_<client>` audit
+  trail. A **sync PUT is logged; a chain propagation is silent** — so "no log row" does **not** mean
+  "never written". Use that as the discriminator between the two write paths: Compass item **2383**
+  (Agilant source 2720, NetSuite id 1536664) has **no** log row while 2382/2384/2385 do, which alone
+  identifies which path set each value.
+  **Query anchor:** prod `Core.RecordFields` **id 2434 = `Items.isFulfillable`** (`recordId 21`); join
+  `Logs_<client>.Record` (`recordId = 21`, `primaryKeyId = <itemId>`) to `Logs_<client>.RecordField`
+  `ON logRecordId` with `recordFieldId = 2434`. Same technique applies to any
+  interceptor-vs-propagation debugging.
+- **Product decision — analyzed 2026-08-12, decision taken for Compass (was "unresolved").** Because
+  NetSuite's `isfulfillable` is `T` for services as well as physical goods (see Phase-1 doc),
+  propagation makes **everything** clickable. A prod evidence review showed item **type cannot
+  confirm** fulfillability (0%-tracked types like DESKTOPS are physical) but the **tracking
+  ride-along test can disqualify** fee/software/miscellaneous lines. Compass has since adopted a
+  **type-derived override** of NetSuite's flag, which **must be enforced at write time** because the
+  Phase-1 daily refresh reverts it. Rule, projected impact, caveats:
+  [Compass isFulfillable data quality & type rule](../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md).
 
 ## Change history
+- 2026-08-12 — Prod investigation (read-only, no code change): recorded the engine's **structural
+  reach limit** (vendor-direct POs have no Agilant-tier SO, so those items can never receive the
+  flag — 0 of the NULL Compass items reach the Agilant tier vs 52,990 reaches for `=1` items),
+  documented the **toga2-supply frontend gate** that consumes the flag (plus its hardcoded Compass
+  `FEE` exception to retire), added the **chain-propagation writes are invisible to the audit log**
+  gotcha with the `Core.RecordFields 2434` / `Logs_<client>` query anchor, and retired the
+  "values are uniformly 1" assumption behind the deferred conflict rule (25 Compass zeros, 14 with
+  real fulfillments). (bala)
 - 2026-07-28 — Fixed a **read-replica routing** bug: `propagateFulfillableAcrossChain`'s source-item
   read and the recursive chain-walk CTE now `setisReadHostEnabled(false)` so they run on the writer
   and see the request's own open write transaction (read-your-writes) — a replica read could return
@@ -151,3 +212,5 @@ uniformly `1` (see the Phase-1 gotcha: NetSuite flags nearly everything fulfilla
   bridge topology.
 - [Compass MITS PO → SO Item Linking](../../../clients/compass-usa/features/mits-po-to-so-item-linking.md)
   — how the SOI↔POI bridges get built (and the integrity bugs that break this walk).
+- [Compass isFulfillable — Data Quality & the Type-Derived Rule](../../../clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md)
+  — measured prod state, why the NULLs are unreachable, and the Compass override.

package/knowledge/INDEX.md

@@ -18,7 +18,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 
 ## 2.0 framework
 
-- **_underscore** (_Underscore) _(framework core)_ — 54 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
+- **_underscore** (_Underscore) _(framework core)_ — 55 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
 - **worker2** (Worker) — 48 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
 - **api2** (API) — 22 doc(s) → [2.0/apps/api2/INDEX.md](2.0/apps/api2/INDEX.md)
 - **dbchanges2** (Database Changes) _(framework core)_ — 8 doc(s) → [2.0/apps/dbchanges2/INDEX.md](2.0/apps/dbchanges2/INDEX.md)

package/knowledge/clients/compass-canada/profile.md

@@ -15,12 +15,13 @@ project: _Underscore
 client: compass-canada
 type: profile
 status: active
-updated: 2026-08-06
+updated: 2026-08-12
 owners: [jcardinal, bala, tcox, apeterson]
 files: []
 related:
   - ../compass-usa/profile.md
   - ../compass-usa/features/approval-decision-flow.md
+  - ../compass-usa/features/isfulfillable-data-quality-and-type-rule.md
   - features/french-order-email-localization.md
   - ../../2.0/apps/toga2-commerce/features/expedited-shipping-gating.md
   - ../../2.0/apps/_underscore/features/item-fulfillment-stage-lifecycle-and-order-status.md
@@ -104,6 +105,17 @@ to but distinct from Compass USA. Like Compass USA it spans the **2.0** commerce
   impact: 34 personas, 7,017 users with personas, 1,461 with more than one. Fix `5313a9b1` exists on
   `TRUE-80672`/`_beta` but is **not in `_production`**. See
   [Client Fields → Login-settings branches](../../2.0/apps/toga2-commerce/features/client-fields.md).
+- **⚠ `Items.isFulfillable` is 100% NULL in Canada — the Qty Fulfilled cell is dead storefront-wide.**
+  All **220** `Client_CompassCanada` items are NULL (prod, 2026-08-12): Canada was **never** included
+  in the multi-client backfill and has never been stamped at all. Note also that Canada uses a
+  **different type vocabulary** than Compass USA — title-case `assetTypes` (`Equipment`, `Hardware`,
+  `Services`, `Fee`, `Consulting`) and its own `itemTypes` (`LAPTOP`, `MACBOOK`, `MONITORS`,
+  `CABLES`, `SERVICE`, `Services`, `CONSULTING`, `SOFTWARE LICENSING`), with **no `FEE` or
+  `SERVICEFEES` itemType at all**. The US-derived rule list still matches, because the columns are
+  `utf8mb4_0900_ai_ci` (case-insensitive) — **do not split it into two hand-maintained lists**, but
+  do re-confirm the Canada vocabulary separately. Projected impact of the proposed rule here: 13 → 0,
+  207 → 1. See
+  [isFulfillable — Data Quality & the Type-Derived Rule](../compass-usa/features/isfulfillable-data-quality-and-type-rule.md).
 - The 2026-06-08 ASN → ItemFulfillment work was for **Compass USA**, not Compass Canada.
 - **Order status is shipped-only**, same as Compass USA (shared `_Model_Compass_SalesOrder`).
   Compass Canada's own IF lifecycle stages (picked/packed/shipped) + shipped backfill are seeded by

package/knowledge/clients/compass-usa/INDEX.md

@@ -5,6 +5,7 @@
 | [Compass Approval-Decision Flow (Notifications & Manager Reassignment)](features/approval-decision-flow.md) | 2.0 | Compass's sales-order approval flow — approval/notification email lists, **manager reassignment**, VIP auto-approve, and EN/FR localization — lives **entirely i | _underscore/Model/Compass/ApprovalDecision.php, _underscore/Model/Compass/SalesOrder.php, _underscore/Model/Compass/Usa/ApprovalDecision.php, _underscore/Model/Compass/Canada/ApprovalDecision.php |
 | [Compass ASN → ItemFulfillment Auto-Creation](features/asn-to-item-fulfillment.md) | 2.0 | For Compass USA, posting an AdvanceShippingNotice (ASN) auto-creates the ItemFulfillment (IF) on the upstream SalesOrder. | _underscore/Model/Compass/AdvanceShippingNotice.php, _underscore/Model/Compass/PurchaseOrder.php, api2/Component/Api/Cxml/Cxml.php, dbchanges2/Client_Compass/2026-06-11 - AsnItemTrackingNumberAcl.sql, dbchanges2/Client_Compass/2026-06-15b - BackfillSA132781ItemFulfillmentTracking.sql, dbchanges2/Client_Compass/2026-06-16 - CleanupSA132763CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16b - CleanupSA132743CrossLineTracking.sql, dbchanges2/Client_Compass/2026-06-16c - BackfillSA132763C40QYUCTracking.sql, dbchanges2/Client_Compass/2026-06-18a - CleanupSA132898DuplicateTracking.sql, dbchanges2/Client_Compass/2026-06-18b - CleanupSA132881DuplicateTracking.sql, dbchanges2/Client_Compass/2026-07-02a - FixSA133377TrackingSerialAndDuplicateIF.sql |
 | [Cost Centers — Unit Locations, numeric-only policy](features/cost-centers.md) | 2.0 | A Compass "cost center" — the value a user picks in commerce and that lands on an order — is **not** a `CostCenters` row. | toga2-commerce/src/pages/Cart/api/CartApi.ts, worker1.5/crons/toga2/compass/import_locations.php, _underscore/Model/Compass/SalesOrder.php, api2/Component/Api/V2/V2.php, dbchanges2/Client_Compass/2026-07-06 - RemoveNonNumericCostCenters.sql |
+| [Compass isFulfillable — Data Quality & the Type-Derived Rule](features/isfulfillable-data-quality-and-type-rule.md) | 2.0 | A **prod-data investigation (2026-08-12, read-only)** into why so many Compass storefront lines still have a dead **Qty Fulfilled** cell. | _underscore/Model/Client/Item.php, library/app/api/toga2.php, worker/crons/toga2/netsuite/backfill_isfulfillable_all_clients.php, toga2-supply/src/pages/Orders/view/OrderView/components/sections/OrderItemsTableSection.tsx |
 | [Compass: Item-Fulfillment TableViews (for-sales-order-items & for-sales-orders, tracking via bridge)](features/item-fulfillment-tracking-tableview.md) | 2.0 | Two sibling Compass TableViews in `Client_Compass` display fulfilled items in toga2-supply, both driven by `TableViews` / `TableViewJoins` / `TableViewFields` c | dbchanges2/Client_Compass/2026-06-10 - ItemFulfillmentsForSalesOrderItemsTableView.sql, dbchanges2/Client_Compass/2026-06-11 - ItemFulfillmentsForSalesOrdersTableView.sql, dbchanges2/Client_Compass/2026-06-15a - FixItemFulfillmentTrackingNumberJoins.sql, dbchanges2/Client/2026-07-15a - ExcludeFeeItemsFromItemFulfillmentsForSalesOrdersView.sql |
 | [Compass MITS PO → SO Item Linking](features/mits-po-to-so-item-linking.md) | 2.0 | MITS sends Compass inbound Purchase Orders (`POST /v2/purchase-orders`) against a Sales Order (`mitsSalesOrder`). | _underscore/Model/Compass/PurchaseOrder.php, worker/crons/toga2/compass/workflow/3a_import_office_depot_purchase_orders.php |
 | [Compass MITS PO Transmission to Vendors](features/mits-po-transmission-to-vendors.md) | 2.0 | The 1.0 worker cron `2_transmit_mits_purchase_orders_to_vendors.php` transmits Compass PurchaseOrders to their vendors (Office Depot, Strategic Systems, Compass | worker/crons/toga2/compass/workflow/2_transmit_mits_purchase_orders_to_vendors.php, worker/crons/toga2/compasscanada/workflow/2_transmit_mits_purchase_orders_to_vendors.php, library/app/client/compass.php |

package/knowledge/clients/compass-usa/features/isfulfillable-data-quality-and-type-rule.md

@@ -0,0 +1,187 @@
+---
+title: Compass isFulfillable — Data Quality & the Type-Derived Rule
+framework: "2.0"
+repo: _underscore
+project: _Underscore
+client: compass-usa
+type: client-feature
+status: active
+updated: 2026-08-12
+owners: ["bala"]
+files:
+  - _underscore/Model/Client/Item.php
+  - library/app/api/toga2.php
+  - worker/crons/toga2/netsuite/backfill_isfulfillable_all_clients.php
+  - toga2-supply/src/pages/Orders/view/OrderView/components/sections/OrderItemsTableSection.tsx
+related:
+  - ../profile.md
+  - ../../compass-canada/profile.md
+  - ../../../2.0/apps/_underscore/features/fulfillable-item-propagation.md
+  - ../../../1.0/apps/library/features/netsuite-item-isfulfillable-sync.md
+  - ../../../1.0/apps/worker/workflows/isfulfillable-multi-client-backfill.md
+---
+
+## Summary
+A **prod-data investigation (2026-08-12, read-only)** into why so many Compass storefront lines still
+have a dead **Qty Fulfilled** cell. Conclusion in one line: the remaining `Items.isFulfillable`
+NULLs are **not a backfill backlog — they are structurally unreachable**, and the values that *are*
+set are partly wrong. This doc records the measured state of `Client_Compass` /
+`Client_CompassCanada`, the evidence for (and against) deriving the flag from item type, the
+**decision** to override NetSuite with a type-derived rule for Compass, and the **write-time guard**
+that decision requires in order to survive the daily NetSuite sync.
+
+No source files were changed and **no migration has been written yet**. All figures below were read
+from **production** on **2026-08-12**.
+
+## Measured state (prod, 2026-08-12)
+- **`Client_Compass`, catalog 1:** **770 NULL / 25 zero / 697 one.**
+- **12,318 Compass order lines have real `ItemFulfillmentItems` but a NULL flag** — the Qty
+  Fulfilled cell is dead on all of them. A further **4,873** lines sit behind `isFulfillable = 0`.
+- **`Client_CompassCanada`: 220 items, 100% NULL.** Canada has **never** been stamped at all, so the
+  Qty Fulfilled cell is dead across the **entire** Canada storefront.
+
+## Why the NULLs cannot be backfilled (structural, not a catch-up gap)
+The flag is born on an **Agilant-catalog source item** during the 1.0 NetSuite item sync
+([Phase 1](../../../1.0/apps/library/features/netsuite-item-isfulfillable-sync.md)) and then
+propagates **up** the `SalesOrderItems`↔`PurchaseOrderItems` chain
+([Phase 2](../../../2.0/apps/_underscore/features/fulfillable-item-propagation.md)). That walk needs
+the Compass PO to have an **Agilant-tier SO behind it** (a `PurchaseOrderItems_SalesOrderItems`
+row). **Vendor-direct POs have none**, so a vendor-fulfilled item can never receive the flag from
+the current pipeline.
+
+Verified in prod `Client_Compass`: **zero** items with `isFulfillable IS NULL` reach the Agilant
+tier, against **52,990** line-level reaches for `isFulfillable = 1` items.
+
+Compass items ordered / reaching the Agilant tier, per vendor:
+
+| Vendor | Ordered | Reaching Agilant tier |
+|---|---|---|
+| OFFICE DEPOT | 497 | 124 |
+| STRATEGIC SYSTEMS | 66 | 0 |
+| FREEDOM GROUPS LLC | 61 | 0 |
+| PRESIDIO | 45 | 0 |
+| COMPASS GROUP | 35 | 0 |
+| ENCOMPASS SUPPLY CHAIN | 2 | 0 |
+
+**Consequence: re-running the multi-client backfill cannot move a single one of these.** Only ODP
+partially routes through Agilant NetSuite.
+
+## The 25 `isFulfillable = 0` Compass items are WRONG — they should be 1
+All 25 are **bundle items**; **14 of them have real fulfillments**. Worst case **`B4NY9UC`**:
+**11,062 order lines and 2,864 fulfillment rows** — the most-shipped laptop in the catalog, with its
+Qty Fulfilled cell **disabled**. NetSuite marks group/kit **headers** `F`, but in TOGa **the header
+IS the line that ships**. This supersedes the earlier assumption (in the Phase 1/Phase 2 docs) that
+the zeros were harmless because values were "uniformly 1".
+
+## Can item type reproduce NetSuite's flag? (evidence)
+**The naive test fails.** "Does this type ever fulfil?" does not separate anything:
+`SERVICES` 119/120 known-fulfillable, `SOFTWARE` 7/7, `FEE` 3/3, while `HARDWARE` fulfils on only
+**26.9%** of lines. `inventoryType = HYBRID` is the **column default** = noise.
+`EntitlementFulfillmentTypes` / `EntitlementFulfillmentMethods` are **EMPTY** in prod.
+
+**The decisive test is the tracking "ride-along":** does a fulfillment row carry **its own** tracking
+number, or does it share one with another line on the same shipment?
+
+| Type | Fulfillment rows | With tracking | Ride-along (shares tracking) |
+|---|---|---|---|
+| itemType `FEE` | 9,639 | 1 (0.0%) | — (0 units) |
+| assetType `FEE` | 10,071 | 22 | **22/22 = 100%** |
+| itemType `SOFTWARE` | — | 129 | **129/129 = 100%** |
+| assetType `MISCELLANEOUS` | — | 385 | **385/385 = 100%** |
+| itemType `SERVICES` | — | 687 | 274 = **39.9%** (413 rows carry their OWN tracking) |
+
+A 100% ride-along rate means the type **never has its own shipment** — a fee/licence line billed
+alongside hardware. `SERVICES` fails that test: 413 service rows genuinely ship on their own.
+
+**⚠ Absence of tracking does NOT prove non-fulfillable.** `DESKTOPS`, `CANTEEN TECHNOLOGY` and
+`VENDING AND OCS ORDERING` all show **0% tracked** yet are physical goods. **Type can only
+DISQUALIFY an item, never confirm one.**
+
+## Decision — the type-derived rule for Compass (2026-08-12)
+Developer's call; it **overrides NetSuite's value**:
+
+```
+isFulfillable = 0  WHERE itemType OR assetType IN
+                   ('FEE','SERVICEFEES','SERVICES','SERVICE','CONSULTING')
+isFulfillable = 1  otherwise
+```
+
+Projected impact:
+- **`Client_Compass`:** **186 → 0** (54 currently NULL + 131 currently **1** + 1 currently 0) and
+  **606 → 1**.
+- **`Client_CompassCanada`:** **13 → 0**, **207 → 1**.
+
+**⚠ Recorded caveat — the SERVICES/CONSULTING half is NOT supported by the evidence.** 413
+`SERVICES` fulfillment rows carry their own tracking, and the rule flips **131 currently-clickable
+items off**. That half **needs product sign-off**. `SOFTWARE` (100% ride-along) is the *stronger*
+candidate on the evidence but was deliberately **left out of scope**.
+
+## ⚠ CRITICAL — a backfill alone will be undone by the daily NetSuite sync
+Phase 1's `getCreateItem` **refreshes `isFulfillable` on EXISTING items** whenever NetSuite's value
+differs from the stored value. NetSuite returns **`T` for service (`NonInvtPart`) items**, so any
+type-derived **0** is **flipped back to 1 on the next sync run**.
+
+Proven from the audit log: Compass items **2382 / 2384 / 2385**
+(`US-IOS-SSC-SHR`, `US-IOS-VENUENEXT`, `US-IOS-VIRTUALMGR` — itemType `SERVICES`, assetType
+`CONSULTING`) were stamped **NULL → 1 on 2026-08-04 13:56:00-01** by `apiId 1`, `userId NULL`,
+inside a **1–2 items/second cron sweep** that began 13:45 and set every item to 1.
+
+**Therefore the rule MUST be enforced at write time** — a `prePut`/`prePost` guard on Items in
+`_Model_Client_Item` — **in addition to** the backfill migration. A migration on its own silently
+reverts within a day.
+
+## Evidence-based alternative signals (if type is not wanted)
+- **`ItemFulfillmentItems`** (via `SalesOrderItems.salesOrderItemId`) = **proven shipped**.
+- **`VendorItems`** (`isActive = 1`) = **procurable from a vendor**.
+
+Tiering the 770 NULL Compass items: **184** have fulfillment history · **286** have an active
+`VendorItems` row · **300** have neither. The frontend gate already requires
+`_qtyFulfilled !== 0`, so **tier-3 items cannot be clicked regardless of the flag**, and can be left
+NULL.
+
+## Where the storefront consumes the flag (+ a hardcode to retire)
+`toga2-supply/src/pages/Orders/view/OrderView/components/sections/OrderItemsTableSection.tsx`,
+`isQtyFulfilledClickable` (~lines 21–30):
+
+```
+String(item?.Items?.isFulfillable) === "1" && Number(item?._qtyFulfilled) !== 0
+```
+
+plus an extra **hardcoded** `hostName === COMPASS && AssetTypes.name === 'FEE' → false`.
+
+- **NULL and 0 behave identically** at this gate.
+- That **FEE hardcode duplicates the proposed data rule** — once the rule lands in the DB it should
+  be **deleted** so the logic lives in one place.
+
+## Compass Canada uses a DIFFERENT type vocabulary
+Canada's `assetTypes` are **title case** (`Equipment`, `Hardware`, `Services`, `Fee`, `Consulting`)
+and its `itemTypes` are a **separate vocabulary** (`LAPTOP`, `MACBOOK`, `MONITORS`, `CABLES`,
+`SERVICE`, `Services`, `CONSULTING`, `SOFTWARE LICENSING`) — it has **no `FEE` or `SERVICEFEES`
+itemType at all**.
+
+Because these tables are `utf8mb4_0900_ai_ci` (**case-insensitive**), the single US-derived
+`IN ('FEE','SERVICEFEES',…)` list **matches Canada's title-case values** — verified against live
+data. **Do not hand-maintain two string lists**, but **do** re-confirm the Canada vocabulary
+separately, since the names genuinely differ and a US list *looks* wrong for Canada.
+
+## Change history
+- 2026-08-12 — Prod read-only investigation of `Items.isFulfillable` across `Client_Compass` /
+  `Client_CompassCanada`. Established that remaining NULLs are **structurally unreachable**
+  (vendor-direct POs have no Agilant-tier SO, so the chain walk has nothing to walk — 0 NULL items
+  reach the Agilant tier vs 52,990 reaches for `=1` items), that the **25 zeros are wrong** (all
+  bundle headers, 14 with real fulfillments, incl. `B4NY9UC` at 11,062 lines / 2,864 fulfillments),
+  and that **Canada is 100% NULL**. Proved item type cannot *confirm* fulfillability but the
+  **tracking ride-along test** cleanly disqualifies fee/software/miscellaneous lines (100%
+  ride-along) while `SERVICES` fails it (39.9%). **Decided** the type-derived rule
+  (`FEE/SERVICEFEES/SERVICES/SERVICE/CONSULTING → 0`, else 1) with the SERVICES/CONSULTING half
+  flagged for product sign-off, and established that it **must** be enforced by a `prePut`/`prePost`
+  guard because the daily sync's existing-item refresh reverts it (audit-log proof: items
+  2382/2384/2385 stamped NULL→1 on 2026-08-04). (bala)
+
+## Related docs
+- [Phase 1 — isFulfillable from NetSuite during item sync (1.0)](../../../1.0/apps/library/features/netsuite-item-isfulfillable-sync.md)
+  — where the value is born and the refresh that reverts overrides.
+- [Phase 2 — isFulfillable propagation up the SO↔PO chain (2.0)](../../../2.0/apps/_underscore/features/fulfillable-item-propagation.md)
+  — the chain walk whose reach is the structural limit described here.
+- [isFulfillable multi-client backfill (worker)](../../../1.0/apps/worker/workflows/isfulfillable-multi-client-backfill.md)
+  — the cron that **cannot** close this gap.

package/knowledge/clients/compass-usa/profile.md

@@ -17,7 +17,7 @@ project: _Underscore
 client: compass-usa
 type: profile
 status: active
-updated: 2026-08-11
+updated: 2026-08-12
 owners: [jcardinal, bala, tcox, apeterson, dfranks]
 files: []
 related:
@@ -27,6 +27,7 @@ related:
   - features/mits-sales-order-transmission-alerting.md
   - features/asn-to-item-fulfillment.md
   - features/cost-centers.md
+  - features/isfulfillable-data-quality-and-type-rule.md
   - features/approval-decision-flow.md
   - workflows/cross-kit-bundle-corruption.md
   - workflows/odp-duplicate-po-line-cleanup.md
@@ -134,4 +135,12 @@ separate, related client (see its own profile).
   up the SO↔PO chain to the client-facing Compass item by an api2 interceptor
   ([Phase 2](../../2.0/apps/_underscore/features/fulfillable-item-propagation.md)). Verified on prod
   Compass chains; a one-time July-5+ backfill re-PUTs source items through the same path.
+  **⚠ Prod audit 2026-08-12 — the flag is largely broken for Compass and NO backfill can fix it.**
+  770 NULL / 25 zero / 697 one; **12,318** order lines are really fulfilled but flagged NULL, so
+  their Qty Fulfilled cell is dead. The NULLs are **structurally unreachable** (vendor-direct POs
+  have no Agilant-tier SO to walk up from), and the 25 zeros are **wrong** (bundle headers that do
+  ship — incl. `B4NY9UC`, 11,062 lines). A **type-derived override** was decided and **must** be
+  enforced by a write-time guard, because the daily NetSuite sync reverts it. Evidence, rule,
+  projected impact and caveats:
+  [isFulfillable — Data Quality & the Type-Derived Rule](features/isfulfillable-data-quality-and-type-rule.md).
 - This profile is a starting point; expand as more Compass-specific behavior is captured.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.564",
+  "version": "1.0.565",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",