Make every step of research inspectable.
ZeroWall Science brings agent reasoning, scientific methods, governed compute, evidence lineage, and delivery into one desktop workbench. Models propose actions. The runtime enforces boundaries. Research Store preserves facts.
From question to delivery, not just another answer
Research state lives beyond chat history. Every stage has explicit inputs, governed execution, and traceable outputs.
The whole research process in one workbench
Real desktop views show sessions, execution, evidence, and delivery. Concept art never pretends to be product UI.
Multi-project, multi-session research
Manage projects, long-running conversations, files, and inspectable agent traces in one window.
- Input
- Questions, papers, and datasets
- Output
- Project sessions, files, and research records
Agents and scientific capabilities
Encode methods as Skills, connect services through MCP, and split complex work into reviewable stages.
- Input
- Research intent and capability constraints
- Output
- Plans, tool calls, and stage artifacts
Recoverable compute jobs
Durable Runs preserve process identity, heartbeat, logs, deadlines, and declared inputs and outputs.
- Input
- Code, environments, and data assets
- Output
- Runs, logs, and collected Artifacts
Trace results back to code and data
Artifacts connect to the run, data, environment, and decisions that produced them.
- Input
- Runs, Artifacts, Papers, Decisions
- Output
- Explicit lineage and audit events
Turn evidence into deliverables
Publications freeze project snapshots; Presentations retain page visuals, revisions, and quality state.
- Input
- Validated research material
- Output
- Paper bundles, PPTX, and checksums
Six views of reasoning, execution, evidence, and delivery
Each architecture view reflects implemented project boundaries. Open any topic to inspect its components.
Reasoning remains separate from privileged execution
DSH orchestrates sessions and capabilities. Electron, the Host, and domain services retain authority over paths, credentials, execution, and research state.
Model output remains a candidate operation, never direct system authority.
RPC requests pass codecs, project ownership, and path containment checks.
Research Store independently retains objects, runs, evidence, decisions, and delivery state.
Models can change. Research boundaries should not.
Critical controls live in Electron, the Host, and research services instead of relying on model compliance.
A capability plane built for real research
Twenty-two first-party domain plugins share project ownership, permission, and scientific object contracts.
Sessions and projects
Organize conversations, files, tools, and scientific facts by project.
Skills and MCP
Hot-load scientific methods and connect stdio or HTTP services.
Scientific files
Managed attachments, PDF and Office parsing, viewers, and integrity checks.
Heterogeneous compute
Manage Local, WSL, and SSH execution through one contract.
Research Store
Persist data, runs, artifacts, papers, decisions, and audit events.
Publication and slides
State machines manage freeze, validation, reproduction, revision, and export.
Research question
→ Agent plan
→ Approved Local / WSL / SSH Run
→ Artifact + Evidence + AuditEvent
→ Publication / PresentationBring the research workbench home
The current reference distribution is Windows x64. Build-time and runtime checks restrict downloads to the trusted same-origin HTTPS executable.