papyro stores your project as a repository in your own GitHub account and keeps a working copy here. It needs permission to create that repository and push your documents to it.
You can read and edit existing projects; creating or syncing a project needs the connection.
LISE needs an AI provider before it can assist you.
Paste the HTTPS URL of a papyro-enabled GitHub or GitLab repository.
Paste the HTTPS URL of your GitLab or GitHub project repository.
papyro will clone it to the server and open it.
Shown on the project dashboard and the wiki homepage. Markdown supported.
Fills the About the Supplier box in every document. Markdown supported.
The facts every title page repeats — the project's own name and ID, and the Program / Customer / Supplier rows.
2–12 characters: A–Z, 0–9, hyphen or underscore. Existing documents keep their identifiers until you apply the change below.
Pre-filled on every new document.
Default cover image on every document's title page.
A review gate is a formal checkpoint where the customer accepts that the project may proceed (ECSS-M-ST-10C Rev.1, §4.4 “Project phasing”). Every deliverable is due at one of them — the gates you switch on here become the columns of the matrix below. Hover a gate for what it reviews and when it falls. Not every project runs all of them; ECSS expects the set to be tailored. Removing a gate unassigns its documents. + Custom gate… adds a review this project runs that ECSS does not name, and places it in the lifecycle.
Row = ECSS branch, column = review gate. Drag a card to move it — only slots that keep a document's issues in order will accept it. Right-click a card to add its next issue, or to rebranch or remove it. Click a gate's date to set the review deadline. An issue stays locked until its predecessor has a gate, and locked for content edits until that issue is Approved / Complete.
Generate the document set issued to a subcontractor (or by a subcontractor to a sub-subcontractor) — the inverse of this project's own customer-supplied inputs.