{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp09_archetype_breadth150_20260804","research_id":"eoa_inverse_innovation_exp09_light_prior_art_20260804","cell_id":"buffering__computer_science","search_lanes":{"direct_problem_and_intervention":{"queries":["repository watcher event storm bounded queue backpressure diagnostics","incremental analysis daemon filesystem watcher overflow rescan stale version events"],"source_ids":["SRC1","SRC2","SRC3"],"no_result_note":null},"synonyms_and_historical_terms":{"queries":["site:facebook.github.io/watchman/docs triggers accumulated changes while command running","file event batching coalescing stale work cancellation concurrency language server analyzer","site:microsoft.github.io/language-server-protocol publishDiagnostics version older"],"source_ids":["SRC1","SRC3","SRC4"],"no_result_note":null},"products_practices_and_standards":{"queries":["Watchman trigger batching single process overflow","FileSystemWatcher InternalBufferSize many changes overflow","Git FSMonitor daemon queue overload dropped events resync","Language Server Protocol publishDiagnostics document version"],"source_ids":["SRC1","SRC2","SRC3","SRC4"],"no_result_note":null},"component_combination":{"queries":["bounded queue filesystem events overflow full rescan priority interactive edits analyzer","file event batching coalescing stale work cancellation concurrency language server analyzer"],"source_ids":["SRC1","SRC2","SRC3","SRC4"],"no_result_note":"The search found partial combinations—bounded watcher buffers, batching and serialized dispatch, token-based invalidation recovery, full-scan overflow handling, and version-tagged diagnostics—but no retained source documented the complete proposed policy in one analyzer dispatch path."}},"sources":[{"source_id":"SRC1","title":"Watchman trigger command","publisher":"Meta Open Source","url":"https://facebook.github.io/watchman/docs/cmd/trigger.html","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["Watchman settles and batches changed-file lists before invoking a trigger.","Only one instance of a given trigger runs at a time; changes arriving during execution are evaluated afterward, explicitly avoiding fork-bomb-style behavior.","A maximum file count can truncate trigger input while setting WATCHMAN_FILES_OVERFLOW=true, providing visible overflow rather than silent truncation."]},{"source_id":"SRC2","title":"FileSystemWatcher.InternalBufferSize Property","publisher":"Microsoft Learn","url":"https://learn.microsoft.com/en-us/dotnet/api/system.io.filesystemwatcher.internalbuffersize?view=netframework-4.8.1","source_type":"OFFICIAL_GUIDANCE","claims_supported":["FileSystemWatcher stores filesystem notifications in a byte-bounded internal buffer.","Many changes in a short time can overflow the buffer and cause loss of detailed change tracking.","Increasing the buffer consumes expensive non-paged memory, demonstrating the need to bound capacity and filter unwanted notifications."]},{"source_id":"SRC3","title":"Improve Git monorepo performance with a file system monitor","publisher":"GitHub","url":"https://github.blog/engineering/infrastructure/improve-git-monorepo-performance-with-a-file-system-monitor/","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["Git FSMonitor is a long-running repository daemon that places changed paths into an in-memory time-sorted queue and serves concurrent clients.","Under heavy load, the operating system or daemon can drop events because the daemon becomes overloaded or falls behind.","FSMonitor uses ordered tokens and synchronization identifiers; after an event-data gap it returns an assume-everything-changed response that forces a regular worktree scan."]},{"source_id":"SRC4","title":"Language Server Protocol 3.17: PublishDiagnostics Notification","publisher":"Microsoft Language Server Protocol","url":"https://raw.githubusercontent.com/microsoft/language-server-protocol/gh-pages/_specifications/lsp/3.17/language/publishDiagnostics.md","source_type":"OFFICIAL_STANDARD","claims_supported":["Published diagnostics represent validation-run results and must be recomputed when a file changes.","Newly published diagnostics replace prior diagnostics rather than being merged.","Diagnostic notifications can identify the document version for which the diagnostics were computed, and clients can advertise version support."]}],"problem_evidence":{"status":"PARTLY_SUPPORTED","finding":"The problem is publicly visible: official and first-party documentation describes short change bursts overflowing bounded watcher buffers, repository monitors becoming overloaded and falling behind, and serialized batching used to prevent process explosions. Version-tagged diagnostics also make stale-result handling visible. The retained sources do not directly measure the proposal's exact analyzer CPU, memory, and diagnostic-latency failure chain, so those severity details remain only partly supported.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"closest_prior_art":[{"name":"Watchman batched, single-instance triggers with explicit overflow indication","source_ids":["SRC1"],"overlap":"It delays until changes settle, batches changed files, prevents concurrent instances of the same trigger, accumulates intervening changes for later execution, caps reported files, and exposes overflow.","remaining_difference":"The documentation does not describe item-and-byte queue bounds between watcher and analyzer, current-content-version checks before dispatch, protected interactive admission, measured service-rate drainage, or analyzer queue-age telemetry."},{"name":"Git FSMonitor queued repository invalidations with token-based resynchronization","source_ids":["SRC3"],"overlap":"It is a repository-specific daemon that queues changed paths, uses ordered state tokens, detects event-history gaps after overload, and converts unsafe incremental state into an explicit full-scan response.","remaining_difference":"Its queue is not documented as a bounded analyzer surge queue; its tokens describe monitor synchronization rather than per-file content versions, and it does not reserve capacity for interactive edits or govern analyzer concurrency."},{"name":"Bounded FileSystemWatcher buffer plus version-tagged LSP diagnostics","source_ids":["SRC2","SRC4"],"overlap":"Together these establish bounded filesystem-notification storage, burst overflow behavior, memory-cost constraints, recomputation after file changes, replacement of prior diagnostics, and association of diagnostics with document versions.","remaining_difference":"They do not establish the proposed integrated admission, priority, staleness-expiration, capacity-governed dispatch, and overflow-to-rescan mechanism."}],"prior_art_disposition":"ADJACENT_PRIOR_ART","contrastive_claim_remaining":"For a transient repository event burst whose post-burst demand falls below analyzer capacity, adding protected interactive admission and pre-dispatch current-file-version validation to an explicitly item-and-byte-bounded queue drained at measured safe analyzer concurrency will reduce analyzer resource-limit breaches without losing required current-version invalidations or exceeding a predefined current-diagnostic tail-latency limit, compared with direct dispatch and ordinary batching or watcher buffering.","contrastive_claim_falsifier":"The claim is falsified if a representative bounded replay shows no reduction in resource-limit breaches, loses any required current-version invalidation, violates required ordering, fails to drain within the accepted window, or exceeds the predefined current-diagnostic tail-latency limit. Persistent demand at or above service capacity after the burst also falsifies buffering as the remedy.","gates":{"adequate_source_search":{"status":"PASS","rationale":"The bounded search covered direct wording, historical terms such as settling and coalescing, deployed watcher and repository-monitor practices, an official diagnostics protocol, and combinations of queue, overflow, rescan, staleness, priority, and concurrency components. Exactly four opened direct sources from three publishers were retained.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"supported_problem":{"status":"PASS","rationale":"The retained sources directly show burst overflow, overload and lag, explicit batching to prevent process proliferation, and version-associated diagnostic replacement. Although the exact analyzer failure chain is only partly supported, the underlying problem is clearly visible.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"distinct_testable_claim":{"status":"PASS","rationale":"Close mechanisms are established, but the retained art does not document the full combination of protected interactive capacity, per-file current-version validation, bounded item-and-byte admission, and analyzer-capacity-governed release. Its incremental effect has measurable resource, loss, ordering, drain-time, and latency outcomes.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"bounded_next_test":{"status":"PASS","rationale":"One offline trace replay against direct dispatch and fixed candidate configurations is bounded and reversible. Queue limits, protected share, version rule, analyzer concurrency, maximum age, overflow response, resource ceilings, loss criteria, drain window, and latency thresholds can all be fixed before execution.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"no_obvious_safety_or_authority_stop":{"status":"PASS","rationale":"The authorized test uses recorded traces, a simulator, and a non-production analyzer without modifying repository files or production dispatch. Existing products demonstrate visible overflow and full-scan recovery patterns; loss, ordering, overload, and latency can be enforced as halt conditions. No obvious external authority or safety stop was found.","source_ids":["SRC1","SRC3"]}},"screen_survival":true,"world_novelty_boundary":"This coarse public-web search found adjacent deployed practices and standards, not proof of a novel invention. It cannot establish world novelty, patentability, market size, expert acceptance, production feasibility, or realized value; unsearched patents, papers, source code, issue trackers, proprietary systems, and differently named designs may contain closer prior art."}