{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp09_archetype_breadth150_20260804","research_id":"eoa_inverse_innovation_exp09_light_prior_art_20260804","cell_id":"graceful_degradation__computer_science","search_lanes":{"direct_problem_and_intervention":{"queries":["language server degraded mode resource pressure syntax diagnostics workspace indexing","language server syntax only mode memory indexing disabled","language server out of memory indexing crash open document diagnostics"],"source_ids":["SRC1","SRC2"],"no_result_note":"No retained source described the complete combination of automatic resource-pressure entry, protected core capacity, hysteretic recovery, and checkpoint-aware reindexing."},"synonyms_and_historical_terms":{"queries":["language server light mode open files only","partial IntelliSense mode syntax server large project","partial semantic language service local file fallback","workspace diagnostics throttling open file priority"],"source_ids":["SRC1","SRC2","SRC3"],"no_result_note":null},"products_practices_and_standards":{"queries":["Pylance languageServerMode light indexing openFilesOnly","VS Code TypeScript Partial IntelliSense mode","LuaLS diagnostics.workspaceRate open file","clangd background indexing skip"],"source_ids":["SRC1","SRC2","SRC3","SRC4"],"no_result_note":null},"component_combination":{"queries":["resource threshold language server cancel indexing preserve open file diagnostics","LSP dynamic capability registration degraded mode","language server hysteresis recovery reindex","tsserver partial semantic mode status restoration"],"source_ids":["SRC1","SRC2","SRC3","SRC4"],"no_result_note":"The component practices were visible separately and in partial combinations, but no retained source joined pressure-triggered admission control, explicit reservations, ranked feature sacrifice, truthful capability advertisement, and hysteretic recovery."}},"sources":[{"source_id":"SRC1","title":"Pylance: Settings and Customization","publisher":"Microsoft Pylance","url":"https://github.com/microsoft/pylance-release","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["Pylance supports an open-files-only diagnostic scope to reduce analysis in large workspaces.","Its light configuration disables indexing and other enrichments, trading auto-import and workspace-symbol coverage for lower resource use.","The documentation identifies type checking and indexing as resource-intensive and provides configuration for out-of-memory situations."]},{"source_id":"SRC2","title":"Working with JavaScript: Partial IntelliSense mode","publisher":"Microsoft Visual Studio Code","url":"https://code.visualstudio.com/docs/nodejs/working-with-javascript","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["VS Code has an explicit partial IntelliSense mode that concentrates service on open files when project-wide information is unavailable.","Partial mode reports syntax errors while disabling or narrowing semantic diagnostics, cross-file navigation, workspace symbols, auto-imports, rename, and refactorings.","The editor visibly reports partial mode in its language status item and returns to project-wide IntelliSense after project loading completes."]},{"source_id":"SRC3","title":"Lua Language Server Settings","publisher":"LuaLS","url":"https://luals.github.io/wiki/settings/","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["LuaLS allows workspace diagnostic processing to be throttled to reduce CPU usage.","The currently open file continues to be diagnosed at full rate regardless of the reduced workspace diagnostic rate, demonstrating explicit foreground prioritization."]},{"source_id":"SRC4","title":"clangd Configuration","publisher":"LLVM clangd","url":"https://clangd.llvm.org/config","source_type":"OFFICIAL_GUIDANCE","claims_supported":["clangd can skip slow background indexing while continuing to process active files.","clangd distinguishes information about the current file from project-index information such as incoming references.","Its configuration exposes separate controls for background indexing and optional analysis or presentation features."]}],"problem_evidence":{"status":"PARTLY_SUPPORTED","finding":"The resource-contention premise is visible: first-party documentation identifies whole-workspace indexing and type analysis as resource-intensive, offers open-file-only or light modes, and documents CPU throttling that preserves full-rate diagnosis of the active file. The retained sources do not directly establish the proposal's entire failure chain—sustained queue growth causing process stalls, restarts, and loss of synchronized open-document syntax feedback—so support is partial rather than complete.","source_ids":["SRC1","SRC3","SRC4"]},"closest_prior_art":[{"name":"VS Code TypeScript/JavaScript Partial IntelliSense mode","source_ids":["SRC2"],"overlap":"Provides an explicit visible partial-service state, preserves open-file and syntax-oriented behavior, disables or narrows repository-wide semantic features, supplies local-file navigation and completion behavior, and automatically returns to project-wide service after loading.","remaining_difference":"The documented trigger is project unavailability or loading rather than measured CPU, memory, or queue pressure; it does not document protected resource reservations, ranked cancellation, hysteretic thresholds, or checkpoint-governed clean reindexing."},{"name":"Pylance light mode and open-files-only analysis","source_ids":["SRC1"],"overlap":"Reduces indexing and enrichment, scopes diagnostics to open files, and explicitly trades richer workspace features for lower resource consumption.","remaining_difference":"The profile is principally configuration-driven, not a reversible runtime transition automatically entered under sustained pressure with advertised capability changes and staged recovery."},{"name":"LuaLS foreground diagnostic prioritization plus clangd background-index suppression","source_ids":["SRC3","SRC4"],"overlap":"Together demonstrate prioritizing the active file, throttling workspace work to reduce CPU, and disabling slow background indexing while accepting reduced repository-wide information.","remaining_difference":"They do not document a unified mode controller with measured entry and recovery thresholds, reserved core capacity, coherent client-visible capability profiles, bounded fallbacks, and consistency-aware restoration."}],"prior_art_disposition":"ADJACENT_PRIOR_ART","contrastive_claim_remaining":"Under the same bounded memory or CPU limit and synthetic indexing backlog, an automatic pressure-triggered controller that reserves capacity for document synchronization and syntax diagnostics, visibly withdraws a ranked set of repository capabilities, and uses hysteretic staged recovery will keep current-version open-document core operations within a preregistered quality floor and restore a consistent full index more reliably than an otherwise identical full-service baseline. The remaining distinction is the pressure-responsive, capacity-protected, integrity-checked transition policy—not partial or light language-service operation by itself.","contrastive_claim_falsifier":"Falsify the remaining claim if matched stress runs show no improvement in survival or core-operation quality versus baseline; if open-file parsing alone exceeds the reserved budget; if emitted diagnostics mismatch document versions; if the visible mode or advertised capabilities disagree with actual behavior; or if pressure removal cannot produce a consistent staged restoration or clean reindex.","gates":{"adequate_source_search":{"status":"PASS","rationale":"The bounded screen covered direct wording, older and synonymous modes, named product practices, and component combinations. Exactly four opened first-party or official sources from Microsoft, LuaLS, and LLVM were retained.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"supported_problem":{"status":"PASS","rationale":"The problem is partly supported by documented resource costs of workspace indexing and type analysis and by existing controls that reduce background work while prioritizing open files; the more specific stall-and-restart chain remains unverified.","source_ids":["SRC1","SRC3","SRC4"]},"distinct_testable_claim":{"status":"PASS","rationale":"Although explicit partial modes, feature disablement, local fallbacks, status signaling, and foreground prioritization already exist, the retained art does not show their integration with sustained resource thresholds, protected capacity, hysteresis, and consistency-aware reindex recovery. That remaining combination has observable transitions and falsifiers.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"bounded_next_test":{"status":"PASS","rationale":"The proposed ten-pair maximum replay on one disposable repository, with a fixed resource limit, synthetic indexing backlog, recorded capability state, version-consistency checks, survival measurements, cleanup checks, and predefined halt conditions, is bounded and directly discriminates the remaining claim.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"no_obvious_safety_or_authority_stop":{"status":"PASS","rationale":"The authorized step is test-only and non-production, uses a disposable repository and derived index, preserves authoritative and unsaved content, forbids weakening syntax or security controls, and halts on version inconsistency, state loss, misleading status, quality-floor failure, or failed recovery.","source_ids":[]}},"screen_survival":true,"world_novelty_boundary":"This bounded public-web screen found substantial adjacent practices but no opened source with the full pressure-triggered, capacity-reserved, hysteretic, integrity-checked combination. It does not establish world novelty, patentability, market size, expert acceptance, implementation feasibility across language servers, or realized value."}