Lonely Pine AI Build Brief
Halehaku Maui

One project. Two halves. You pick your half.

A family art gallery and farm shop on the road to Hana. Building it properly means two genuinely different jobs. They are peers, not a senior one and a junior one. You take the half you want to build, and Nalu takes the other.

Prepared for
Amit
Prepared by
Nalu, Lonely Pine AI
Date
September 2026
Your call
Lane A or Lane B
01 / The client

Halehaku Maui. Mile marker 1, road to Hana.

The first real stop for everyone driving the road to Hana, and their own name for themselves, straight off the window decal: Halehaku Maui, Family Farm Shop. It is an art gallery with a cafe corner rather than a cafe with a gift shelf. Three makers sell through it. The shop is already a design system: white walls, pale floors, and every bit of colour in the room comes from the work hanging on them.

Juliet

Hand painted silk, kimonos and tops on crepe de chine and charmeuse, dyed rather than painted. T-shirts in florals and horses. Original geode art, one of a kind, never repeated. An organic skincare line.

Ty

Surf photography, a Volcom team rider since 1993 who winters at Pipeline and calls it Aqua Therapy. Also woodwork and T-shirts. Sold as originals and as prints in a range of sizes and materials.

Moon

Pottery, made in Hana. The shelves carry bird bowls and teapots among other pieces, though exactly what is whose is one of the things still to confirm with the family. The smallest catalog of the three today.

02 / The two lanes

Pick the one you want to build.

Design to launch

Lane A · The public site

The storefront. A parent site carrying the shop's own story, then a shop that splits by maker, rendering a catalog it reads but does not own. Five design directions are already built and live for the family to choose from, and real photography throughout, no stock. The whole arc of a client engagement, design through launch, compressed into something small enough to finish.

You'd touchHTML + CSS from a design system · an image pipeline · Cloudflare Pages · DNS cutover · on-page SEO
Product + tooling

Lane B · The maker's portal

The front door one of the makers uses herself. She uploads a photo, swaps a photo, edits a description. That is the entire surface area, and keeping it that small is the product rather than a constraint, because off-the-shelf store admin has already defeated her once. Checkout and card data stay on a commerce backend behind it, so the portal never touches either.

You'd touchTypeScript on Workers · D1 schema + migrations · image upload to R2 · auth · a Pages front end
Where the halves meet: one catalog contract, describing a product and its images, variants and fulfilment. Lane B writes it, Lane A reads it. We define that shape together first, before either side builds against it, because it is the only place the two can collide.
03 / True either way

Four things that hold whichever lane you take.

01Client credentials and client contact stay with Nalu. Neither lane needs them. The portal gets built against test data, and anything that needs the family gets asked through Nalu.
02No card data in anything we build. Checkout lives on a commerce backend that carries that burden. This one is not a preference, it is the condition the client set for rebuilding at all.
03Nothing about the family gets published until they confirm it. Our own notes and the meeting record disagree about who is related to whom, and there is at least one maker nobody wrote down. Names and credits get checked before they go on a page.
04Never invent a price or a product detail. Only a handful are actually on record and they sit with Nalu. A placeholder has a way of shipping as the real thing.
Your seat: you take as much as you want to take, starting small enough to finish. You will not be handed a ticket and left alone with it. We work the same session together, and the piece you ship goes live with your name on it.

Lane A or Lane B. Tell me which one you want.

Lonely Pine AI · JDKC Ventures LLC · nalu@lonelypine.ai