{"schema_version":1,"assessment_id":"eoa_inverse_innovation_exp03_opportunity320_20260801","source_experiment_id":"eoa_inverse_innovation_exp03_full320_20260801","cell_id":"deadweight_loss_reduction__military_strategic_studies","archetype_slug":"deadweight_loss_reduction","domain_slug":"military_strategic_studies","title":"Bounded Reallocation of Eligible Joint ISR Capacity","opportunity_summary":"Test whether commander-approved transfer of eligible ISR capacity can reduce usable idle windows and improve priority-weighted fulfillment relative to fixed allocations and faster manual exceptions, while preserving reserve, legal, security, safety, deconfliction, coalition, and processing constraints. The sealed candidate does not establish that stale allocation is materially prevalent or that the mechanism is distinctive.","adopter_authorizer":"The prospective adopter is a joint collection-management organization; authorization would rest with the joint force commander or formally delegated collection-management authority, together with applicable legal, security, platform-safety, coalition, and oversight authorities.","scores":{"meaningful_impact":{"score":4,"rationale":"If feasible high-priority requirements materially coexist with locked usable capacity, reallocation could improve time-sensitive mission support from fixed short-run capacity. Impact remains conditional because the candidate supplies no evidence of the wedge's prevalence or magnitude."},"stakeholder_pull":{"score":3,"rationale":"Requesting units and collection managers have a proposal-specific reason to value improved fulfillment, while releasing units and commanders may resist loss of reserve or future access. No sealed evidence demonstrates demand, sponsorship, or willingness to change allocations."},"incremental_advantage":{"score":3,"rationale":"The controlled-transfer rule makes a clear incremental change beyond the nearest rival's faster manual exceptions and has specified outcome measures. Whether transferability adds benefit beyond administrative acceleration is wholly untested."},"distinctiveness_plausibility":{"score":3,"rationale":"The mechanism is coherently distinguished from fixed allocations and prioritized manual exceptions, but prior-art status is explicitly unsearched. Closed-book evidence cannot establish novelty or uncommonness."},"technical_implementability":{"score":3,"rationale":"A synthetic or authorized historical shadow comparison for one exercise and asset class appears implementable, but operational implementation must encode compatibility, reserve, geometry, classification, deconfliction, processing, and recall constraints that may prevent reliable transfer."},"adoption_authority_feasibility":{"score":3,"rationale":"A joint force commander or delegated collection-management authority is identified, but adoption also depends on legal, security, safety, coalition, oversight, and component cooperation. The candidate provides no evidence that these parties would authorize an operational rule."},"evidence_readiness":{"score":4,"rationale":"The packet specifies three comparators, observable measures, problem and intervention falsifiers, a non-live bounded setting, protected metrics, and halt conditions. Readiness is limited by uncertain access to appropriately authorized and sufficiently representative data."},"safety_net_benefit":{"score":4,"rationale":"Reservation floors, recall rights, expiry, audits, hard legal and safety gates, a shadow-only first test, and explicit rollback conditions provide substantial protection against foreseeable harms. Their adequacy has not yet been demonstrated."},"scalability":{"score":3,"rationale":"The rule could in principle be repeated across planning cycles, but asset compatibility, classification, coalition access, platform constraints, and local command priorities may require substantial context-specific configuration. No cross-setting evidence is supplied."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"One time-bounded shadow study for one exercise and one ISR asset class, including authorized or synthetic data preparation, constraint coding, three-rule comparison, protected-metric review, and a decision memorandum.","confidence":"LOW","assumptions":["Existing planning records or credible synthetic inputs can be accessed without developing a new classified data system.","A small multidisciplinary team can complete collection-management, analytical, legal, security, safety, and evaluation work.","No live collection or platform modification occurs."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Design and approval of a limited operational pilot for one command and asset class, including workflow integration, access controls, audit and recall functions, training, contingency procedures, and independent evaluation preparation.","confidence":"LOW","assumptions":["Existing tasking and collection-management systems can be configured rather than replaced.","The pilot remains limited to eligible capacity and named participants.","Required accreditation, coalition coordination, or software integration does not become enterprise-scale."]},"operational_launch":{"band_2026_usd":"1M_TO_5M","scope":"Launch within one joint operational organization across a bounded portfolio of compatible ISR capacity, with system integration, staffing, training, governance, monitoring, legal and security review, and evaluation.","confidence":"LOW","assumptions":["Launch does not require new ISR platforms or major processing infrastructure.","Multiple components participate but enterprise-wide or multinational rollout is excluded.","Protected constraints and reserve rules can be represented in operational workflows."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Recurring operation for the bounded organizational deployment, including collection-management labor, rule maintenance, auditing, access reviews, training, software support, incident response, and periodic outcome evaluation.","confidence":"LOW","assumptions":["The mechanism uses existing collection-management personnel and systems with incremental support.","Processing demand does not require major new analyst or computing capacity.","Scope remains one joint organization rather than force-wide adoption."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"YES","reason":"The candidate defines an observable mismatch: feasible validated high-priority requirements remain unfilled while usable capacity is locked, unused, or assigned lower priority. Material prevalence still requires evidence, but the problem and its falsifier are externally testable."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"The joint collection-management organization is the identifiable adopter, and the joint force commander or formally delegated collection-management authority is named as the decision authority subject to controlling reviews."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal claims that controlled transfer of eligible capacity will outperform both fixed allocations and faster manual exceptions on priority-weighted fulfillment or usable idle capacity without breaching protected metrics."},"bounded_next_evidence_step":{"status":"YES","reason":"The sealed candidate authorizes a non-live, time-bounded shadow comparison using synthetic or appropriately authorized historical data for one exercise and asset class."},"no_unresolved_safety_or_authority_stop":{"status":"UNCERTAIN","reason":"Hard gates and rollback conditions are specified, but the candidate identifies as a failure condition the possibility that transferable capacity cannot be defined without weakening accountability or protected constraints. Relevant authorities have not endorsed the test or operational rule."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"A narrow shadow study can be scoped into a broad resource band, but operational breadth, system integration, accreditation, data-access requirements, coalition involvement, and downstream processing needs are not specified well enough for a confident deployment range."}},"blocking_evidence":["Whether feasible high-priority unmet requirements materially coexist with locked usable capacity after reserve, compatibility, geometry, weather, legal, classification, operator, and processing constraints are coded.","Whether allocation status predicts nonfulfillment after distinguishing stale allocation from approval latency, true scarcity, and infeasible requests.","Whether controlled transfer outperforms both fixed allocation and faster manual exceptions without exceeding preset bounds for readiness loss, violations, workload, volatility, gaming, or inequitable access.","Whether accountable authorities can define eligible transferable capacity, reservation floors, recall rights, and audit rules without weakening command responsibility or protected constraints.","Whether materially similar allocation or reassignment mechanisms already exist, since prior art is unsearched."],"next_evidence_step":"Conduct one non-live shadow reallocation for one exercise and ISR asset class using synthetic or appropriately authorized historical data. Pre-code reserve status, request feasibility, compatibility, legal and classification restrictions, deconfliction, operator limits, and processing capacity; then compare fixed allocation, prioritized manual exceptions, and controlled transfer on priority-weighted fulfillment, usable idle capacity, reassignment latency, backlog, workload, access distribution, and protected violations. Reject the problem hypothesis if feasible unmet priority demand does not materially coexist with locked usable capacity, and reject the intervention if controlled transfer fails to beat both comparators or exceeds preset protected-metric bounds.","research_questions":["How much apparent unused capacity remains genuinely usable after justified reserve and all operational constraints are applied?","Is nontransferability a material predictor of unmet feasible requirements beyond approval latency and total scarcity?","What eligibility, reservation, recall, expiry, and audit rules preserve commander accountability and contingency readiness?","Does controlled transfer improve priority-weighted fulfillment relative to both baseline and manual exceptions?","Does the rule induce priority inflation, hoarding, workload, decision volatility, processing congestion, or displacement of less powerful units?","Can representative data be accessed and evaluated without unauthorized disclosure or coalition-access violations?","What comparable mechanisms or prior art exist, and what incremental claim, if any, remains distinctive?","What systems integration, accreditation, staffing, and recurring governance would a bounded operational pilot require?"] ,"recommendation":"PRIOR_ART_RESEARCH","uncertainty_constraints":["No external evidence establishes problem prevalence, effect magnitude, stakeholder demand, prior art, or realized impact.","Apparent slack may predominantly reflect justified reserve, incompatibility, infeasible requests, downstream bottlenecks, or true scarcity.","Exercise or historical data may not represent adversarial, classified, coalition, or time-sensitive operational conditions.","Cost bands are low-confidence resource-equivalent estimates because implementation architecture and organizational scope are unspecified.","A favorable shadow result would not by itself authorize live tasking changes or establish operational safety."],"closed_book_prior_art_boundary":"Prior art is explicitly unsearched. This assessment makes no claim about novelty, prevalence, existing military allocation practices, market size, or comparable deployed systems; distinctiveness remains an external-research question."}