Catalogued.
Every project we admit receives a folio number, a colour-coded spine, and a small index card with three sentences explaining what it is for. If three sentences is not enough, the project is split.
N° 01 / TITLE CARD / FOLIO 0001
A municipal bureau for the systematic care of projects, restored with the patience of an archivist and the discipline of a Swiss draftsman.
SCROLL ↓ SEVEN PANELS · ALL ALIGNMENT MARKS PRESENT
miris-project.net is a workshop where complicated projects are catalogued, tagged, indexed, and gently returned to their owners. We treat your initiatives the way a 1960s municipal records office treated its drawer of municipal blueprints — with care, precision, and a small sense of humour about the whole business.
Every project we admit receives a folio number, a colour-coded spine, and a small index card with three sentences explaining what it is for. If three sentences is not enough, the project is split.
Tasks snap to a baseline of eight units. Owners snap to a single name. Deadlines snap to Fridays. Anything that refuses to snap is returned to the corridor with a polite request for clarification.
The grid is rigid; the room is not. Coffee is allowed near the drafting table provided it does not touch the original. Notes in margins are encouraged, particularly small marginal questions.
We do not pretend the typewriter never existed. The interface borrows registration marks, paste-up corners, and section cartouches from the printer's tray because those tools were tools of clarity long before they were aesthetics. They still are.
Six instruments, six functions. Each is one isometric tool you already know how to hold. None of them are software metaphors pretending to be something else.
A drawer per workstream. A label per drawer. No nesting beyond two.
People, sorted by hand. Owners are humans, not avatars or rectangles.
Long-form plans. Rolled, capped, dated. Unrolled only when necessary.
Approvals are a deliberate act. One stamp, one owner, one ink colour.
Counting that you can hear. Velocity, burn, and budget — beads that move.
Time as a face, with gears showing. We tell you why a deadline moved.
First the protocol; then the protocol's footnotes. We list both, because hiding the second one is how projects acquire ghosts.
One folio. One owner. Three sentences of intent. A spine colour chosen from the warm shelf, never the cool. The folio is logged into the day book by hand.
T-square down, triangle aligned, all pieces face up. We do not begin until every piece is visible at the same time.
Each milestone receives a small terracotta cross. The crosses mark where future revisions must land — without them, no revision ever lands in the same place twice.
The original goes back to the team. The carbon stays in the archive drawer, indexed by date and spine colour, available on request without ceremony.
A composed scene. Each object is real work, in mid-flight, arranged on the same table at the same time.
Six small observations from this season's day book. All quoted with permission, dates redacted, names changed to initials.
“Reduced our weekly status meeting to one folio card. The card is read aloud, then filed. The meeting now ends.”
“Spine colours have done more for cross-team comprehension than three previous taxonomies combined. People can now point.”
“The day book is the only document I never feel like apologising for. It is short, dated, and honest.”
“Stopped pretending we have eleven priorities. We have three. The other eight are 'see also' on the back of the card.”
“Our review meetings now happen at the drafting table. Nobody opens a laptop. We read what we made aloud, in turn.”
“Filed three projects this quarter. Properly filed, not cancelled. The bureau gives them a quiet shelf instead of guilt.”