{"schema_version":1,"research_id":"eoa_inverse_innovation_exp06_external_evaluation_20260803","source_assessment_id":"representation_independent_interface_contract__chemistry_materials:P4:v0","cell_id":"representation_independent_interface_contract__chemistry_materials","search_queries":["materials science sample provenance tracking lineage laboratory samples FAIR data problem","NIST materials data provenance sample tracking laboratory","GS1 EPCIS 2.0 standard transformation event quantity traceability official","laboratory inventory sample lineage split pool aliquot LIMS official documentation","\"Lifetime Sample Tracking\" LiST materials science sample splits lineage platform paper","site:materialscommons.org sample tracking provenance experiment official","materials science laboratory sample tracking provenance platform sample lineage primary research","laboratory sample management split aliquot lineage official product documentation Benchling LabWare","W3C PROV-DM provenance data model entities activities agents official recommendation","materials provenance event sourced architecture ESAMP samples lineage event sourcing 2023","sample lineage quantity mass balance LIMS split combine idempotent atomic material inventory","laboratory sample chain custody audit trail ISO 17025 official sample handling records","site:w3.org/TR/prov-dm/ W3C Recommendation 30 April 2013 PROV-DM","site:ref.gs1.org/standards/epcis/2.0.0 EPCIS 2.0 transformation event quantity list official","site:fda.gov \"Sample Handling\" \"Chain of Custody\" laboratory manual","site:pubs.rsc.org d3dd00054k ESAMP event sourced materials provenance samples collections lineage"],"sources":[{"source_id":"S1","title":"NCAL: Data Management","publisher":"National Institute of Standards and Technology","url":"https://www.nist.gov/programs-projects/ncal-data-management","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2025-11-25","accessed_at":"2026-08-03","claims_supported":["NIST states that mechanical-testing and materials-science communities lack a widely accepted test-data-management solution.","NIST operates a system tracking provenance from delivered material through publication, with more than 10,000 records and nearly 20 TB of files.","NIST is an identifiable adopter and potential authorizer with a generic laboratory workflow and willingness to share schemas and lessons."]},{"source_id":"S2","title":"Lifetime Sample Tracking (LiST): A Data Platform for Materials Science","publisher":"arXiv / 2D Crystal Consortium authors","url":"https://arxiv.org/abs/2606.17469","source_class":"PRIMARY_RESEARCH","publication_date":"2026-06-16","accessed_at":"2026-08-03","claims_supported":["An NSF-supported materials facility developed LiST because it needed to organize and share data with users.","LiST automates capture, curation, analysis, and dissemination and holds synthesis and property data for approximately 20,000 samples.","LiST is reportedly used by groups outside the originating facility, showing adopter pull for materials sample-data infrastructure."]},{"source_id":"S3","title":"Tracking materials science data lineage to manage millions of materials experiments and analyses","publisher":"npj Computational Materials / Springer Nature","url":"https://www.nature.com/articles/s41524-019-0216-x","source_class":"PRIMARY_RESEARCH","publication_date":"2019-07-26","accessed_at":"2026-08-03","claims_supported":["The authors identify challenges in managing and linking data across disparate materials synthesis and characterization experiments.","MEAD maintained lineage through defined data-flow rules and identifiers and had managed millions of experiments and analyses.","The implementation demonstrates that experimental-material provenance systems can operate at large scale, while also showing substantial established prior practice."]},{"source_id":"S4","title":"ESAMP: event-sourced architecture for materials provenance management and application to accelerated materials discovery","publisher":"Royal Society of Chemistry, Digital Discovery","url":"https://pubs.rsc.org/en/content/articlehtml/2023/dd/d3dd00054k","source_class":"PRIMARY_RESEARCH","publication_date":"2023-06-21","accessed_at":"2026-08-03","claims_supported":["ESAMP is a generalizable event-sourced architecture that records sequences and interrelationships of experimental or simulation events and material-state evolution.","It explicitly models samples, processes, sample creation and consumption, split and combination lineages, parents and ancestors.","It was demonstrated by ingesting MEAD-scale materials data, creating a substantial collision with the proposed event-and-lineage model.","The paper acknowledges that complete physical ground truth is infeasible because unrecorded processes may alter a material."]},{"source_id":"S5","title":"PROV-DM: The PROV Data Model","publisher":"World Wide Web Consortium","url":"https://www.w3.org/TR/prov-dm/","source_class":"STANDARD","publication_date":"2013-04-30","accessed_at":"2026-08-03","claims_supported":["W3C PROV-DM is a technology-independent, domain-agnostic provenance model intended to translate and interchange provenance among heterogeneous systems.","It models entities, activities, agents, derivations, usage, generation, responsibility, and collections.","Its generic model does not itself specify material quantity conservation, atomic ledger operations, idempotency, correction semantics, or a multi-implementation conformance oracle."]},{"source_id":"S6","title":"EPCIS Standard, Release 2.0","publisher":"GS1","url":"https://ref.gs1.org/standards/epcis/2.0.0/","source_class":"STANDARD","publication_date":"2022-06","accessed_at":"2026-08-03","claims_supported":["EPCIS standardizes historical visibility events and interfaces independently of barcode, RFID, or other data carriers.","Transformation events support input and output identifiers and quantity lists; source and destination fields represent transfers of ownership, responsibility, or custody.","EPCIS is mature adjacent prior art for representation-independent lot transformations and traceability, although application-specific business rules remain outside the standard."]},{"source_id":"S7","title":"Create and track samples with the Inventory","publisher":"Benchling","url":"https://help.benchling.com/hc/en-us/articles/39943809066637-Create-and-track-samples-with-the-Inventory","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2026-01-13","accessed_at":"2026-08-03","claims_supported":["A current commercial system tracks sample location, quantity, status, transfers, usage, and history.","Benchling supports immutable notebook snapshots, transfer quantities, quantity additions or deductions, audit reports, permissions, APIs, and barcode changes.","The documentation also exposes representation/workflow-specific behavior, such as directly editing quantities and audit-logging only a plate barcode rather than automatically changed well barcodes."]},{"source_id":"S8","title":"ORA Laboratory Manual Volume III, Section 2: Chain of Custody—Sample Handling","publisher":"U.S. Food and Drug Administration","url":"https://www.fda.gov/media/74006/download?attachment=","source_class":"OFFICIAL_GUIDANCE","publication_date":"2019-06-06","accessed_at":"2026-08-03","claims_supported":["FDA laboratory procedure assigns operational responsibilities to analysts, sample custodians, supervisors, and laboratory management.","It requires documentation and reconciliation of sample discrepancies, specifies splitting and transferring samples, and requires remaining quantity to be compatible with received and used amounts or discrepancies to be explained.","It confirms that production chain-of-custody records can have regulatory or litigation significance and that controlled-material disposition requires separate authority."]}],"problem_evidence":{"support":"MODERATE","rationale":"The need for materials provenance and sample-data management is visible in NIST, LiST, MEAD, and ESAMP, including systems spanning tens of thousands to millions of records. FDA procedure confirms that splits, transfers, custody, remaining quantities, and discrepancy reconciliation matter in consequential laboratories. However, the exact proposed failure prevalence—schema replacement changing balances, clients bypassing invariants, duplicate allocation, and partial multi-lot commits—was not quantified by the eight sources. The supplied spreadsheet baseline therefore remains plausible but unverified.","source_ids":["S1","S2","S3","S4","S8"]},"stakeholder_evidence":{"support":"STRONG","rationale":"NIST is an identifiable materials-laboratory adopter operating an ongoing provenance system, and the NSF-supported 2DCC facility explicitly developed LiST in response to an organizational and user-sharing need. FDA guidance identifies custodians, laboratory supervision, and management as real authorizers for consequential sample workflows. None of these parties has expressed demand for this exact representation-independent contract or agreed to fund a pilot.","source_ids":["S1","S2","S8"]},"prior_art":{"proximity":"SUBSTANTIAL_COLLISION","closest_analogues":[{"name":"ESAMP","similarity":"Direct materials-domain event architecture modeling sample histories, state changes, creation, consumption, splits, combinations, parents, and ancestors at demonstrated scale.","remaining_difference":"The paper standardizes an event-sourced database architecture rather than demonstrating one storage-neutral command contract with atomic quantity laws, idempotency, immutable corrections, typed failures, and a shared oracle across snapshot, graph, and event-log implementations.","source_ids":["S4"]},{"name":"GS1 EPCIS 2.0","similarity":"Representation-independent visibility-event standard with transformations, input/output quantities, identifiers, custody-related sources and destinations, capture/query interfaces, and historical events.","remaining_difference":"EPCIS leaves application business logic to implementers and does not establish the proposed laboratory-specific mass-balance, uncertainty, closure, correction, idempotency, or transaction-atomicity rules.","source_ids":["S6"]},{"name":"W3C PROV-DM","similarity":"Technology-independent abstract provenance model supporting heterogeneous representations, entities, activities, agents, derivation, generation, usage, and validation constraints.","remaining_difference":"It is deliberately domain-agnostic and does not prescribe accountable material quantities or executable ledger commands and acceptance tests.","source_ids":["S5"]},{"name":"Benchling Inventory","similarity":"Deployed product practice for sample quantities, usage, transfers, immutable snapshots, histories, permissions, barcodes, and API access.","remaining_difference":"The reviewed documentation does not claim implementation substitutability under a common behavioral oracle and permits workflow-specific direct quantity and metadata edits.","source_ids":["S7"]},{"name":"LiST and MEAD lineage platforms","similarity":"Operational materials-science systems organizing sample, synthesis, characterization, analysis, and lineage data at meaningful scale.","remaining_difference":"The reviewed publications establish provenance infrastructure and scale, not the proposed cross-representation quantity-accounting contract or mutation-tested conformance rule.","source_ids":["S2","S3"]}],"distinctive_claim_remaining":"Relative to ESAMP, EPCIS, PROV-DM, and current inventory products, a storage-neutral MaterialLineageLedger contract can make independently structured relational-snapshot and event-log implementations observably equivalent for balances, ancestry, append-only corrections, idempotent duplicate operations, atomic multi-lot failures, typed errors, units, and declared uncertainty. This is falsified if the preregistered contract requires representation-specific fields, either implementation diverges on any promised observation, or deliberately mutated implementations that over-allocate, partially commit, erase history, or double-apply an operation still pass the oracle.","confidence":"HIGH"},"implementation_evidence":{"support":"MODERATE","rationale":"W3C PROV-DM and EPCIS demonstrate technology-independent provenance and event interfaces; ESAMP, MEAD, LiST, and Benchling demonstrate implementable provenance, lineage, inventory, and quantity workflows. These make a synthetic two-implementation prototype technically credible. Feasibility remains unproved for concurrent allocation, uncertainty propagation, legacy mapping, complete leakage detection, and equivalence across genuinely independent implementations. Workflow and authority are manageable only if the first step stays synthetic or read-only. FDA evidence warns that production custody, controlled-material disposition, regulatory records, and physical actions require laboratory-specific authorization. The ledger cannot establish physical mass, homogeneity, identity, or unrecorded events.","source_ids":["S2","S3","S4","S5","S6","S7","S8"]},"scores":{"meaningful_impact":{"score":4,"rationale":"Reliable sample ancestry and accounting can affect reproducibility, auditability, data reuse, and avoidance of wrong-sample associations; multiple large materials programs invest in provenance infrastructure. The magnitude of errors prevented by this particular contract is unmeasured.","source_ids":["S1","S2","S3","S4","S8"]},"stakeholder_pull":{"score":4,"rationale":"NIST and 2DCC provide explicit institutional need and actual adoption, while FDA assigns responsibility for comparable workflows. Pull for this exact interface contract is not established.","source_ids":["S1","S2","S8"]},"incremental_advantage":{"score":3,"rationale":"Atomic balance laws, idempotency, append-only correction, uncertainty semantics, and one oracle across storage representations could improve on provenance schemas or products, but no comparative result exists.","source_ids":["S4","S5","S6","S7"]},"distinctiveness_plausibility":{"score":2,"rationale":"ESAMP already covers materials events, state, split/combine lineage, creation, and consumption; EPCIS and PROV-DM already provide representation-independent event/provenance abstractions. Only the combined executable ledger laws and substitutability oracle remain plausibly distinctive.","source_ids":["S4","S5","S6"]},"technical_implementability":{"score":4,"rationale":"Standards and deployed systems establish the component technologies and scale. The proposed prototype is conventional software engineering, although concurrency and uncertainty rules may expose specification defects.","source_ids":["S2","S3","S4","S5","S6","S7"]},"adoption_authority_feasibility":{"score":4,"rationale":"A materials-data owner can plausibly authorize a synthetic or read-only exercise. Production changes require the sample custodian, laboratory management, IT/security, quality, and possibly regulatory owners.","source_ids":["S1","S2","S8"]},"evidence_readiness":{"score":3,"rationale":"The candidate defines concrete operations, comparators, mutants, and falsifiers, and adjacent systems supply model precedents. No fixture corpus, independent implementation, prospective adopter commitment, or measured baseline is available.","source_ids":["S4","S5","S6","S7"]},"safety_net_benefit":{"score":3,"rationale":"Atomic validation, immutable corrections, and rollback-friendly sandboxing could prevent or expose digital inconsistencies. They cannot detect mislabeled material, inaccurate weighing, contamination, evaporation, or missing physical events and may create false confidence.","source_ids":["S4","S8"]},"scalability":{"score":4,"rationale":"LiST, MEAD, and ESAMP demonstrate materials provenance at approximately 20,000 samples through millions of experiments and states. Performance of the proposed cross-implementation oracle and transactional quantity rules remains untested.","source_ids":["S2","S3","S4"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Preregister the abstract model; implement an in-memory reference plus independent event-log and relational-snapshot prototypes; create fixed, generated, concurrent, fault-injection, and mutation tests; produce a divergence report.","confidence":"MODERATE","assumptions":["Two software engineers for 8–12 weeks at fully loaded 2026 resource-equivalent rates.","Part-time materials-data steward and test/quality reviewer.","Synthetic fixtures only; no production integration, procurement, or regulated validation.","Open-source database and property-testing infrastructure."],"source_ids":["S4","S5","S6"]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"One-laboratory read-only integration, legacy mapping, access-control design, reconciliation tooling, client inventory, security review, and migration rehearsal.","confidence":"LOW","assumptions":["One laboratory and two incumbent data sources.","No physical relabeling or authoritative balance writeback.","Legacy records are sufficiently complete to map without inventing facts.","Includes engineering, data stewardship, security, and laboratory staff time but not enterprise software license premiums."],"source_ids":["S1","S2","S7","S8"]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Validated production service for one laboratory, including authoritative migration, integrations, monitoring, training, standard operating procedures, reconciliation, rollback, and staged cutover.","confidence":"LOW","assumptions":["Single institution with moderate integration complexity.","Excludes physical inventory recount, hazardous-material remediation, and broad regulated-computer-system validation.","Existing identity, backup, and hosting services are reusable.","A laboratory manager and custodian approve production use."],"source_ids":["S7","S8"]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Hosting, monitoring, backups, incident response, contract/version stewardship, conformance regression, user support, and periodic reconciliation for one laboratory.","confidence":"LOW","assumptions":["One production instance and a small support rotation.","No major schema migration or institution-wide rollout during the year.","Resource-equivalent estimate rather than a vendor quote.","Physical inventory operations remain an existing laboratory responsibility."],"source_ids":["S1","S2","S7"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"Multiple independent materials organizations report provenance and heterogeneous experimental-data-management needs and operate systems addressing them, although the candidate's exact failure prevalence remains unknown.","source_ids":["S1","S2","S3","S4"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"NIST and 2DCC are identifiable adopters of materials provenance systems; FDA procedure identifies laboratory management and sample custodians as credible authorizers for consequential sample workflows.","source_ids":["S1","S2","S8"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"The remaining claim specifies observable equivalence across independent representations and names precise violations that must be rejected, distinguishing it from a mere provenance schema.","source_ids":["S4","S5","S6","S7"]},"bounded_next_evidence_step":{"status":"YES","reason":"A synthetic, three-implementation, seeded replay and mutation-testing exercise is finite, reversible, comparator-based, and has preregistrable falsifiers.","source_ids":["S4","S5","S6"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The bounded step makes no production or physical changes. Production custody, labels, controlled materials, disposal, and regulatory records remain explicitly outside scope and under laboratory authority.","source_ids":["S8"]},"credible_cost_scope_and_range":{"status":"UNCERTAIN","reason":"The four bands are scoped resource-equivalent engineering estimates, but no direct pricing, labor quote, legacy-data assessment, or regulated-validation estimate was obtained from the eight sources.","source_ids":["S1","S2","S7","S8"]}},"next_evidence_step":"With a materials-data steward, preregister version-0 event, quantity, unit, uncertainty, correction, idempotency, concurrency, and typed-error semantics. Build a simple in-memory reference, an immutable event-log implementation, and an independently designed relational-snapshot implementation using only synthetic or copied non-authoritative fixtures. Comparator set: the reference model, pairwise black-box comparison of the two candidate implementations, an ESAMP/EPCIS-informed event mapping, and the incumbent direct-edit snapshot baseline. Replay 25 fixed histories and 500 seeded generated sequences covering nested splits, multi-parent combinations, custody transfer, consumption, explicit loss, closure, duplicate requests, corrections, unit mismatches, insufficient quantity, causal-cycle attempts, concurrent allocation, and simulated partial writes. Add at least four mutants: negative availability, duplicate application, partial multi-lot commit, and correction history erasure. Falsify the claim if any valid history needs storage-specific public fields or invented physical facts, conforming implementations disagree on a promised observation, either candidate cannot map to the abstract state, or any mutant survives. Halt on any production write path or ambiguous fixture; retain the original fixtures and divergence log.","blocking_evidence":["No source quantified how often materials laboratories directly edit storage internals or suffer balance or ancestry changes during schema replacement.","No adopter has requested, funded, or committed to test this exact behavioral contract.","No evidence yet shows that the proposed uncertainty and process-loss rules are complete across materials workflows.","No independent prototypes or mutation results demonstrate that the conformance oracle is executable and discriminating.","No concurrency, performance, or large-history replay measurements exist for the proposed invariants.","Legacy-data mappability without inferred ancestry or invented quantities is unknown.","Legal, electronic-signature, records-retention, export-control, controlled-material, and hazardous-material requirements are institution- and jurisdiction-specific and were not comprehensively assessed.","Cost bands lack direct labor estimates, vendor quotes, integration inventories, and regulated-validation scope.","Realized impact, market size, world novelty, patentability, freedom to operate, and physical-inventory accuracy remain unmeasured."],"research_disposition":"PARTNERED_RESEARCH_PROGRAM","world_novelty_boundary":"The search establishes substantial collision with ESAMP's materials event/state/lineage architecture, EPCIS transformation and quantity events, W3C's representation-independent provenance model, and existing inventory products. It did not locate a direct demonstration of one material-lot behavioral contract enforcing atomic quantity accounting, uncertainty, idempotency, append-only corrections, typed failures, and black-box substitutability across independent snapshot, graph, and event-log implementations. Absence from this bounded eight-source search is not evidence of world novelty. Patentability, freedom to operate, market size, and realized impact were not assessed.","arm":"COMPLETE_PROPOSAL_PORTFOLIO","candidate_version":0,"controller_recommendation":{"action":"STOP_EMPIRICAL_RESEARCH_NEEDED","repairable":false,"material_progress_observed":false,"progress_targets":["Secure a materials-data steward and laboratory-system owner for a synthetic, non-authoritative evaluation.","Publish the version-0 abstract state, operation laws, uncertainty rules, correction semantics, and representation-leakage allowlist before implementation.","Demonstrate pairwise observational equivalence of independently designed snapshot and event-log implementations against an in-memory reference.","Show that every preregistered mutant is rejected and report mutation score, minimal counterexamples, and uncovered laws.","Measure concurrent-allocation behavior, replay performance, and oracle runtime on histories representative of the intended laboratory.","Compare the contract clause-by-clause with ESAMP, EPCIS, PROV-DM, and the incumbent inventory product to isolate genuinely incremental obligations.","Obtain a legacy-fixture mappability assessment, authority matrix, production safety review, and scoped 2026 resource quote before any deployment decision."],"reason":"Bounded web research verifies the problem class, adopters, feasibility precedents, and substantial prior art, but the remaining advantage is an empirical software claim: independent representations must actually conform while known-bad mutants fail. Resolving it requires implementation, proprietary or representative fixtures, concurrency tests, and steward judgment rather than more bounded web search."},"proposal_index":4}