{"schema_version":1,"research_id":"eoa_inverse_innovation_exp04_external_evaluation_20260802","source_assessment_id":"layer_decay_and_expiration_management__logistics_supply_chain:PROPOSAL_FIRST:v0","cell_id":"layer_decay_and_expiration_management__logistics_supply_chain","search_queries":["site:docs.oracle.com transportation management override rule expiration planning constraint","site:help.sap.com transportation management planning profile incompatibility validity date override","supply chain planning stale overrides exception management temporary constraints","transportation management temporary overrides governance expired rules","site:docs.oracle.com \"override\" \"Transportation Management\" \"effective date\"","site:docs.oracle.com \"override\" \"shipment\" \"expiration\" transportation management","site:help.sap.com transportation planning \"validity period\" incompatibility","site:learn.microsoft.com supply chain planning override expiration temporary constraint","supply chain planning human overrides forecast accuracy empirical study planner overrides","transportation planning manual overrides stale rules data quality study","site:sciencedirect.com supply chain planners judgmental overrides forecast empirical","site:mit.edu supply chain planning overrides temporary constraints case study","site:bls.gov/oes/2025 operations research analysts annual mean wage","site:bls.gov/ooh logisticians median pay 2025","site:aws.amazon.com/s3/pricing Glacier Deep Archive pricing restore requests","site:nist.gov records retention disposal audit logging legal hold guidance","site:archives.gov records management disposition schedule legal hold records must not destroy","site:nist.gov \"Audit Record Retention\" organization-defined","site:law.cornell.edu FRCP 37(e) electronically stored information preservation","site:justice.gov legal hold records preservation guidance electronically stored information","site:iso.org ISO 15489 records management appraisal disposition controls metadata","site:iso.org ISO 30301 records management requirements disposal retention","site:archives.gov records management metadata disposition audit trail electronic records","site:learn.microsoft.com retention labels disposition review records management","site:oracle.com/customers transportation management customer planning disruption logistics Oracle OTM","site:sap.com/about/customer-stories transportation management planning customer SAP TM","site:oracle.com \"Oracle Transportation Management\" customer story logistics planning","site:sap.com \"SAP Transportation Management\" customer story"],"sources":[{"source_id":"SRC1","title":"Order Base/Release: Constraints","publisher":"Oracle","url":"https://docs.oracle.com/en/cloud/saas/transportation/26c/otmol/planning/order_manager/order_plan_constraints.htm","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2026","accessed_at":"2026-08-02","claims_supported":["Oracle Transportation Management permits order- and leg-level constraints controlling carrier, mode, rate, itinerary, bundling, and shipment creation.","Specified rate and itinerary constraints take precedence over the referenced object's active state and effective or expiration dates.","An obsolete order-level constraint can therefore continue influencing shipment construction unless it is separately identified and governed."]},{"source_id":"SRC2","title":"Itinerary Leg Manager","publisher":"Oracle","url":"https://docs.oracle.com/en/cloud/saas/transportation/26a/otmol/planning/itinerary_manager/itinerary_leg_manager.htm","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2026","accessed_at":"2026-08-02","claims_supported":["Oracle Transportation Management already gives equipment-capacity overrides effective and expiration dates.","Override applicability is evaluated against order pickup and delivery windows and can be refined with lead time.","Validity-bounded transportation overrides are established product functionality and close prior art."]},{"source_id":"SRC3","title":"Condition (SAP Library—Transportation Planning/Vehicle Scheduling)","publisher":"SAP","url":"https://help.sap.com/saphelp_snc70/helpdata/EN/dd/490c404a435509e10000000a1550b0/content.htm","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"not stated","accessed_at":"2026-08-02","claims_supported":["SAP transportation-planning conditions are defined by a validity period and filter fields covering orders, locations, vehicles, and shipments.","Conditions may be local to a particular optimization profile or function.","Validity-scoped planning rules are established practice in another major platform."]},{"source_id":"SRC4","title":"Profiles and Settings","publisher":"SAP","url":"https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/e3dc5400c1cc41d1bc0ae0e7fd9aa5a2/e2199850143047378b9ed7edde1a3b20.html","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2026-02","accessed_at":"2026-08-02","claims_supported":["SAP transportation-planning profiles group capacities, costs, optimizer settings, incompatibilities, and carrier-selection settings.","SAP documents authorization objects controlling who can create or change planning profiles, selection profiles, incompatibility settings, conditions, and freight-unit rules.","SAP recommends automatic change recording because otherwise consistency across profiles and settings is difficult to ensure.","Role-gated configuration and auditable change capture are technically and organizationally feasible."]},{"source_id":"SRC5","title":"Emerson gains supply chain responsiveness and visibility with Oracle Cloud","publisher":"Oracle","url":"https://www.oracle.com/europe/customers/emerson/","source_class":"COMMERCIAL_FIRST_PARTY","publication_date":"not stated","accessed_at":"2026-08-02","claims_supported":["Emerson is an identifiable Oracle Transportation Management adopter.","Emerson's Director of Supply Chain Systems and Solutions expressed a need for clearer, integrated supply-chain information so experts could solve problems instead of hunting through spreadsheets.","Emerson uses transportation-management capabilities to reroute freight during hurricanes, floods, volcanoes, and other disruptions.","Transportation-control and supply-chain-systems leadership constitute plausible pilot authorizers, although Emerson did not express a specific need for override-expiration governance."]},{"source_id":"SRC6","title":"Profit Implications of Judgmental Adjustments to Forecast Inputs: Evidence from a Large-Scale Field Experiment","publisher":"INFORMS, Management Science","url":"https://pubsonline.informs.org/doi/abs/10.1287/mnsc.2024.06321","source_class":"PRIMARY_RESEARCH","publication_date":"2025-07-25","accessed_at":"2026-08-02","claims_supported":["A large-scale field experiment at an automotive spare-parts retailer confirms that human overrides of supply-chain algorithm inputs occur and can materially change profit outcomes.","The experiment found a 4.92% average profit increase from allowing judgmental forecast-input adjustments, showing that blanket suppression of overrides would be unsafe.","Override governance must preserve valuable human intervention and evaluate operational outcomes rather than assuming overrides are harmful."]},{"source_id":"SRC7","title":"Learn about records management","publisher":"Microsoft","url":"https://learn.microsoft.com/en-us/purview/records-management","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2025-09-26","accessed_at":"2026-08-02","claims_supported":["Microsoft Purview implements retention labels, event-based retention, disposition review, deletion evidence, activity logging, and specific records-management permissions.","Regulatory-record controls can prevent deletion and prevent shortening retention periods.","Generic lifecycle governance, authority separation, preservation exceptions, and auditable disposition are established product capabilities outside transportation planning."]},{"source_id":"SRC8","title":"Working with archived objects","publisher":"Amazon Web Services","url":"https://docs.aws.amazon.com/AmazonS3/latest/userguide/archived-objects.html","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"not stated","accessed_at":"2026-08-02","claims_supported":["Archived objects can be restored through a console, API, SDK, command line, or batch operations.","Cold archives are not immediately accessible; restoration can require minutes or hours and creates a temporary accessible copy.","Archive restoration and scheduled restore testing are technically conventional, but successful object restoration alone does not prove that a historical planning model can interpret or replay the override."]}],"problem_evidence":{"support":"MODERATE","rationale":"The exact proposed prevalence and realized harm of stale shipment-planning overrides were not found in public evidence. However, Oracle documents that order constraints can dictate carrier, mode, rate, and itinerary and can override inactive status and recorded expiration dates, establishing a concrete persistence-and-influence pathway. Emerson confirms disruption rerouting and the operational need for clearer integrated planning information. The INFORMS field experiment independently confirms that human supply-chain overrides materially affect outcomes, while also showing that overrides can be beneficial. The problem visibly exists as a credible control risk, but its frequency, backlog size, and cost in any adopter remain unmeasured.","source_ids":["SRC1","SRC5","SRC6"]},"stakeholder_evidence":{"support":"MODERATE","rationale":"Emerson is an identifiable OTM adopter, and its Director of Supply Chain Systems and Solutions expressed needs for clearer decision information, disruption response, and reduced spreadsheet searching. SAP documentation identifies authorization objects that make transportation-planning configuration owners and administrators credible authorizers. Neither source expressly requests an expiring override ledger, so pull for the specific intervention remains inferential rather than demonstrated.","source_ids":["SRC4","SRC5"]},"prior_art":{"proximity":"SUBSTANTIAL_COLLISION","closest_analogues":[{"name":"Oracle OTM effective/expiration-dated equipment capacity overrides","similarity":"Same domain, same object type, and the core lifecycle mechanism of bounding a temporary transportation-planning override by effective and expiration dates.","remaining_difference":"The documentation does not show a unified inventory of heterogeneous overrides, owner/reason metadata, cross-object live dependency blocking, reversible deactivation, tombstones, or historical-plan replay.","source_ids":["SRC2"]},{"name":"SAP validity-scoped transportation-planning conditions and governed profiles","similarity":"Transportation-planning rules already have validity periods, scoped applicability, authorization controls, and change-recording mechanisms.","remaining_difference":"No reviewed source shows lifecycle scoring, exception-hold revalidation, quarantine, deletion evidence, or dependency-aware retirement across multiple override classes.","source_ids":["SRC3","SRC4"]},{"name":"Microsoft Purview records lifecycle and disposition controls","similarity":"Implements retention schedules, event-triggered retention, role separation, holds, disposition review, audit logging, and proof of deletion—the proposal's generic governance layer.","remaining_difference":"It governs content records rather than executable transportation-planning constraints and does not test plan-level dependencies or replay outcomes.","source_ids":["SRC7"]},{"name":"Amazon S3 archive and restore workflow","similarity":"Provides the archive, temporary restoration, API, and batch machinery needed for periodic restore tests.","remaining_difference":"It establishes byte-level retrievability, not semantic interpretability or successful replay in the current planning engine.","source_ids":["SRC8"]}],"distinctive_claim_remaining":"Relative to native validity dates, configuration audit trails, and generic records-management workflows, a transportation-specific ledger that combines heterogeneous override inventory, accountable ownership, live dependency blocking across open shipments and reconstruction objects, reversible exclusion from new planning, durable successor/deletion evidence, and sampled semantic replay will reduce stale active constraints and reviewer effort without changing valid plan decisions or losing reconstructability. This is contrastive and falsifiable, but no reviewed source establishes its superiority or novelty.","confidence":"HIGH"},"implementation_evidence":{"support":"MODERATE","rationale":"Core pieces are technically conventional: transportation platforms expose constraints and validity dates; SAP documents scoped permissions and configuration change recording; Purview demonstrates lifecycle states, retention, holds, disposition review, and deletion evidence; and AWS supports programmable archive restoration. Major unverified dependencies remain: complete export APIs, identity resolution across tickets and spreadsheets, visibility into runtime/string/external references, historical optimizer reproducibility, restricted shipment-data access, and organization-specific retention authority. A read-only pilot is feasible; safe production deactivation is not yet established.","source_ids":["SRC1","SRC2","SRC4","SRC7","SRC8"]},"scores":{"meaningful_impact":{"score":3,"rationale":"Planning constraints directly select or exclude modes, providers, rates, and itineraries, so stale constraints could affect service and cost. Actual prevalence and effect size are missing.","source_ids":["SRC1","SRC5"]},"stakeholder_pull":{"score":3,"rationale":"An identifiable OTM adopter wants clearer disruption information and less spreadsheet hunting, but no stakeholder has expressly requested override-lifecycle management.","source_ids":["SRC5"]},"incremental_advantage":{"score":2,"rationale":"Native validity periods, permissions, change recording, and generic disposition workflows cover much of the mechanism. The remaining advantage is the integrated dependency/replay safety layer, whose benefit is untested.","source_ids":["SRC2","SRC3","SRC4","SRC7"]},"distinctiveness_plausibility":{"score":2,"rationale":"The specific coupling may differ from reviewed products, but the component practices are established and the search was not exhaustive of vendor extensions, consulting implementations, patents, or proprietary customer configurations.","source_ids":["SRC2","SRC3","SRC7","SRC8"]},"technical_implementability":{"score":4,"rationale":"Existing platforms demonstrate validity metadata, permissions, audit trails, retention workflows, APIs, and archive restoration. Semantic dependency tracing and faithful plan replay are the principal technical uncertainties.","source_ids":["SRC2","SRC4","SRC7","SRC8"]},"adoption_authority_feasibility":{"score":3,"rationale":"Supply-chain-systems leadership and configuration owners are identifiable, and SAP exposes role-gated change authority. Cross-functional approval for compliance, disputes, and production changes is organization-specific and unverified.","source_ids":["SRC4","SRC5"]},"evidence_readiness":{"score":2,"rationale":"Public evidence supports the mechanism and nearby problem, but the decisive evidence—override inventory, dependency completeness, replay effects, reviewer workload, and restore fidelity—requires proprietary data and fieldwork.","source_ids":["SRC1","SRC6"]},"safety_net_benefit":{"score":4,"rationale":"Read-only review, dependency blocking, quarantine, holds, audit evidence, and non-production replay directly mitigate premature deletion and preserve valuable human overrides.","source_ids":["SRC6","SRC7","SRC8"]},"scalability":{"score":3,"rationale":"Metadata, APIs, batch restoration, and role-based governance can scale, but heterogeneous systems, spreadsheets, external consumers, and local retention rules make cross-enterprise rollout integration-heavy.","source_ids":["SRC4","SRC5","SRC8"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"Four-week, read-only study of no more than 100 overrides in one facility-to-region scope, including extraction, two-planner labeling, dependency review, historical replay, and ten archive-restore checks.","confidence":"MODERATE","assumptions":["Existing staff can export override and historical-plan data without vendor customization.","Approximately 200-500 loaded labor hours are required across planners, an analyst, a TMS administrator, and a compliance reviewer.","No production configuration or paid enterprise software procurement is included."],"source_ids":["SRC4","SRC5"]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Design and build a production-capable ledger for one business unit, including data connectors, lifecycle schema, permissions, audit store, dependency checks, quarantine workflow, and non-production replay harness.","confidence":"LOW","assumptions":["Six to twelve months of a small cross-functional product, integration, operations, and compliance team.","Existing TMS, identity, analytics, and archive platforms are reused.","Vendor professional services and difficult legacy connectors could move the estimate beyond this band."],"source_ids":["SRC1","SRC4","SRC7","SRC8"]},"operational_launch":{"band_2026_usd":"1M_TO_5M","scope":"Multi-facility production rollout with legacy inventory, workflow integration, policy approval, training, monitoring, validation, and controlled quarantine—not hard deletion.","confidence":"LOW","assumptions":["Rollout spans several facilities or regions and multiple override sources.","A dedicated program team, vendor integration support, user acceptance testing, compliance review, and change management are required.","The estimate excludes replacement of the underlying TMS or ERP."],"source_ids":["SRC4","SRC5","SRC7"]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Ongoing ownership, policy revalidation, exception review, dependency-monitor maintenance, replay testing, archive restore drills, support, and audit evidence.","confidence":"LOW","assumptions":["Two to five FTE-equivalents are distributed across product ownership, TMS administration, data engineering, planning operations, and compliance.","Cloud storage is not the main cost driver; review labor and integration maintenance dominate.","Scope remains one enterprise rather than a commercial multi-tenant product."],"source_ids":["SRC4","SRC7","SRC8"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"Official Oracle documentation establishes that executable order constraints can supersede inactive and expired planning objects, while adopter and experimental evidence show that disruption controls and human overrides materially affect supply-chain decisions. Prevalence remains unknown but the problem pathway is externally supported.","source_ids":["SRC1","SRC5","SRC6"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"Emerson is an identifiable OTM adopter with an expressly identified Director of Supply Chain Systems and Solutions, and SAP documents authorization controls for transportation-planning settings. Specific willingness to sponsor this pilot is not established.","source_ids":["SRC4","SRC5"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"The remaining claim compares the coupled ledger, dependency gate, quarantine, and semantic replay against current manual review and native validity-date controls using measurable review and plan outcomes.","source_ids":["SRC2","SRC3","SRC7"]},"bounded_next_evidence_step":{"status":"YES","reason":"A four-week, one-scope, 100-override, read-only comparison with copied historical plans, explicit metrics, and no production changes is bounded and reversible.","source_ids":["SRC4","SRC8"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The next step is read-only, uses non-production copies, preserves every source override, and requires no waiver of legal, compliance, contractual, dispute, or safety holds. Production deactivation remains outside authorization.","source_ids":["SRC4","SRC7"]},"credible_cost_scope_and_range":{"status":"YES","reason":"All four bands identify a concrete scope, staffing and platform assumptions, exclusions, and confidence. Vendor pricing and proprietary integration complexity remain gaps but do not prevent resource-equivalent ranges.","source_ids":["SRC4","SRC5","SRC7","SRC8"]}},"next_evidence_step":"Partner with one transportation-control owner using a system that supports persistent planning constraints. For four weeks, sample at most 100 overrides across age and class bands in one facility-to-region scope. In a randomized crossover, have two planners review each candidate once using the current manual/native-validity workflow and once using a read-only ledger containing owner, reason, scope, age, last activation, supersession, retention class, and dependency results. Trace open shipments, reservations, tenders, disputes, reports, and replay references; then replay eight weeks of copied plans with only jointly rated high-confidence candidates omitted. Measure inventory coverage, missing ownership or expiry, reviewer time, inter-rater agreement, dependency blocks, changed carrier/mode/route/feasibility decisions, and restoration/interpretation of ten archived samples. Pre-register falsifiers: fewer than 10% of active sampled overrides lack a current owner, valid end condition, or explicit supersession; ledger inventory coverage below 95%; no improvement of at least 20% in median review time without lower agreement; any unanticipated changed plan decision among orders touched by a supposedly safe candidate; any known live dependency missed by the trace; or fewer than 10 of 10 archived samples restored and interpreted. No production override is changed or deleted.","blocking_evidence":["No public estimate of how many shipment-planning overrides persist beyond their useful context or lack owners and expiry conditions.","No causal evidence links stale transportation overrides specifically to premium freight, infeasibility, delay, or manual replanning in an identified adopter.","No evidence establishes the completeness of dependency tracing across TMS, ERP, spreadsheets, partner systems, disputes, and runtime references.","No organization-specific retention schedule, privacy classification, contractual obligation, or legal-hold process has been reviewed.","No exhaustive comparison has been made against vendor extensions, system-integrator implementations, patents, or proprietary customer configurations.","No live adopter has committed staff, data access, or authorization for the proposed study."],"research_disposition":"PARTNERED_RESEARCH_PROGRAM","world_novelty_boundary":"The search establishes substantial collision with effective/expiration-dated transportation overrides, validity-scoped planning conditions, governed configuration, generic records lifecycle controls, and archive restoration. It does not measure world novelty, patentability, freedom to operate, market size, proprietary implementations, realized impact, or whether the remaining integrated claim has previously been implemented. No novelty conclusion should be inferred.","arm":"PROPOSAL_FIRST","candidate_version":0,"controller_recommendation":{"action":"STOP_EMPIRICAL_RESEARCH_NEEDED","repairable":true,"material_progress_observed":true,"progress_targets":["Secure a named transportation-control partner and written authorization for read-only data access and historical replay.","Measure override accumulation, ownership, expiry, supersession, and active-use prevalence in one proprietary scope.","Validate dependency-trace recall against system owners and deliberately seeded known references.","Run the pre-registered baseline-versus-ledger crossover and non-production replay with explicit falsifiers.","Obtain records-management, trade-compliance, privacy, and legal approval for the lifecycle classes and quarantine policy.","Complete a focused differentiation review of the partner's native TMS features, extensions, and integrator configurations before building custom functionality."],"reason":"Web research establishes a real mechanism, credible adopters, implementation feasibility, and substantial prior-art collision, but cannot determine local prevalence, dependency completeness, comparative workflow benefit, or safe plan effects. Those decisive questions require proprietary operational data, planner participation, and historical simulation; further general web search cannot close them."}}