{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp04_retrieval_first_paired20_20260802","cell_id":"layer_decay_and_expiration_management__logistics_supply_chain","round_index":0,"assessments":[{"hypothesis_id":"H1","search_queries":["warehouse work instructions document control obsolete versions point of use ISO 9001 official","warehouse management system work instructions version history superseded documents","site:support.tulip.co work instructions version published version archive official","digital work instruction software only current version operators archived versions official product documentation"],"sources":[{"source_id":"H1-S1","title":"ISO 9001 Work Instruction Document Control","publisher":"StepLinq","url":"https://steplinq.com/en/resources/iso-9001-work-instruction-document-control","source_class":"COMMERCIAL_FIRST_PARTY","claims_supported":["The product retains superseded work-instruction versions for traceability while withholding them from operators.","Only approved versions are visible in the floor-facing viewer.","Version history, approvals, change logs, and periodic review are established document-control practices."]},{"source_id":"H1-S2","title":"Work Instruction Details","publisher":"PTC","url":"https://support.ptc.com/help/thingworx_applications/r9.7/en/thingworx_applications/user_interface/CWC_Authoring_WIAuthoring_Details.html","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["PTC automatically versions approved work instructions and identifies the most recent version as current.","Prior approved versions remain available in a read-only version history.","Work instructions under approval cannot be edited."]}],"closest_analogue":"Commercial digital-work-instruction document control that exposes only the current approved instruction to operators while retaining read-only prior versions.","overlap":"Automatic versioning, a designated current version, suppression of obsolete versions at the point of use, retained history, approval metadata, and recoverable traceability substantially reproduce the proposed intervention.","remaining_difference":"The warehouse-specific matched-site outcome test and an explicit active-view TTL are narrower implementation and evaluation details; the lifecycle mechanism itself is already present.","classification":"OBVIOUS_COLLISION","disposition":"REJECT","rationale":"The central mechanism—preventing operators from using superseded instructions while preserving version history—is already a documented first-party product capability and standard document-control pattern."},{"hypothesis_id":"H2","search_queries":["carrier rate card effective dates version freight audit rate management official documentation","Oracle Transportation Management rate record effective expiration dates rate version","Oracle Transportation Management overlapping carrier rate versions dependencies shipment invoice","SAP transportation management rate table validity periods official"],"sources":[{"source_id":"H2-S1","title":"Rate Record","publisher":"Oracle","url":"https://docs.oracle.com/en/cloud/saas/transportation/26c/otmol/planning/rate_manager/create_rate_record.htm","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Oracle Transportation Management rate records have effective and expiration dates and are invalid outside that period.","Rate records have expiration markers, active status, and parent identifiers for tracking versions during approval.","A rate record and offering become locked when attached to a dependent CRT configuration, preventing later edits that would invalidate copied data."]},{"source_id":"H2-S2","title":"Oracle Transportation Management Data Management Guide","publisher":"Oracle","url":"https://docs.oracle.com/cd/E38437_01/otm/acrobat/otm/integration/E38426_02.pdf","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Oracle documents exporting rate records marked for expiration.","Its rate-management tooling copies offerings into new versions for upcoming periods.","The tooling updates child-record identifiers when rate identifiers change, preserving structural consistency."]}],"closest_analogue":"Oracle Transportation Management rate-record lifecycle management using validity periods, expiration markers, parent-version lineage, and locks on rate records already attached to dependent configurations.","overlap":"Temporal authority, explicit expiration, version lineage, active/inactive use, child-record maintenance, and dependency-related locking overlap nearly all of the proposed lifecycle control.","remaining_difference":"The sources do not show a retirement gate that queries unsettled shipment quotes and freight invoices specifically; that is a testable integration detail rather than a clearly distinct lifecycle mechanism.","classification":"OBVIOUS_COLLISION","disposition":"REJECT","rationale":"Existing transportation-management documentation already combines rate-version validity, expiration, lineage, and dependency protection. Restricting the dependency check to open quotes and invoices is too narrow to survive this shallow screen."},{"hypothesis_id":"H3","search_queries":["cold chain temperature monitoring data retention archive retrieval official guidance","cold chain telemetry archived data restore test end to end","NIST backup restoration testing archive media format readability official","ELPRO liberoMANAGER cold chain data archive retention official"],"sources":[{"source_id":"H3-S1","title":"Cold chain equipment and dry store temperature mapping tool","publisher":"World Health Organization","url":"https://www.who.int/publications/m/item/cold-chain-equipment-and-dry-store-temperature-mapping-tool","source_class":"OFFICIAL_GUIDANCE","claims_supported":["Temperature mapping and monitoring are integral to pharmaceutical storage controls.","The WHO tool explicitly supports multiple logger types and has been updated to add compatibility with additional devices, evidencing format and tooling heterogeneity."]},{"source_id":"H3-S2","title":"Database Management Software for Pharmaceutical Supply Chains","publisher":"ELPRO","url":"https://www.elpro.com/en/libero-manager","source_class":"COMMERCIAL_FIRST_PARTY","claims_supported":["liberoMANAGER processes cold-chain data from USB, Bluetooth, and real-time logger types in one database.","The platform digitally archives, analyzes, traces, and assesses shipment data.","It performs integrity checks on uploaded reports and preserves an unalterable original file."]},{"source_id":"H3-S3","title":"Restore testing","publisher":"Amazon Web Services","url":"https://docs.aws.amazon.com/aws-backup/latest/devguide/restore-testing.html","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["AWS Backup provides scheduled restore jobs and optional post-restore validation rather than relying only on backup metadata.","Restore tests can select random or older recovery points and report completion time.","Periodic restore testing is an established general-purpose recovery-control pattern."]}],"closest_analogue":"A cold-chain system of record that archives heterogeneous logger data, combined with general-purpose scheduled backup restore testing and validation.","overlap":"Cold-chain telemetry is already centrally archived with integrity checking, and periodic restoration from selected recovery points is already an operationalized infrastructure capability.","remaining_difference":"The located sources do not combine the two into cold-chain-specific drills stratified by archive age and logger format that must parse the telemetry and reconnect it to the current shipment-investigation record. A direct test can compare such drills with integrity-check-only controls and measure latent retrieval, parsing, and linkage failures.","classification":"POSSIBLE_DISTINCTION","disposition":"ADVANCE","rationale":"The constituent practices are established, but the shallow search did not reveal a direct cold-chain analogue that validates semantic parsing and shipment reconnection across age and format bands. That bounded combination merits deeper review."},{"hypothesis_id":"H4","search_queries":["warehouse slotting optimization inventory velocity age demand multi factor official documentation","stranded inventory aged inventory re-slotting quarantine reserve warehouse software","Oracle warehouse inventory age velocity slotting official","warehouse inventory reversible quarantine non-sellable location lot official documentation"],"sources":[{"source_id":"H4-S1","title":"Slotting Overview and Setup","publisher":"Oracle","url":"https://docs.oracle.com/cd/E95327_01/oroms/pdf/5/cws_help/WH16_01.htm","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Oracle slotting selects locations using sales, purchase orders, on-hand quantity, velocity, product attributes, and location pick volume.","The system identifies products that should move to different primary pick locations.","It supports transferring discontinued and bottom-performing items out of primary locations."]},{"source_id":"H4-S2","title":"Warehouse slotting","publisher":"Microsoft","url":"https://learn.microsoft.com/en-us/dynamics365/supply-chain/warehousing/warehouse-slotting","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Dynamics 365 consolidates demand and assigns inventory to pick locations using quantity, unit, dimensions, fixed locations, and existing on-hand inventory.","The slotting plan can generate replenishment and movement work.","Slotting can run automatically on a recurrence."]},{"source_id":"H4-S3","title":"Understanding Inventory Numbers in Warehance","publisher":"Warehance","url":"https://www.warehance.com/support-center/products-and-inventory/inventory/understanding-inventory-numbers-in-warehance","source_class":"COMMERCIAL_FIRST_PARTY","claims_supported":["Inventory can be moved into non-sellable quarantine or returns locations while remaining physically on hand.","Moving inventory between non-sellable and sellable locations reversibly changes availability without destroying the lot.","Expired, damaged, reserved, and quarantined inventory are differentiated states."]}],"closest_analogue":"Multi-factor warehouse slotting that moves slow, discontinued, or low-performing inventory out of prime pick locations, coupled with reversible non-sellable or quarantine states.","overlap":"Multi-factor ranking, velocity and demand signals, forward-location capacity allocation, physical movement to other locations, automatic recurring execution, and reversible quarantine are all established components.","remaining_difference":"The proposal scores individual lots rather than SKUs and explicitly applies an age-decay term plus provenance and hold vetoes. Those details are testable, but they sit inside an already mature multi-factor slotting and inventory-status pattern.","classification":"OBVIOUS_COLLISION","disposition":"REJECT","rationale":"The claimed operational lever and expected throughput benefit substantially collide with existing slotting products; lot granularity and an explicit age multiplier do not create enough separation at this elimination stage."},{"hypothesis_id":"H5","search_queries":["SAP IBP planning override validity date expiration manual forecast adjustment official","Oracle demand planning override start date end date official documentation","planning override expiration date renewable override supply chain planning official documentation","supply planning manual overrides persist exception expiration research"],"sources":[{"source_id":"H5-S1","title":"Oracle Demand Planning Implementation and User's Guide","publisher":"Oracle","url":"https://docs.oracle.com/cd/E26401_01/doc.122/e48759/T295435T478906.htm","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Oracle demand-planning events can modify forecasts for explicit From and To dates.","Events can be scoped to products and other dimensions and associated with plans or scenarios.","Date validation constrains detailed event periods to their parent start and end dates, while omitted end dates can extend effects through the plan horizon."]},{"source_id":"H5-S2","title":"Oracle Service Parts Planning Implementation and User Guide","publisher":"Oracle","url":"https://docs.oracle.com/cd/E18727_01/doc.121/e13338/T515331T515344.htm","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Planners can manually override forecast and demand-schedule values at forecasting-bucket level.","Some manual changes are temporary and are erased when a new demand-planning scenario is published.","Manual override entries can be selected and deleted by planners."]}],"closest_analogue":"Date-bounded planning events and bucket-level manual overrides that can be explicitly deleted or cleared when a new scenario is published.","overlap":"Planning systems already support time-scoped forecast modifications, dimensional targeting, manual overrides, temporary override behavior, and removal of override entries.","remaining_difference":"The located analogue does not show creation-time leases with a named owner, evidence-based renewal, dependency checks against committed orders or allocations, and a reversible quarantine before removal. These features can be tested by measuring rationale-less active overrides and service failures after expiry.","classification":"POSSIBLE_DISTINCTION","disposition":"ADVANCE","rationale":"Date-bounded planning interventions are known, but the accountable renewable-lease workflow remains meaningfully different from ordinary event dates or scenario clearing and has a clear comparative test."}],"nominated_ids":["H3","H5"],"replenishment_recommended":false}