Development record
Build checks, one received test email and the current preview limits.
Source and projects
The site includes a catalogue, static page build and enquiry application. Alex Roze’s public biography connects the tattoo practice and software work; Motherlabs is a separate independent project.
The preview is available for inspection. No installation package or template download is offered on these pages.
Build and behaviour checks
The build generates the pages; Astro diagnostics check the source. Behaviour tests cover selected designs, draft preservation and invalid form input.
One catalogue correction places AR-T-016 in both Traditional and Black & grey through its collections field. tests/discovery.test.mjs checks both memberships; a monochrome image alone does not determine style.
These tests do not measure phone gesture feel, search visibility or bookings. Those require separate observation under stated device or business conditions.
npm run build
npm run check
npm testDelivery test and preview
On 18 October 2026, Pacific time, a synthetic enquiry reached the bookings inbox with two attachments and passing SPF, DKIM and DMARC authentication. Replaying the accepted attempt after restart did not create a second send.
The delivery application retains receipts for retries. The observed restart behaviour covers one receiving application and the provider’s duplicate window, rather than unlimited duplicate prevention across hosts.
Mocked tests cover rejected and uncertain delivery outcomes while preserving entered information. The public development form still sends nothing and creates no customer enquiry, payment or appointment record.
Rejected → keep the brief → fix and retry
Acceptance uncertain → retain the same attempt → reconcile
Accepted receipt → replay the receipt → no second send
Preview → show the brief → nothing sentData and retention
The delivery test used a sending-only credential restricted to its sending domain. Credentials and private account details are not published.
Reference images are supplied to explain an enquiry. They do not grant permission for publication or model training.
In the public preview, text and retry details use the tab’s session storage. Uploaded files stay in the open page’s memory. No artist-facing enquiry is created.
The configured server schedules unconfirmed message-body cleanup after 24 hours and retains duplicate receipts for 30 days by default. Cleanup runs while the service is active or at its next start. Delivered Gmail messages have separate retention; the production host and mailbox arrangements remain undecided.
Release status
The development site is deployed for review, marked noindex and unable to accept real enquiries. Build and test records describe that review version.
Production launch still needs final content and policies, a receiving service, decisions for old URLs and activation checks. A deployed preview does not establish live customer delivery.
Cost and effort
No measured saving or return on investment is published. A useful comparison would include subscriptions, model use, time spent directing and reviewing work, and later maintenance.
Implementation and test records describe the software. Operational improvement would require studio records and a comparable baseline.
Reuse and licensing
Photographs, drawings, identity assets and website code have separate rights. Viewing this site does not grant a licence to reuse them.
Any future code release needs a source link, a stated licence, clear artwork exclusions and setup instructions. A visible repository does not itself grant reuse rights.
Enquiries and appointments
An enquiry, qualified enquiry, agreed appointment, verified deposit and completed appointment are different records. A conversion measurement needs authorised records that can be connected without unnecessary personal data.
A repeat appointment is a later completed visit within a defined customer group and period. Any comparison also needs to account for seasonality, offers and other changes.
Website tests establish none of the conversion, revenue, staff-time or repeat-appointment outcomes.
- Enquiry: the development preview currently discards it.
- Delivered: one synthetic inbox test observed.
- Appointment agreed: a separate studio record.
- Deposit received: a verified payment record.
- Appointment completed: a fulfilled studio record.
- Returned: a later completed visit within the defined group.
Search observations
Publication, indexing, search appearance and visits are separate observations. An AI answer mentioning a name is different from citing the right source or sending a visitor.
These pages describe the work and link its sources. Rankings and recommendations are not guaranteed; later observations would need a date, question and platform.
