{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp09_archetype_breadth150_20260804","research_id":"eoa_inverse_innovation_exp09_light_prior_art_20260804","cell_id":"rate_limiting__computer_science","search_lanes":{"direct_problem_and_intervention":{"queries":["shared remote build service rate limit per user workspace compile jobs token bucket speculative compilation IDE","compiler service admission control concurrency limit retry-after compilation jobs"],"source_ids":["SRC1","SRC2","SRC3","SRC4"],"no_result_note":"No exact all-in-one implementation surfaced; the assessment relies on adjacent systems and component combinations, not on phrase absence."},"synonyms_and_historical_terms":{"queries":["continuous compilation superseded builds cancel obsolete compile requests IDE build server queue","remote build execution service priority CI interactive builds quota"],"source_ids":["SRC2","SRC3"],"no_result_note":null},"products_practices_and_standards":{"queries":["Cloud Build quotas concurrent builds queued quota","GitHub Actions concurrency cancel-in-progress pending job replaced","Buildfarm scheduler priority queued operations fairness quotas remote execution","Azure DevOps rate limits retry-after pipeline shared resources"],"source_ids":["SRC1","SRC2","SRC3","SRC4"],"no_result_note":null},"component_combination":{"queries":["remote execution scheduler quotas priority CI interactive builds fairness documentation","shared build queue max depth priority concurrency rate limit retry-after"],"source_ids":["SRC1","SRC2","SRC3","SRC4"],"no_result_note":null}},"sources":[{"source_id":"SRC1","title":"Rate and usage limits - Azure DevOps","publisher":"Microsoft","url":"https://learn.microsoft.com/en-us/azure/devops/integrate/concepts/rate-limits?view=azure-devops","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["Shared-resource consumption spikes can cause performance problems or outages in a multi-tenant developer service.","Azure DevOps applies sliding-window consumption limits to individual pipelines and can delay or block them.","The service exposes rate-limit state and Retry-After information to support observable, explicit excess handling."]},{"source_id":"SRC2","title":"Control the concurrency of workflows and jobs","publisher":"GitHub","url":"https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency?apiVersion=2022-11-28","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["CI jobs can be grouped under concurrency limits before simultaneous execution.","A newer queued run can replace an older pending run, and configured runs can cancel in-progress work.","Pending queues can be explicitly bounded, with excess runs canceled rather than accumulated indefinitely."]},{"source_id":"SRC3","title":"Configuration | Buildfarm","publisher":"Buildfarm","url":"https://buildfarm.github.io/buildfarm/docs/configuration/configuration/","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["A Remote Execution API implementation exposes maximum prequeue and ready-queue depths to control arrival flow.","Buildfarm supports priority queues driven by Bazel remote-execution priority.","Worker execution width and global execution limiting provide concurrency controls close to compiler-worker admission."]},{"source_id":"SRC4","title":"Quotas and limits | Cloud Build","publisher":"Google Cloud","url":"https://cloud.google.com/build/quotas","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["Cloud Build applies per-project quotas to running builds to protect against unforeseen usage spikes.","Cloud Build enforces limits on concurrent builds and CPUs.","When private-pool CPU quota is filled, additional requests are queued and processed serially, illustrating the backlog behavior that explicit excess handling must address."]}],"problem_evidence":{"status":"PARTLY_SUPPORTED","finding":"The general problem is visible: official product documentation reports that shared developer-service spikes can impair availability, build services impose concurrent-build limits, remote-execution systems bound queues and execution width, and CI systems replace superseded pending work. The retained sources do not directly document IDE-triggered speculative compilation bursts displacing release-validation compiles in one shared compiler service.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"closest_prior_art":[{"name":"Azure DevOps pipeline rate and usage limiting","source_ids":["SRC1"],"overlap":"Measures pipeline consumption in a sliding window, limits shared-resource use, delays or blocks excess activity, and exposes limit state plus Retry-After guidance.","remaining_difference":"It is a broad service-consumption limiter rather than a documented pre-worker token bucket for speculative compile admissions, and it does not describe a reserved release-validation allowance."},{"name":"GitHub Actions concurrency groups","source_ids":["SRC2"],"overlap":"Provides source-keyed concurrency control, bounded pending work, replacement of superseded runs, and optional cancellation of in-progress work.","remaining_difference":"It limits simultaneous runs rather than sustained temporal admission through a refillable token bucket and does not combine workspace fairness with protected release-validation capacity or jittered retry."},{"name":"Buildfarm remote-execution queue and worker controls","source_ids":["SRC3"],"overlap":"Directly concerns remote build execution and combines bounded arrival queues, priority scheduling, worker execution width, and a global execution limit.","remaining_difference":"The documentation does not show per-workspace token buckets with burst/refill rates, a protected release-validation reserve, or Retry-After responses with jitter."},{"name":"Google Cloud Build concurrent-build quotas","source_ids":["SRC4"],"overlap":"Limits concurrent build resource use at project scope to protect service fairness and availability during spikes.","remaining_difference":"It is a concurrency quota whose documented overflow can queue; it is not a speculative-versus-validation admission policy with bounded retries and workspace-level temporal envelopes."}],"prior_art_disposition":"ADJACENT_PRIOR_ART","contrastive_claim_remaining":"For a shared compiler service carrying replaceable IDE speculation and release validation, per-workspace sustained admission rate is an independently important control variable: adding a measured burst-and-refill envelope before workers, alongside an aggregate in-flight ceiling and a separately protected validation allowance, will preserve validation latency better than concurrency limits, priority queues, or superseded-run cancellation alone without creating hidden backlog.","contrastive_claim_falsifier":"The contrast disappears if an existing compiler or remote-build system is shown to implement, for speculative requests, the same combined pre-worker controls: per-workspace token-bucket burst/refill admission, aggregate concurrency ceiling, protected release-validation capacity, bounded Retry-After handling with jitter, and class/workspace enforcement telemetry. Empirically, it is also falsified if trace replay shows no incremental preservation of validation capacity over matched concurrency, priority, and supersession baselines.","gates":{"adequate_source_search":{"status":"PASS","rationale":"The bounded search covered direct wording, older or synonymous continuous-build and supersession terminology, named build and remote-execution products, and combinations of rate, concurrency, priority, bounded-queue, and retry components. Exactly four opened first-party sources from four publishers were retained.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"supported_problem":{"status":"PASS","rationale":"The exact IDE-to-validation displacement scenario is not directly documented, but official sources support the constituent shared-resource spike, build-capacity, queue-growth, and obsolete-work phenomena strongly enough for PARTLY_SUPPORTED problem evidence.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"distinct_testable_claim":{"status":"PASS","rationale":"The remaining claim is narrower than generic rate limiting: it predicts an incremental validation-latency benefit from workspace-level temporal admission combined with protected class capacity, compared with documented concurrency, priority, quota, and supersession controls. It has explicit prior-art and empirical falsifiers.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"bounded_next_test":{"status":"PASS","rationale":"Offline replay of a bounded, consenting service trace can compare the proposal against concurrency-only, priority-only, and supersession baselines while measuring validation latency, worker-envelope violations, ordinary-workspace allocation, legitimate burst preservation, and hypothetical delays. It requires no production enforcement.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"no_obvious_safety_or_authority_stop":{"status":"PASS","rationale":"The first test is read-only and reversible, and compiler-platform owners can evaluate hypothetical policy without delaying or rejecting production jobs. Workspace identifiers should be minimized or pseudonymized, request-class labels validated, and any later enforcement conditioned on CI-owner approval and rollback controls; no retained source reveals an inherent safety or authority prohibition.","source_ids":["SRC1","SRC2","SRC3","SRC4"]}},"screen_survival":true,"world_novelty_boundary":"This bounded public-web screen establishes only that the retained sources are adjacent rather than an exact documented match. It cannot establish world novelty, patentability, market size, expert acceptance, realized value, or absence of undiscovered proprietary, academic, historical, or patent prior art."}