Skip to main content

Papyrus

Inside Papyrus

Humans Steer. Machines Operate.

Editors set mission, policy, topics, and taste. The system runs continuously inside that guidance—not off reader surveillance.

Papyrus is built around a different bargain: humans steer, machines operate. Publication doctrine—mission, policies, and section priorities—tells the newsroom what outcomes matter and what standards cannot be crossed.

Editors guide discovery with explicit questions, themes, and trend lines. That guidance can be broad strategic direction or a specific assignment. It is editorial intent, not a stream of chat prompts.

As sources arrive, human reviewers rate, vote on, and comment on references. Those decisions shape the curated structured knowledge graph that future planning and drafting rely on. They are not cosmetic feedback.

The system does not tune itself to individual reader behavior. It does not personalize headlines to maximize engagement. It improves when editors accept or reject proposals, adjust policy, refine section doctrine, and record why a source is trusted or excluded.

Papyrus supports high-touch and low-touch operation. Set stable policy and let the autopilot continue on course, or steer each cycle with assignments, curation calls, and coverage pivots.

When needed, humans issue direct reporting assignments or write a piece by hand. The default remains automated execution inside human-defined boundaries.

Steering becomes a durable asset. Your mission and taste persist across editions instead of disappearing after a single session.