TL;DR

Papyria’s alpha is live. We’re executing configurable workflows on real Word & InDesign manuscripts with a small group of forward-leaning publishing companies. Early results show hours → minutes speed-ups while keeping editors in control via Tracked Changes and review gates.

Join our pilot programme

⸻

🛸 What shipped in alpha

Workflow engine – Deterministic, versioned pipelines for proofreading, copy-editing, formatting
Config as code – Per-publisher workflow configurations mapped to house style guides and templates (.dotx/.idml).
Execution runtime – Queue + idempotent jobs, retries, and audit logs; runs on-prem or private cloud.
Human-in-the-loop – All edits returned with Tracked Changes; optional approval checkpoints per step.

⸻

👀 A look at workflow configuration

Below is a high-level snippet for “Manuscript → Styled .docx” workflow:

workflow: word_style_normalisation/v0
inputs:
  docx
steps:
  - detect_structure: { headings: true, lists: true, quotes: true, emphasis: true }
  - map_styles: { template: ${template_dotx}, strict: true }
  - typographic_norms: { spacing: true, punctuation: en_GB, dashes: em/en }
  - qa_rules: { styleguide: "house-v3.yml", severity: warn }
outputs:
  - docx_tracked: s3://outputs/{id}-tracked.docx
  - report_html: s3://outputs/{id}-report.html

📄 Editors receive a .docx with Tracked Changes and a compact QA report summarising what changed and why.

⸻

Early signals from the field

Speed: Large manuscripts restyled in ~30 seconds; first-pass copy-edits in minutes, not hours.
Consistency: Style-guide compliance across titles/series without manual restyling.
Focus: Editors spend time on content decisions, not formatting mechanics.

(We’ll publish full benchmarks as we expand the test set.)

⸻

Integrity, safety & deployment

Editorial control: Every change is reviewable, reversible, and attributed by step.
Reproducibility: Frozen prompts, seeded operations, and version-locked models per workflow.

⸻