{"schema_version":1,"assessment_id":"eoa_inverse_innovation_exp03_opportunity320_20260801","source_experiment_id":"eoa_inverse_innovation_exp03_full320_20260801","cell_id":"layer_decay_and_expiration_management__architecture_urban_planning","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"architecture_urban_planning","title":"Provision-Level Lifecycle Management for Municipal Zoning Codes","opportunity_summary":"Create inspectable, nonbinding lifecycle metadata for zoning provisions, apply dependency and retention checks, route proposed dispositions through lawful municipal authority, and preserve reconstructable history. The proposal targets operative-looking superseded or uncertain provisions but remains an untested hypothesis with unknown local prevalence and unsearched prior art.","adopter_authorizer":"Municipal planning, legal, records, and code-publication staff could adopt the workflow; municipal counsel validates legal constraints, while the city council or lawfully delegated zoning authority alone authorizes legal-status changes through required procedures.","scores":{"meaningful_impact":{"score":4,"rationale":"If lifecycle-related conflicts are materially present, clearer controlling provisions and preserved historical reconstruction could reduce review delay and erroneous application while protecting reliance interests. The packet provides no evidence of prevalence or realized impact, preventing the highest score."},"stakeholder_pull":{"score":3,"rationale":"Planning, legal, records, applicants, property interests, and neighborhood groups have plausible reasons to value clearer status and history, but the candidate contains no documented demand, adoption request, or willingness to fund the workflow."},"incremental_advantage":{"score":4,"rationale":"The continuing provision-level states, dependency gates, exception revalidation, supersession markers, and restoration controls offer a specific advantage over reactive amendment and a one-time rewrite. Whether the added review burden produces net improvement is untested."},"distinctiveness_plausibility":{"score":3,"rationale":"The combination is coherently differentiated from the stated baseline and nearest rival, but prior art is explicitly unsearched and may already exist in continuous codification, sunset review, records, or historical-publication practice."},"technical_implementability":{"score":3,"rationale":"Provision identities, metadata, labels, inventories, and archives appear implementable in a bounded shadow setting, while external cross-references, tacit reliance, vested interests, litigation history, and reconstruction create difficult completeness requirements."},"adoption_authority_feasibility":{"score":3,"rationale":"The candidate clearly allocates inventory, legal validation, and status-change authority. Adoption nevertheless depends on counsel, records coordination, public procedures, and a politically accountable authority, with no evidence of institutional willingness."},"evidence_readiness":{"score":4,"rationale":"A nonbinding 90-day pilot, explicit comparators, measurable outcomes, problem and intervention falsifiers, and halt conditions are already specified. Baseline data, sampling rules, and decision thresholds still require definition."},"safety_net_benefit":{"score":5,"rationale":"The shadow pilot leaves official law unchanged, prohibits automatic repeal and record destruction, preserves audit and historical materials, assigns legal authority correctly, and requires halting for missed dependencies, reconstruction failure, confusion, or unlawful automation."},"scalability":{"score":3,"rationale":"Provision-level identities and lifecycle states could extend across a code, but legal variation, manual dependency tracing, public procedures, archive quality, and municipality-specific systems may make scaling labor-intensive."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"A 90-day nonbinding shadow pilot covering one overlay district or no more than 100 provisions, including inventory, dependency tracing, archival-restoration testing, counsel review, comparison with ordinary review, stakeholder comprehension checks, and evaluation.","confidence":"MODERATE","assumptions":["Existing zoning texts, maps, amendments, and historical records are accessible to the participating municipality.","The pilot uses existing staff and limited analytical or metadata tooling rather than building a production platform.","No legal-status changes, formal repeal proceedings, or destructive records operations occur."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Municipality-wide preparation after successful evidence: provision inventory, lifecycle schema, legal and records protocols, dependency mapping, archive design, workflow configuration, staff training, and integration planning.","confidence":"LOW","assumptions":["The municipality has a code of moderate complexity and usable digital source materials.","Substantial staff and counsel review is required because automated signals cannot establish legal status.","The candidate does not specify municipality size, record quality, software architecture, or procurement requirements."]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"First operational review cycle, including authorized disposition recommendations, counsel validation, public-process support, publication of supersession markers, historical-access testing, system integration, and user communications.","confidence":"LOW","assumptions":["Launch covers one municipality and phases dispositions rather than processing the entire code simultaneously.","Legally effective changes continue through existing notice, hearing, and legislative procedures.","Material litigation, extensive digitization, or replacement of the official publication platform could move the resource requirement to a higher band."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Recurring provision review, dependency and hold maintenance, exception revalidation, archive preservation, publication updates, counsel oversight, training, audit, software support, and evaluation.","confidence":"LOW","assumptions":["Reviews are periodic and risk-prioritized rather than exhaustive every year.","The lifecycle workflow becomes part of ongoing planning, legal, records, and publication operations.","Municipality size, amendment volume, vendor costs, and procedural workload remain unspecified."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"YES","reason":"The candidate identifies concrete audit-observable conditions—operative-looking superseded rules, broken references, uncertain status, and lifecycle-related review errors—and supplies a falsifier. Their prevalence in any municipality remains unestablished."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"Planning, legal, records, and publication staff are identifiable operational adopters, and the council or lawfully delegated zoning authority is explicitly identified as the legal authorizer."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal claims that continuing provision-level lifecycle controls improve controlling-rule identification and conflict detection beyond ordinary review or one-time consolidation, with specified failure outcomes."},"bounded_next_evidence_step":{"status":"YES","reason":"The sealed candidate bounds a nonbinding 90-day shadow pilot to one overlay district or at most 100 provisions and names comparisons, adverse outcomes, and halt conditions."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"Legal status remains with authorized officials; the pilot changes no operative law, and explicit exclusions, counsel review, archival preservation, and rollback conditions address the identified immediate hazards."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"The pilot has a bounded scope that supports a broad first-evidence band, but municipality-wide code size, record condition, systems integration, procurement, procedural volume, and recurring legal workload are unspecified."}},"blocking_evidence":["No provision-level audit establishes whether lifecycle-related defects are materially present rather than rare or already handled adequately.","No comparative evidence shows improved controlling-provision identification or conflict detection relative to ordinary review or one-time consolidation.","Dependency completeness, including external and tacit reliance, has not been demonstrated.","False-stale flags, missed dependencies, archival-restoration failures, user confusion, and staff burden have not been measured.","Prior art in continuous codification, sunset review, zoning-code audits, records schedules, and historical-code publication is unsearched.","Municipal counsel and affected users have not validated that shadow labels can remain clearly distinguishable from legal status."],"next_evidence_step":"With one municipal planning, legal, and records partner, run the specified 90-day nonbinding shadow pilot on one overlay district or no more than 100 provisions. Compare lifecycle-assisted review with ordinary review on time to identify controlling provisions, conflict detection, staff effort, and restoration success; record false-stale flags, missed dependencies, and user confusion. Treat a finding of virtually no lifecycle defects, no comparative improvement, any missed sampled dependency, failed reconstruction, or material status confusion as a falsifier or halt condition, leaving official law unchanged.","research_questions":["How many sampled provisions exhibit operative-looking supersession, broken references, uncertain status, expired predicates, or lifecycle-related review errors?","Does lifecycle-assisted review improve controlling-provision identification or conflict detection over ordinary review or one-time consolidation?","What false-stale and missed-dependency patterns arise, especially for older protections, nonconforming uses, vested approvals, and external references?","Can staff and public users reliably distinguish lifecycle metadata, operative law, and historical material?","Can every sampled historical state be reconstructed without reducing practical access to archived materials?","How much planning, legal, records, publication, and stakeholder-review effort does the workflow add or displace?","Which existing code-maintenance, sunset, audit, records, or historical-publication practices already implement the claimed mechanisms?","What formal authority, notice, hearing, retention, litigation-hold, and publication requirements constrain later operational use?"] ,"recommendation":"PARTNERED_RESEARCH","uncertainty_constraints":["Closed-book assessment: no external validation of prevalence, prior art, adoption demand, realized impact, or market size was available.","The proposal is explicitly a hypothesis, and generator confidence is not empirical evidence.","Cost bands are resource-equivalent planning ranges, not quotations; municipality size and code complexity are unknown.","Legal validity cannot be inferred from age, lifecycle metadata, storage location, usage frequency, or an automated score.","A successful shadow pilot would support local utility but would not by itself establish world novelty or safe generalization across jurisdictions."],"closed_book_prior_art_boundary":"Prior art was explicitly unsearched. This assessment makes no novelty, prevalence, or superiority claim beyond the candidate's internal comparison with reactive amendment and one-time consolidation; continuous codification, sunset review, zoning-code audits, records schedules, and historical-code publication require external research."}