Research Problem and Gap Discovery

Editorial synthesis grounded in the source pattern. Early research development where a bounded literature and domain framing must be examined for consequential unanswered questions.

Academics aim to identify meaningful gaps in the literature, yet individual expertise constrains visibility and the accelerating volume of publications makes comprehensive awareness unattainable. Blind spots, disciplinary assumptions and information overload limit the ability to detect novel or underexplored areas.

Editorial synthesis grounded in the source response. Combine domain judgement with a systematic, bounded evidence map. Assemble and classify relevant literature, identify candidate absences, contradictions or weak connections, and attach supporting sources and uncertainty to each. Actively test candidates through fresh searches, adjacent terminology and expert review. Do not treat low frequency, database absence or retrieval failure as proof of novelty.

• A bounded evidence map and source-linked set of candidate gaps or unresolved questions.
• Classification of each candidate by gap type, evidential strength and plausible alternative explanation.
• Expert validation that does not equate absence, low frequency or retrieval failure with novelty.

People define purpose and boundaries, supply or authorise source material, inspect intermediate representations, resolve ambiguity, approve consequential outputs, correct errors, and remain accountable for scholarly, pedagogical, legal, or organisational decisions. A generated recommendation or draft is not an approval decision.

Source-stated improvement concerns

• Integrate grant and funding databases to align identified gaps with current funding priorities.
• Expand multilingual search capabilities to address bias toward English language literature.
• Develop stronger validation mechanisms to assess the reliability of artificially generated gap suggestions.
• Provide case studies demonstrating how identified gaps evolve into research questions and projects.

Inferred workflow risks

• Inferred: unstated constraints.
• Inferred: scope drift.
• Inferred: ambiguous success conditions.
• Inferred: duplicate ingestion.
• Inferred: unsupported formats.
• Inferred: lost provenance.
• Inferred: partial imports.
• Inferred: database coverage bias.

• Minimum viable implementation: a documented human procedure using the ordered modules: Workflow Briefing and Context Definition → Source and Record Ingestion → Scholarly Search → Semantic Retrieval → Bibliographic Metadata Management → Summarisation → Metadata and Tagging → Knowledge Base Indexing → Research Gap Analysis → Argument and Concept Analysis → Perspective Simulation → Source Linking and Citation Grounding → Output Quality Evaluation → Recommendation and Ranking → Human Review and Approval.
• Robust implementation: add explicit schemas, source identifiers, access controls, logging, exception queues, independent evaluation, backups, and named approval owners.
• Low-code implementation: use forms and a workflow orchestrator to connect bounded services, with approval gates before external communication or state changes.
• Local or privacy-preserving implementation: keep sensitive artefacts in controlled storage and prefer local extraction, transcription, search, or model execution where capability and governance permit.
• Speculative implementation: more autonomous coordination may be explored only with constrained tools, stop conditions, audit logs, and human authority; it is not implied by the source pattern.