Research-Quest: Scientific Discovery Platform

Created By
Saptaswa Deya year ago
Research-Quest A comprehensive desktop extension implementing the Research-Quest framework for systematic scientific reasoning through an 8-stage graph-based methodology. Overview The Research-Quest desktop extension provides researchers with a powerful tool for conducting systematic scientific analysis through a structured, graph-based approach. This extension implements the complete Research-Quest framework as defined in the Research-Quest.md specification, enabling: - Systematic Research Methodology: 8-stage process from initialization to reflection - Multi-dimensional Confidence Tracking: Bayesian belief updates with statistical rigor - Interdisciplinary Research Support: Bridge nodes connecting different domains - Causal Inference Capabilities: Pearl's do-calculus and counterfactual reasoning - Temporal Pattern Analysis: Dynamic relationship modeling - Bias Detection & Mitigation: Systematic bias identification and correction - Impact Assessment: Research significance and utility estimation - Collaborative Research Features: Multi-researcher attribution and consensus building Architecture 8-Stage Research-Quest Framework 1. Initialization: Create root node with task understanding 2. Decomposition: Break down research task into fundamental dimensions 3. Hypothesis/Planning: Generate competing hypotheses with detailed metadata 4. Evidence Integration: Bayesian confidence updates with typed relationships 5. Pruning/Merging: Graph refinement based on confidence and impact 6. Subgraph Extraction: Focus on high-value research pathways 7. Composition: Generate structured research narratives 8. Reflection: Comprehensive quality audit and validation
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Saptaswa Dey
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago