{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp09_archetype_breadth150_20260804","research_id":"eoa_inverse_innovation_exp09_light_prior_art_20260804","cell_id":"backpressure__accounting_auditing","search_lanes":{"direct_problem_and_intervention":{"queries":["audit PBC request list backlog duplicate requests client burden evidence requests","audit client evidence requests PBC delays duplicate requests study"],"source_ids":["SRC1","SRC3"],"no_result_note":null},"synonyms_and_historical_terms":{"queries":["provided by client audit bottleneck requests","audit request management backlog client evidence workflow"],"source_ids":["SRC1","SRC2","SRC3"],"no_result_note":null},"products_practices_and_standards":{"queries":["audit evidence request management PBC software request status workflow","audit client portal PBC priorities deadlines bottlenecks","PCAOB AS 1105 sufficient appropriate audit evidence"],"source_ids":["SRC1","SRC2","SRC3","SRC4"],"no_result_note":null},"component_combination":{"queries":["audit evidence request WIP limit","PBC request capacity audit client","audit evidence request throttle rate limit","audit request queue capacity WIP limit kanban PBC"],"source_ids":["SRC2","SRC3"],"no_result_note":"The search found an audit-request product with an internal Backlog-to-published gate and another with priorities, request-volume analytics, turnaround-time and bottleneck reporting, but no retained source made measured downstream capacity or congestion automatically govern releases with queue bounds, reserved critical flow, and hysteretic recovery."}},"sources":[{"source_id":"SRC1","title":"PBC Requests","publisher":"AuditDashboard","url":"https://www.auditdashboard.com/pbc-requests","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["The vendor identifies inbox fragmentation, miscommunication, duplicate requests, excessive manual follow-up, and difficulty determining what remains outstanding as PBC-process problems.","Its product centralizes requests, inquiries, documents, conversations, assignments, dates, submission status, review, requests for additional details, and outstanding-item visibility."]},{"source_id":"SRC2","title":"Request Board","publisher":"Punchcard","url":"https://guide.punchcard.com/auditor/requests-and-workpapers/request-board","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["The Request Board tracks each audit request with status, owner, due date, priority, category, files, comments, and an audit trail.","Requests can remain in an internal Backlog state and are published to the client by moving them to another workflow state, providing close prior art for visible auditor-side staging and gated release.","The documented publication gate is discretionary; the source does not describe a capacity-derived pressure signal, WIP limit, reserved critical path, or hysteretic recovery."]},{"source_id":"SRC3","title":"Engage | Complete Audit Collaboration Platform","publisher":"Circit","url":"https://www.circit.io/platform/engage","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["The platform manages PBC request lists with statuses, priorities, deadlines, assignments, messaging, templates, contextual follow-ups, and audit trails.","Dashboards track request completion and activity, while reporting identifies turnaround times, bottlenecks, trends, delays, and risk trends.","The product claims structured workflows and visibility reduce follow-ups, lost files, and back-and-forth, but the page does not describe pressure-triggered admission control."]},{"source_id":"SRC4","title":"AS 1105: Audit Evidence","publisher":"Public Company Accounting Oversight Board","url":"https://pcaobus.org/oversight/standards/auditing-standards/details/AS1105","source_type":"OFFICIAL_STANDARD","claims_supported":["The auditor must plan and perform procedures to obtain sufficient appropriate evidence supporting the audit opinion.","Evidence sufficiency depends partly on risk, and appropriateness concerns relevance and reliability.","Information produced by the company must be evaluated for audit purposes, so an audited organization’s capacity signal cannot determine evidence necessity, scope, or sufficiency."]}],"problem_evidence":{"status":"PARTLY_SUPPORTED","finding":"The retained product sources directly expose fragmented request handling, duplicate requests, manual follow-up, outstanding-item uncertainty, back-and-forth, delays, and bottlenecks, and they treat status, priority, ownership, turnaround time, request activity, and blockers as useful observables. They do not establish the proposal's stronger causal premise that audit-workstream release rates commonly exceed measured client validation throughput or that queue occupancy itself causes aging and rework.","source_ids":["SRC1","SRC3"]},"closest_prior_art":[{"name":"Punchcard Request Board Backlog-to-client publication gate","source_ids":["SRC2"],"overlap":"Audit requests may be drafted and retained in a structured Backlog with owners, priorities, due dates, files, comments, and an audit trail, then deliberately published into the client-facing workflow. This closely overlaps attributable staging and explicit release rather than immediate submission.","remaining_difference":"The documented release decision is not tied to a regularly computed downstream pressure state or acknowledged response capacity; no priority-specific WIP bounds, throughput-based demand signal, reserved critical capacity, lower recovery threshold, or recovery probe is specified."},{"name":"Circit Engage request management and bottleneck analytics","source_ids":["SRC3"],"overlap":"Centralized PBC lists expose priorities, deadlines, ownership, blockers, request activity, turnaround times, bottlenecks, trends, and contextual follow-ups.","remaining_difference":"The analytics inform coordination and prioritization but are not documented as a rule that prevents additional noncritical requests from being released when downstream pressure is high."},{"name":"AuditDashboard centralized PBC workflow","source_ids":["SRC1"],"overlap":"Central tracking, assignments, dates, automatic status updates, review, clarification, history, and outstanding-item visibility address duplication, miscommunication, and repeated follow-up.","remaining_difference":"The workflow monitors and automates admitted requests without coupling upstream request release to measured downstream handling capacity."}],"prior_art_disposition":"ADJACENT_PRIOR_ART","contrastive_claim_remaining":"Compared with a centralized request board that already supports auditor-side backlog staging, priorities, status tracking, and bottleneck analytics, a predeclared priority-specific pressure signal computed from released-queue occupancy, age, validated-response throughput, and clarification workload causes workstreams to withhold new noncritical requests in bounded traceable staging until capacity is acknowledged, while preserving a reserved critical path and using a lower recovery threshold; this reduces peak released backlog and request age without increasing combined released-plus-staged backlog or delaying critical work.","contrastive_claim_falsifier":"The contrastive claim is falsified if a timestamped replay shows that the pressure rule does not reduce peak released backlog or aging relative to ordinary backlog-to-publish management; merely displaces equal or greater accumulation into staging; fails to signal before overload; delays any material, fraud-related, statutory, or deadline-critical request; makes staged requests untraceable; or shows that ambiguity, unavailable records, approval dependencies, or intrinsically long procedures—not admitted workload—dominate delays.","gates":{"adequate_source_search":{"status":"PASS","rationale":"The bounded search covered direct terminology, PBC and provided-by-client synonyms, current products and an official audit-evidence standard, plus combinations involving backlog gates, capacity, WIP limits, throttling, and bottleneck analytics. Exactly four opened sources from four publishers were retained.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"supported_problem":{"status":"PASS","rationale":"Duplicate requests, fragmented communication, manual follow-up, back-and-forth, delays, blockers, and bottlenecks are directly visible, although the proposed throughput-versus-arrival causal model is not established; problem evidence is therefore partly supported.","source_ids":["SRC1","SRC3"]},"distinct_testable_claim":{"status":"PASS","rationale":"Close products already provide staging, publication gates, priorities, and congestion-related analytics, but the remaining claim distinctly requires measured downstream pressure to govern release and specifies comparative queue, age, traceability, and critical-delay outcomes.","source_ids":["SRC1","SRC2","SRC3"]},"bounded_next_test":{"status":"PASS","rationale":"A single completed-workstream shadow replay is limited and noninterventional. With thresholds and safeguards fixed in advance, it can compare the actual sequence with the proposed rule using releases, validated completions, both queue sizes, age, clarifications, priorities, and deadlines.","source_ids":[]},"no_obvious_safety_or_authority_stop":{"status":"PASS","rationale":"The retrospective replay changes no live request or audit judgment. A later pilot would require engagement-lead control because the auditor remains responsible for obtaining sufficient appropriate evidence; the reserved critical path, complete histories, explicit exceptions, and immediate rollback conditions address the obvious authority hazard.","source_ids":["SRC4"]}},"screen_survival":true,"world_novelty_boundary":"This bounded public-web screen found close adjacent capabilities—central request tracking, auditor-side backlog staging, explicit publication, priorities, bottleneck analytics, and turnaround reporting—but no retained source documenting the complete pressure-responsive release-control mechanism. It cannot establish world novelty, patentability, freedom to operate, market size, expert acceptance, regulatory acceptability across jurisdictions, or realized audit value."}