Skip to content

Roadmap

These are improvement priorities, not claims about current support.

Near term

  1. Act on research-search saturation. Build on the saturation record with follow-up discovery that reuses a finished run, so broadening a brief or widening the graph adds to the same candidate set instead of starting a new directory.
  2. Improve IEEE institution diagnostics. Extend the current named-profile doctor with clearer first-use adaptation and live access diagnostics while keeping secrets private.
  3. Productize ACM authorized access. Design a dedicated visible, isolated, exact-host browser contract with the same fail-closed standards as IEEE; retain manual fallback when access or page shape is unknown.
  4. Extend safe delta acquisition. Build on the existing library import/update plans to bind new frozen selections while preserving verified files.
  5. Expand composition guidance. Build on the shipped recipes, input templates, and run summaries; evaluate optional init helpers after their contracts stabilize.

Medium term

  1. Measure discovery quality. Build labeled venue/topic fixtures and report coverage, precision, recall, pending-abstract rate, and reviewer disagreement by source and discipline.
  2. Expand official enumeration. Add exact, auditable venue adapters where an official index or API exists, especially for IEEE and ACM collections, without weakening identifier requirements.
  3. Improve batch scheduling. Build on per-host parallelism, checkpoints, and pauses with retry scheduling across runs, while preserving rate limits and shared-session safety.
  4. Expand checked portability. Validate host integrations and IEEE browser workflows per operating system while retaining explicit file-credential setup and Windows DPAPI migration compatibility.
  5. Open a publisher plug-in contract. Let users register exact approved hosts and tested page contracts for the generic adapter without accepting arbitrary redirects or generated citations.

ScienceDirect browser automation is deliberately not on the roadmap unless publisher policy and a safe official integration make it appropriate.