Loading project…
Continue with GitHub Continue with GitLab
By continuing, you agree to our Privacy Policy and consent to the data handling summarised below.
papyro

Your projects

Paste the HTTPS URL of a papyro-enabled GitHub or GitLab repository.

Connect a repository

Paste the HTTPS URL of your GitLab or GitHub project repository.
papyro will clone it to the server and open it.

papyro
Not built
Overview
Documents
Customer requirements
Input docs
Waiting on
Master Wiki
Loading…
Readiness
Deliverables
Released
Blocked
Loading…
Loading…
The customer's requirement list for this project, imported read-only from your SoW or RM-tool export — not the ECSS standards' own requirements.
Technical ?
Management ?
Product Assurance ?
Click the Customer requirements tab to load
Documents
No input documents yet.
Upload a SoW, ICD, or other customer document.
Select a document to read
Waiting on
Open points owed to this project.
All
Overdue
Unassigned
Master Wiki not built yet
Build the Sphinx site to preview it here.
LISE — Space Engineering Assistant
papyro
Changes
Files
Review
You edit a private copy of the project. You save and submit one document at a time, and nothing reaches the team until a review is approved.
History
Review
Select text, then press Comment — here, in the toolbar, or Alt+R.
All
Open
Mine
Notes
RIDs
Drifted

This is the approved baseline on main — start a draft to make changes

Applied by LISE
Wiki not built yet
Build the site to see this document as your team will read it.
Look up ECSS definitions & abbreviations
Type to search ECSS definitions and abbreviations
New chat
Click ▶ Run to check this document
Document info changes save automatically
LISE
DRD
Terms
Related
Reqs
Check
Calc
Info
Comments
Provider
Repository (owner / repo-name)
Personal access token
GitHub: Settings → Developer settings → Personal access tokens. Required scope: repo.
papyro Template Kitchen editing
✦ Draft this template with LISE…
Import from Word document…
+ New style (from current)
Delete this style
md_style.sty
dummy document not built yet

Click ▶ Build to compile the dummy document
with the current style and see the PDF here — or switch to Wiki to preview the HTML output.
papyro Settings
Project overview

Shown on the project dashboard and the wiki homepage. Markdown supported.

Company description

Fills the About the Supplier box in every document. Markdown supported.

Project identity

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.

Default signatories

Pre-filled on every new document.

Default document image

Default cover image on every document's title page.

No image set

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.