{"schema_version":1,"research_id":"eoa_inverse_innovation_exp06_external_evaluation_20260803","source_assessment_id":"representation_independent_interface_contract__nanotechnology:P1:v0","cell_id":"representation_independent_interface_contract__nanotechnology","search_queries":["site:nist.gov nanofab GDSII design file electron beam lithography","site:klayout.de/doc Region class geometry API DRC","site:si2.org OpenAccess API standard IC design database","OGC Simple Features standard geometry interface operations official","NIST NanoFab electron beam lithography GDS file requirements CAD official","site:stanford.edu nanofabrication GDS design rules electron beam lithography","Si2 OpenAccess standard API design database official documentation","nanofabrication CAD geometry interoperability layout GDS OASIS software paper","site:nist.gov NanoFab user guide project approval safety review","site:nnci.net nanofabrication facility GDS file submission design review safety authorization","site:stanford.edu nanofabrication facility GDSII electron beam file submission official","site:cornell.edu nanofabrication electron beam GDS design rules official","site:doc.cgal.org kernel representation exact predicates official geometry","site:geos.org geometry model precision robustness official documentation","site:hypothesis.readthedocs.io property based testing stateful official","property-based testing computational geometry paper metamorphic testing geometry","site:bls.gov software developers median pay 2025 occupational outlook handbook","site:bls.gov OEWS software developers annual mean wage May 2025","\"Geometric interoperability via queries\" PDF Hoffmann Shapiro Srinivasan","\"Geometric interoperability via queries\" DOI 10.1016/j.cad.2013.08.027"],"sources":[{"source_id":"S1","title":"PHIDL: Python-based layout and geometry creation for nanolithography","publisher":"National Institute of Standards and Technology","url":"https://www.nist.gov/publications/phidl-python-based-layout-and-geometry-creation-nanolithography","source_class":"PRIMARY_RESEARCH","publication_date":"2021-09-27","accessed_at":"2026-08-03","claims_supported":["CAD is critical to creating nanopatterned structures and devices.","Script-generated lithographic geometry is increasingly used.","Open-source GDSII CAD has documented usability gaps, and PHIDL is an existing nanolithography geometry tool."]},{"source_id":"S2","title":"Electron-beam lithography","publisher":"National Institute of Standards and Technology","url":"https://www.nist.gov/programs-projects/electron-beam-lithography","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2021-02-18; page updated before access","accessed_at":"2026-08-03","claims_supported":["Electron-beam lithography can achieve approximately 10 nm lateral resolution and 1 nm placement accuracy, making pattern semantics consequential.","Pattern accuracy depends on pattern definition, fracturing, alignment, processes, and lithography-system operation.","NIST created software specifically to improve control of pattern accuracy and reduce design barriers."]},{"source_id":"S3","title":"OpenAccess Coalition","publisher":"Silicon Integration Initiative","url":"https://si2.org/openaccess-coalition/","source_class":"OFFICIAL_ORGANIZATION_DATA","publication_date":"undated","accessed_at":"2026-08-03","claims_supported":["A governed, extensible API and reference implementation are established semiconductor-EDA practices.","OpenAccess changes are scrutinized by a coalition team and propagated into member tool suites for version compatibility and interoperability.","Foundries, device manufacturers, fabless companies, and EDA suppliers are identifiable stakeholders and potential authorizers of interface extensions."]},{"source_id":"S4","title":"The Geometry API","publisher":"KLayout","url":"https://www.klayout.de/0.24/doc/programming/geometry_api.html","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"undated; documentation for KLayout 0.24","accessed_at":"2026-08-03","claims_supported":["An existing layout-geometry API already provides regions, boolean operations, transforms, bounding boxes, and design-rule checks.","KLayout documents rounding from floating-point to integer coordinates and ambiguity for touching polygons.","Its Region is a collection of polygons and exposes polygon iteration, so it is not the proposed representation-opaque, multi-backend contract."]},{"source_id":"S5","title":"CGAL 6.2 Manual: Geometry Kernels","publisher":"The CGAL Project","url":"https://doc.cgal.org/latest/Manual/devman_kernels.html","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"undated; current CGAL 6.2 documentation","accessed_at":"2026-08-03","claims_supported":["Geometry-kernel substitution across different internal representations is established practice.","CGAL requires packages to state kernel requirements and supports algorithms working with both Cartesian and homogeneous representations.","Standardized operations already include bounding boxes, transforms, and inside/boundary/outside-style predicates."]},{"source_id":"S6","title":"Geometric Interoperability via Queries","publisher":"National Institute of Standards and Technology; article published in Computer-Aided Design","url":"https://www.nist.gov/publications/geometric-interoperability-queries","source_class":"PRIMARY_RESEARCH","publication_date":"2014-05-19","accessed_at":"2026-08-03","claims_supported":["Geometric model interoperability and interchangeability are documented CAD/manufacturing problems.","The paper identifies limitations of representation-translation approaches and proposes formally specified queries supported by different systems.","The associated paper defines tolerance-aware point-membership queries returning in, out, or on, creating a particularly close analogue to the proposal."]},{"source_id":"S7","title":"The Application Process: Instructions and Guidance","publisher":"National Institute of Standards and Technology","url":"https://www.nist.gov/cnst/application-process-instructions-and-guidance","source_class":"OFFICIAL_GUIDANCE","publication_date":"2013-03-21; updated 2024-06-17","accessed_at":"2026-08-03","claims_supported":["NIST NanoFab has a formal project-review process covering technical feasibility, merit, materials, processes, training, and safe execution.","A principal investigator must sign required project documentation, and facility review is a credible authorization path.","An offline software prototype can be separated from any later fabrication authorization."]},{"source_id":"S8","title":"Table 1. National employment and wage data from the Occupational Employment and Wage Statistics survey by occupation, May 2025","publisher":"U.S. Bureau of Labor Statistics","url":"https://www.bls.gov/news.release/ocwage.t01.htm","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2026-05-15","accessed_at":"2026-08-03","claims_supported":["May 2025 national mean wages were $148,100 annually for software developers and $111,490 for software QA analysts and testers.","These wages provide a public labor-cost anchor for 2026 resource-equivalent estimates, subject to loading and specialist-cost assumptions."]}],"problem_evidence":{"support":"MODERATE","rationale":"External evidence establishes that nanoscale pattern CAD is critical, pattern accuracy matters at nanometer-scale resolution, and geometric interoperability is a recognized CAD/manufacturing problem. KLayout also documents concrete rounding and topology ambiguities. No source directly measures how often nanopattern clients inspect polygon, voxel, or field internals or quantifies failures caused by backend replacement, so the candidate-specific prevalence and consequence magnitude remain unverified.","source_ids":["S1","S2","S4","S6"]},"stakeholder_evidence":{"support":"MODERATE","rationale":"NIST explicitly develops nanolithography design software to improve pattern accuracy, Si2 members govern an EDA API to maintain interoperability, and NIST NanoFab has a named project-review and authorization process. These identify credible adopters, funders, and authorizers, but none expresses demand for this exact NanoPatternRegion contract or commits resources to it.","source_ids":["S2","S3","S7"]},"prior_art":{"proximity":"SUBSTANTIAL_COLLISION","closest_analogues":[{"name":"Geometric interoperability via queries","similarity":"Very high conceptual overlap: representation-neutral, formally specified geometry queries; tolerance-aware point membership returning in, out, or on; applicability to CAD, manufacturing, metrology, and simulation.","remaining_difference":"The candidate adds material labels, immutability, overlap rules, nanoscale units, explicit versioning/leakage governance, and a shared property-based backend acceptance suite.","source_ids":["S6"]},{"name":"CGAL geometry-kernel concepts","similarity":"High overlap: algorithms are parameterized over interchangeable kernels with differing internal representations and standardized bounding-box, transform, and boundary-side operations.","remaining_difference":"CGAL does not itself define the proposed nanolithography material-region semantics, facility workflow, or one cross-vendor acceptance oracle.","source_ids":["S5"]},{"name":"KLayout Region and Geometry API","similarity":"High domain proximity: semiconductor-layout regions, transforms, boolean operations, bounds, ambiguity policies, rounding, and DRC are already implemented.","remaining_difference":"KLayout Region is polygon-based and exposes polygon iteration; it does not establish equivalence among polygon, voxel, and implicit-field backends under the proposed opaque contract.","source_ids":["S4"]},{"name":"Si2 OpenAccess","similarity":"Moderate-to-high workflow overlap: an industry-governed EDA API, scrutinized reference implementation, extensions, and version compatibility across vendor tool suites.","remaining_difference":"OpenAccess is a broad design database/API rather than a tolerance-defined material-membership abstraction with a black-box semantic conformance suite.","source_ids":["S3"]}],"distinctive_claim_remaining":"For a restricted nanolithography primitive set, a material-labeled immutable region contract with an explicit boundary band and one independently derived example/property/leakage oracle will make analytic and voxelized implementations agree on all held-out classifications and cross-operation laws outside the ambiguity band, while requiring fewer backend-specific exceptions than a format-only adapter or representation-specific Region API. Failure by any conforming backend on a held-out contract-relevant case, or the need for representation-specific clauses, falsifies the claim.","confidence":"HIGH"},"implementation_evidence":{"support":"STRONG","rationale":"Existing KLayout and CGAL APIs demonstrate the required geometry operations, representation-parameterized kernels, boundary predicates, transforms, and bounds. Query-based geometric interoperability supplies a formal tolerance-aware membership model, while OpenAccess demonstrates API stewardship and compatibility governance. The offline prototype is technically credible. Production feasibility remains conditional on domain validation of tolerance, materials, units, overlap semantics, numerical robustness, performance, and leakage channels; software conformance cannot authorize fabrication or establish physical safety.","source_ids":["S3","S4","S5","S6","S7"]},"scores":{"meaningful_impact":{"score":3,"rationale":"Pattern accuracy is important at nanometer-scale resolution, but the frequency and downstream severity of representation-caused failures are unmeasured.","source_ids":["S1","S2","S6"]},"stakeholder_pull":{"score":3,"rationale":"NIST and semiconductor-EDA stakeholders express adjacent needs for pattern accuracy and interoperability, but no exact adopter commitment was found.","source_ids":["S2","S3","S7"]},"incremental_advantage":{"score":2,"rationale":"The remaining advantage is narrow because tolerance-aware representation-neutral queries, interchangeable kernels, geometry APIs, and governed EDA interfaces already exist.","source_ids":["S3","S4","S5","S6"]},"distinctiveness_plausibility":{"score":2,"rationale":"The nanoscale material-label and shared-oracle combination may be distinctive, but its principal abstraction substantially collides with established prior art.","source_ids":["S4","S5","S6"]},"technical_implementability":{"score":4,"rationale":"All core operations have credible software analogues, and a two-backend offline harness is straightforward; numerical and semantic adequacy still require testing.","source_ids":["S4","S5","S6"]},"adoption_authority_feasibility":{"score":3,"rationale":"Formal EDA governance and NanoFab review paths exist, but the actual geometry-component owner and production release authority are not identified for a specific organization.","source_ids":["S3","S7"]},"evidence_readiness":{"score":3,"rationale":"Public prior art supports an immediate bounded prototype, but no real client inventory, incident corpus, proprietary backend, or validated fixture set is available.","source_ids":["S1","S4","S5","S6"]},"safety_net_benefit":{"score":3,"rationale":"A semantic acceptance oracle could catch silent geometry divergence, but an inadequate tolerance band or test suite could also provide false assurance.","source_ids":["S2","S5","S6","S7"]},"scalability":{"score":3,"rationale":"A common contract suite is reusable across backends, although each process, dimensionality, material system, and tolerance regime may require governed extensions.","source_ids":["S3","S5","S6"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Pre-register the restricted contract; implement analytic and voxel toy backends; build fixed, generated, differential, mutation, and leakage tests; obtain limited geometry and process-engineer review.","confidence":"MODERATE","assumptions":["Approximately 12-24 person-weeks split among a software engineer, QA/test engineer, and part-time nanofabrication or computational-geometry reviewer.","Uses synthetic or previously approved fixtures and open-source tooling; excludes equipment operation and proprietary integration.","Loaded labor is assumed to be roughly 1.5-2.0 times cash wages."],"source_ids":["S4","S5","S6","S8"]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Integrate the contract and oracle with two real design backends, build adapters and fixture governance, inventory clients, validate tolerance clauses, and establish version/change control.","confidence":"LOW","assumptions":["Approximately 2-4 loaded FTE-years across software, QA, geometry, process, and workflow owners.","Excludes fabrication-tool replacement, license purchases, and remediation of undiscovered legacy-client dependencies.","Specialized EDA labor may exceed national mean wage anchors."],"source_ids":["S3","S4","S7","S8"]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Validate against approved historical patterns, qualify release workflows, migrate selected clients, train maintainers, perform security and leakage review, and execute a reversible non-fabricating shadow comparison before any production decision.","confidence":"LOW","assumptions":["One organizational deployment with two backends and a bounded client population.","Existing fabrication approval paths remain unchanged.","No claim that passing software conformance eliminates physical or process qualification."],"source_ids":["S3","S7","S8"]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Contract stewardship, test maintenance, backend certification, compatibility review, incident triage, and periodic leakage and tolerance audits.","confidence":"LOW","assumptions":["Approximately 0.4-1.0 loaded FTE plus occasional domain review.","Backend count and contract-change rate remain modest.","Does not include routine nanofabrication or commercial EDA-license costs."],"source_ids":["S3","S7","S8"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"Nanoscale pattern accuracy and general geometric interoperability are externally documented, although candidate-specific prevalence is still unknown.","source_ids":["S1","S2","S4","S6"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"NIST is an identifiable nanolithography software developer and facility authorizer; Si2 provides an identifiable semiconductor-EDA API governance body. Neither has committed to this proposal.","source_ids":["S2","S3","S7"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"The remaining claim compares a material-labeled, tolerance-explicit, cross-backend conformance oracle against format-only or representation-specific baselines and has explicit failure conditions.","source_ids":["S4","S5","S6"]},"bounded_next_evidence_step":{"status":"YES","reason":"A restricted, offline two-backend experiment can be completed without fabrication or production integration and includes comparators and predeclared falsifiers.","source_ids":["S4","S5","S6","S7"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The first step is software-only and reversible. Any fabrication remains subject to the existing NanoFab technical, training, process, and safety review; conformance is not physical qualification.","source_ids":["S7"]},"credible_cost_scope_and_range":{"status":"YES","reason":"All four scopes state staffing and exclusion assumptions and are anchored to current national developer and QA wage data, although integration estimates remain low-confidence.","source_ids":["S8"]}},"next_evidence_step":"Run an 8-12 week offline experiment. Before observing outputs, freeze a versioned contract for rectangles, circles, empty regions, two material labels, affine transforms, union, slicing, typed errors, and a numeric boundary band. Implement independent analytic and voxel backends. Compare them with (a) the existing representation-specific/direct-structure baseline and (b) a format-only adapter baseline on at least 100 fixed fixtures, 10,000 generated operation sequences, held-out thin/near-touching/overlap/singular-transform cases, and seeded semantic mutants. Acceptance requires zero unexplained classification or cross-operation divergence outside the boundary band, no representation-specific contract clause, deterministic declared overlap behavior, and detection of every seeded contract-relevant mutant. Falsify or redesign if a backend passes the suite yet diverges on a held-out promised behavior, if useful semantics require backend-specific exceptions, or if a dependency audit finds neither representation coupling nor unexplained backend divergence. Do not connect outputs to fabrication equipment or alter production acceptance criteria.","blocking_evidence":["No measured prevalence of representation coupling or backend-change failures in actual nanopattern toolchains.","No named organization has committed to adopt, fund, or govern this exact contract.","No results from independently implemented analytic, polygonal, voxel, or implicit-field backends on held-out fixtures.","No process- or metrology-authorized validation that the proposed boundary band preserves physically consequential distinctions.","No client dependency inventory, proprietary-format constraints, performance benchmark, or production integration estimate.","No evidence that the combined oracle outperforms existing CGAL, KLayout, OpenAccess, or query-based interoperability practices."],"research_disposition":"KNOWN_PRACTICE_DIFFUSION","world_novelty_boundary":"This evaluation found substantial conceptual prior art but did not conduct an exhaustive literature, product, code, standards, or patent search. World novelty, patentability, freedom to operate, market size, and realized impact remain unmeasured. The only remaining assessed distinction is the proposed nanolithography-specific combination of material labels, explicit boundary semantics, opacity, and a shared conformance/leakage oracle.","arm":"COMPLETE_PROPOSAL_PORTFOLIO","candidate_version":0,"controller_recommendation":{"action":"STOP_EMPIRICAL_RESEARCH_NEEDED","repairable":false,"material_progress_observed":true,"progress_targets":["Obtain a real client dependency and backend-divergence inventory from one nanopattern toolchain.","Secure a named geometry steward, process/metrology reviewer, and production-release authority for the experiment.","Complete the preregistered two-backend trial with format-only and representation-specific comparators.","Demonstrate held-out semantic agreement outside the boundary band and mutation sensitivity without representation-specific clauses.","Validate tolerance, units, material overlap, and slice semantics against approved domain fixtures.","Replace low-confidence integration and recurring estimates with organization-specific staffing, licensing, and migration data."],"reason":"Web research materially establishes the problem class, implementability, authority boundary, and substantial prior-art collision. The remaining incremental claim cannot be resolved by further bounded web search: it requires dependency fieldwork, independently implemented backends, held-out live execution, and domain validation. Under the required decision rule this is an empirical-research stop, and all STOP recommendations are non-repairable."},"proposal_index":1}