{"closest_prior_art":[{"name":"OCLC WorldShare Collection Manager Activity History and title/collection histories","overlap":"Tracks knowledge-base collection activities, staff or institutional sources, provider data loads, automatic holdings feeds, collection selection or deletion, and title changes; users can inspect previous title data and processing reports.","remaining_difference":"The documentation describes histories inside Collection Manager, not a governed canonical log spanning licenses, discovery, authentication, outages, and tickets, and does not specify dual effective/record time, assertion status, correction lineage, or deterministic rebuilding of disposable composite projections.","source_ids":["SRC4"]},{"name":"Ohio State electronic-resource problem reporting in JIRA with a controlled vocabulary","overlap":"Retains complete ticket histories and classifies access, coverage/holdings, catalog, link-resolver, proxy, outage, subscription, and site-behavior problems for analysis and workflow improvement.","remaining_difference":"Tickets remain case narratives classified through staff interpretation. The practice does not make underlying cross-system changes canonical events or derive entitlement, discovery, authentication, and decision-time states through pinned replayable projectors.","source_ids":["SRC2"]},{"name":"NISO KBART and KBART Automation","overlap":"Standardizes timely transfer of accurate institution-specific holdings data from provider access-control systems to library knowledge bases, including regular automated updates that influence link resolvers and ERM systems.","remaining_difference":"KBART exchanges holdings snapshots or reports; it is not a cross-system event authority with bitemporal semantics, competing evidentiary assertions, linked corrections, projection frontiers, or rebuild-and-diff verification.","source_ids":["SRC3"]},{"name":"Formal tracking and assessment of electronic-resource troubleshooting data","overlap":"Documents tracking access reports in email, spreadsheets, ticket systems, and other tools, and analyzing them to identify failure points and improve troubleshooting.","remaining_difference":"The studied practice analyzes reported incidents rather than replaying canonical access-changing events into reproducible historical entitlement, discoverability, authentication, and composite-availability views.","source_ids":["SRC1"]}],"contrastive_claim_falsifier":"The contrastive claim is falsified if an existing authorized ERM, knowledge-base, audit-history, or ticketing workflow can, for every sampled case, deterministically regenerate entitlement, discovery visibility, authentication applicability, outage status, and composite availability at both effective-time and record-time frontiers from declared immutable inputs, while preserving provenance, unresolved assertions, and correction lineage without manual inference from mutable records.","contrastive_claim_remaining":"Within the retained sources, no close match was found for making cross-system electronic-resource access-changing assertions the governed canonical history and treating entitlement, discovery, authentication, composite availability, and decision-time records as disposable, versioned projections with explicit processing frontiers, evidentiary status, and correction lineage. This bounded structural distinction remains testable, not established as novel or beneficial.","experiment_id":"eoa_inverse_innovation_exp13_second_slot_policy60_20260806","gates":{"adequate_source_search":{"rationale":"PASS: The search covered the proposal directly, ERM and troubleshooting terminology, standards and first-party products, and combinations involving holdings, discovery, authentication, audit history, bitemporality, and event sourcing. Four retained sources were opened; they represent three publishers and include two primary studies, an official recommended practice, and first-party product documentation. Exact event-sourcing searches produced no close domain implementation, but that phrase miss is not treated as novelty evidence.","source_ids":["SRC1","SRC2","SRC3","SRC4"],"status":"PASS"},"bounded_next_test":{"rationale":"PASS: Encoding 20 closed cases from two platforms and six months, freezing the schema and evidence policy, and having two independent operators replay them is bounded and capable of testing determinism, component-state separation, declared-input sufficiency, identity resolution, and projection agreement with preserved evidence. Ticket-based studies show that closed access cases and classifications are practical study material, while also warning that interpretation can be subjective.","source_ids":["SRC1","SRC2"],"status":"PASS"},"distinct_testable_claim":{"rationale":"PASS: The retained standards, product histories, and ticket practices cover important components, but none documents the complete combination of a canonical cross-system event history, dual time, evidence status, linked corrections, pinned projectors, and rebuild-and-diff checks. The remaining distinction can be tested on identical cases against existing records and histories.","source_ids":["SRC1","SRC2","SRC3","SRC4"],"status":"PASS"},"no_obvious_safety_or_authority_stop":{"rationale":"PASS: The authorized first step is read-only, limited to closed cases and experimental projections, and excludes production mutation, patron-behavior inference, and disclosure beyond existing access groups. Contractual, authentication, identity-resolution, and retention risks are material but have named authorities and explicit halt/deletion conditions; no obvious stop prevents the bounded shadow test.","source_ids":[],"status":"PASS"},"supported_problem":{"rationale":"PASS: Primary studies document intertwined discovery, link-resolver, knowledge-base, holdings, proxy, subscription, and outage problems; fragmented tracking in email and tickets; fields that differ or change over time; ambiguous initial classifications; and difficulty attributing failures. This supports the practical problem, although the sources do not directly establish the full bitemporal-reconstruction failure asserted by the proposal.","source_ids":["SRC1","SRC2"],"status":"PASS"}},"prior_art_disposition":"ADJACENT_PRIOR_ART","problem_evidence":{"finding":"The problem is visible but only partly supported at its strongest level. Lowry documents intertwined access systems, disparate or changing fields, heavy reliance on email, limited formal analysis, unclear ticket resolutions, and contentious fault attribution. Foster documents fluctuating access caused by platform, subscription, network, holdings, proxy, and outage conditions; complete ticket histories still required manual, sometimes subjective interpretation, and an initial generic access label was about as likely to be wrong as correct. NISO and OCLC show that standardized holdings updates and detailed knowledge-base histories already address parts of the problem. None of the retained sources directly demonstrates that sampled libraries cannot reconstruct every historical effective-time and record-time composite access state.","source_ids":["SRC1","SRC2","SRC3","SRC4"],"status":"PARTLY_SUPPORTED"},"research_id":"eoa_inverse_innovation_exp13_light_screen_20260806","schema_version":1,"screen_id":"E13P093","screen_survival":true,"search_lanes":{"component_combination":{"no_result_note":null,"queries":["library ERM bitemporal event sourcing electronic resource access ledger replay","\"event sourcing\" library \"electronic resources\" OR ERM holdings","library electronic resource access \"audit trail\" entitlement discovery authentication","electronic resource access troubleshooting tickets study libraries ERM multiple systems historical records"],"source_ids":["SRC1","SRC2","SRC4"]},"direct_problem_and_intervention":{"no_result_note":null,"queries":["library electronic resource access troubleshooting historical entitlement discovery proxy audit trail","library ERM bitemporal event sourcing electronic resource access ledger replay","electronic resource access troubleshooting tickets study libraries ERM multiple systems historical records"],"source_ids":["SRC1","SRC2"]},"products_practices_and_standards":{"no_result_note":null,"queries":["NISO KBART recommended practice holdings coverage title transfer access entitlements","site:help.oclc.org WorldShare knowledge base activity history title changes holdings","site:knowledge.exlibrisgroup.com Alma electronic resource portfolio history audit activation coverage","site:docs.folio.org agreements e-resources entitlements history audit log coverage"],"source_ids":["SRC3","SRC4"]},"synonyms_and_historical_terms":{"no_result_note":null,"queries":["electronic resource management lifecycle license coverage activation title transfer terminology library","site:old.diglib.org ERMI electronic resource management workflow history access troubleshooting license holdings","\"access problem\" \"electronic resources\" library ticket workflow history","electronic resource access troubleshooting tickets study libraries ERM multiple systems historical records"],"source_ids":["SRC1","SRC2","SRC3"]}},"sources":[{"claims_supported":["Electronic-resource access troubleshooting involves intertwined discovery services, link resolvers, and knowledge bases.","Tracking is often fragmented across email and other tools, and disparate or changing fields are difficult to correlate.","Only 51 percent of 143 respondents tracked e-access problems, and only 10 percent reported a prior formal analysis.","Tickets may not clearly reveal the problem or resolution, and attributing outages can be contentious."],"publisher":"American Library Association, Core / Library Resources & Technical Services","source_id":"SRC1","source_type":"PRIMARY_RESEARCH","title":"Fighting an Uphill Battle: Troubleshooting Assessment Practices in Academic Libraries","url":"https://journals.ala.org/index.php/lrts/article/view/7511/10379"},{"claims_supported":["Electronic-resource availability can change because of subscriptions, platforms, campus networks, authentication, holdings, links, and outages.","Ohio State used JIRA to retain and analyze electronic-resource problem reports, including a full history of 1,771 tickets.","A controlled vocabulary covered access, coverage/holdings, catalog records, subscriptions, links, proxy problems, and outages.","Manual classification remained subjective, and the generic access label was approximately as likely to be assigned incorrectly as correctly."],"publisher":"American Library Association, Core / Library Resources & Technical Services","source_id":"SRC2","source_type":"PRIMARY_RESEARCH","title":"A Controlled Vocabulary for an Electronic Resources Problem Reporting System: Creation, Implementation and Assessment","url":"https://journals.ala.org/index.php/lrts/article/view/7382/10375"},{"claims_supported":["KBART is a NISO Recommended Practice for transferring holdings metadata among content providers, knowledge-base suppliers, and libraries.","Knowledge bases support link resolvers and electronic-resource management systems.","KBART Automation supports timely, accurate, institution-specific holdings reports and regular automated updating through APIs."],"publisher":"National Information Standards Organization","source_id":"SRC3","source_type":"OFFICIAL_STANDARD","title":"Knowledge Bases and Related Tools (KBART)","url":"https://www.niso.org/standards-committees/kbart"},{"claims_supported":["WorldShare Collection Manager records activity, collection, and title histories for knowledge-base collections.","Title History exposes changed and previous title data and distinguishes local from global edits.","Activity History records provider loads, automatic holdings feeds, KBART uploads, dates, sources, and processing results.","The feature is a strong system-specific history rival but is documented within the Collection Manager knowledge-base scope."],"publisher":"OCLC","source_id":"SRC4","source_type":"FIRST_PARTY_PRODUCT","title":"Use the Activity History","url":"https://help.oclc.org/Metadata_Services/WorldShare_Collection_Manager/Collection_Manager_Activity_History/Use_the_Activity_History"}],"world_novelty_boundary":"This coarse public-web screen found adjacent standards, product histories, and ticket-based practices but no retained source documenting the complete proposed combination. The bounded search cannot establish world novelty, patentability, market size, expert acceptance, implementation feasibility beyond the proposed pilot, or realized operational value."}