The Delivered Suite · 2027
B · The Tile Wall
Beatriz & Rafael BittencourtThe Wall Entire
Nine pieces · Two carry a name
Nine pieces · Two carry a name
Every piece below is the delivered artwork, not a mock-up of it. The panel is live: put a name in it and watch each piece that carries a name take it, exactly as it does in a real print run.
The pieces that read the same for the whole room carry no name at all — and we say so.
Not decoration — every one of these has a job, and they are the same inks the pieces below are printed in.
Aa
Aa
A direction is as much what it turns down. This list was written when The Tile Wall was chosen, and every piece below holds to it.
The specimen above is the delivered artwork, with its real copy. This piece IS personalised: the suite ships a platform edition of it, and that is the file set for each guest.
{{GREETING}}{{GUEST_NAME}}{{RSVP_QR}}
Each guest's own code — live, and it scans. No piece in this suite carries a zone for it, so it reaches the guest through their personal link.
Not every piece should be personalised. This one reads the same for the whole room, so it carries no placeholders — one design, one print run.
no placeholders
Delivered here as one design. It is a piece the platform personalises per guest wherever a suite ships its platform edition.
no placeholders
no placeholders
no placeholders
no placeholders
no placeholders
no placeholders
This piece already carried a guest's name — it shipped showing real ones. The platform simply sets each guest's own.
{{GUEST_NAME}}
The screens below are the real interface, in the real stylesheet, doing the real arithmetic. The guest list is invented — no real client’s list appears here, and none ever will.
Not printed pieces — documents the software composes from the event itself, set in that event’s own design system rather than in ours. The figures in them are sums of the rows beneath them, never a second record that could drift.
Every impression below is the same delivered file — Place Cards — with a different guest's name set into it, exactly as it comes off a real run. Not a mock-up: it is the piece shown above, personalised by the same code. The names are examples.
12 guests shown across 2 sheets. A real list simply continues — one run, one file per guest.
At the guest's own link the platform renders Invitation — this file, not a separate digital version — and adds a reply panel to it. On the left, as it prints, with no trace of the panel. On the right, as it opens.
The panel is injected by the platform, not drawn by the design, and the printed card carries no trace of it. The right-hand state shows how it reads; for the platform to compose it into this piece, the file declares the empty container the Living Invitation expects.
The nine designs above are delivered as print-ready files — at the true trim size, with the backgrounds and the fonts the printer expects. The two that carry a name become a personalised file for every guest on the list.
Two of the nine pieces carry a name. The rest read the same for the whole room, so they print once — and each one says so.
Each guest's own code opens their own page. The same code, read at the door, marks them arrived — so the host knows who is in the room without a clipboard.
The table numbers above are generated from the event's own list, not typeset one at a time. The seating chart is drawn in the portal from that same list, so moving a guest between tables is a change of one field — not a new piece of artwork.
The same card, at the same guest’s link, with a reply panel drawn into it. Not a separate digital version in a different style — the design itself, continued. It is further down this page, in both of its states.