Waymark · the editorial platform for scholarly journals

Every paper carries its own history.

Where it is, where it's been, and who has it now — held by the manuscript itself, instead of reassembled from memory and forwarded mail. The mail still goes out, but who was written to, when, and what came back sits on the record where both sides can see it. Editorial staff stop holding it in their heads, and an editor's day looks the way it always has: the same folders, the same queues, the same consultations.

See it working

Open the live demo

Sample manuscripts, on free demo hosting — no login needed. The host puts up a loading page of its own while the demo wakes, which can take a minute.

waymark-demo.onrender.com/?invite=tessera-quire-46a73a

Or start with what doesn't change →

Every step marked. Every number explained.

Submitted · QC'd · assigned · reviewed · decided — every waymark stays on the record.

Who this is for

Three people spend their week waiting on a manuscript. All three stop guessing.

Each sees only what their role permits — an author never sees editorial internals, and every view is authorized on the server, per request (requirements A19, I1–I48).

The author

The answer is already on the page

Where the manuscript stands, in words that mean something outside the editorial office — what it's waiting on, and how long that stage usually takes. Letters still arrive by mail, and they are also on the record, so an author reads the thread in place instead of searching for the message that had the decision in it.

A17–A20, A26 — plain-language status, what is being waited on, and correspondence in one place rather than only in the author's mailbox
Editorial office staff

Chasing is a system, not a memory

Chasers to whoever owes the next action go out automatically, on a schedule staff can see and change. Nothing is chased twice by accident, and nothing owed slips because the reminder lived in someone's head instead of on the record.

E27 — automatic, configurable chasers, with a Chasing view of what's owed and what came back
The editor

The same call, with the whole file open

An editor-in-chief still pulls in another editor's opinion before deciding, and still works the folders they know. What's new is that the manuscript's full history — every assignment, every invitation, every reversal, and the whole correspondence thread — is on one screen instead of reconstructed from memory and forwarded mail.

E28 — consultations; M20 — the correspondence thread on the manuscript; M1–M59 — the detail screen and its event timeline

What doesn't change

The workflow survives. The record underneath it changes.

This is a replacement, not a reinvention. The folder-and-queue model, consultations, and visible paper movement are the parts worth reproducing faithfully — and an editor who came up through the old system should recognize their day.

Folders and queues The same working folders — QC, awaiting assignment, under review, awaiting decision — stay the shape of the day.
Consultations An editor-in-chief can still pull in another editor's opinion on a manuscript before deciding.
Visible paper movement Where a manuscript is, and how it got there, stays a first-class view — not a report someone has to run.

Why the record had to change

Most publishing platforms don't lose data. They overwrite it.

None of the above works if the history keeps moving under it. An author can't be told what a paper is waiting on, and an editor can't be judged fairly, when the system quietly replaces what it recorded last time.

It happens to a person

When a first round of reviewer invitations is declined and a second goes out, the second date replaces the first. The associate editor who handled a slow first round looks one to two weeks slower than they were, in a number someone may use to judge them — and the original date is simply gone.

It happens to a meeting

A manuscript that later moves out of the state a report excluded it from can reappear retroactively, so the same report run a month apart returns different counts — and the board meeting spends its time arguing about which printout is right. On Waymark that report is answerable as-of any date, and returns the same numbers every time.

The five commitments

Five promises, each one a specific failure made unrepresentable

These aren't aspirations. Each is falsifiable in a five-minute demo, and each names a behavior other publishing platforms still have, that this one must not reproduce.

01

History is append-only

Nobody's work can be quietly rewritten after the fact. A correction is a new entry sitting next to the one it corrects, never a replacement for it.

the assignment-date problem above is structurally impossible when nothing is overwritten
02

Reports are reproducible

The figure you took to the board last quarter is still there this quarter. Every report is answerable as-of a point in time, and says which point it used.

re-run any report against last month's as-of date and get last month's numbers, exactly
03

Every number carries its formula

Nobody has to defend a figure they can't explain. Acceptance rate and turnaround time are the two numbers everyone asks for and almost no submission system defines — so the population counted and the arithmetic used are printed next to the figure, not buried in documentation.

every report ships its own Method and Provenance panel
04

Defaults do not hide data

A number is never wrong because someone forgot a checkbox. Nothing a journal would want counted is opt-in by accident, and any active filter is shown alongside the result it produced.

transferred papers are included by default, not behind a box someone has to remember to tick
05

Structured state is structured

The knowledge that currently lives in one person's side spreadsheet belongs to the journal. Anything staff track as a coloured sticky note or a private convention becomes a typed, queryable, auditable field.

a shadow data model built from sticky notes and side spreadsheets becomes part of the record itself

The honest alternative

Why not just fix the reports?

A reporting layer bolted onto an existing platform is the closest, most credible alternative, and it can genuinely help — it can snapshot an unstable system's numbers and make a given query stable.

It has a ceiling, though: it cannot fix the reason the numbers were unstable in the first place, because that reason lives in the platform underneath, which updates rows instead of recording what happened. Nor can a layer touch the workflow complaints — editorial staff have said plainly that those need the system of record itself to change.

Waymark takes the other path: get the history right first, and let reporting, audit, and reproducibility follow from a record most publishing platforms never kept.

Where this actually stands

Built, demonstrated, and still open

Published here because a page that hides its open questions reads as sales. These are the same open questions the requirements carry.

Running today, against synthetic data

  • ✓The append-only record, its projection, and as-of query
  • ✓Server-side authorization by grant, resolved per request
  • ✓The editor surface's core loop — queues, manuscript detail, search, workflow tasks
  • ✓A first reporting view with its Method and Provenance panel
  • ✓Automatic, scheduled chasers and a Chasing report on what's owed and what came back

Still open

  • —Author submission, reviewer invitations, decision letters, and consultations are specified, not yet built
  • —Whether this ships as a production system or a public demonstrator is undecided
  • —Historical migration from whatever a journal runs on today is unscoped
  • —Adoption is the real obstacle — editors who came up through the incumbent have no reason to want a change

The running demo spans an invented family of six journals and entirely synthetic manuscripts, authors, and reviewers — built to show the model, not to stand in for any journal family's real records.

Five minutes, no account

Open a manuscript and try to break its history.

Every claim on this page is falsifiable in the demo. That's the bar it was written to.

Open the live demo

Sample manuscripts, on free demo hosting — give it a minute to wake, and expect the host's own loading page first.

waymark-demo.onrender.com/?invite=tessera-quire-46a73a