Pipeline

Paper-Pro Workflow

Structured manuscript pipeline with architecture, writing, skeptical review, verification, compliance, and provenance.

Quick reference

Core invocation details and the exact command surfaces users will touch first.

Type
Pipeline
Slash command
/paper-pro
CLI
bohr paper-pro

At a glance

The shortest useful summary of what this workflow is for and what it produces.

  • Builds a paper-shaped artifact with explicit structure before drafting starts.
  • Uses skeptical review and verification passes before promotion.
  • Produces a provenance sidecar alongside the final manuscript.

How to run

Start with the slash command in the REPL for interactive work, or call the CLI when you need a shell-native invocation.

In the Bohr research shell (REPL), enter /paper-pro followed by your topic or instructions. From a terminal, invoke the CLI as bohr paper-pro. Refer to the linked documentation for arguments, profiles, and environment setup.

Flow diagram

Stages and agent labels are indicative. Your configuration may swap or rename modules, but the diagram still shows the intended execution shape and handoff order.

Detailed guide

Full notes, usage guidance, and the longer explanation for how this workflow behaves in practice.

Overview

paper-pro is the manuscript workflow for teams who want a polished paper and an honest record of what the paper is actually supported by.

When to use it

Use it when the deliverable should feel like a professional paper rather than a short memo or raw literature brief.

Outputs

The workflow produces both the manuscript and the audit trail around it: plan, architecture, review, compliance, and provenance.

Practical notes

It works best when you start from a real evidence file or a verified local note set. If the evidence is thin, the workflow should narrow the claims instead of pretending certainty.

See also