Home / Make-A-Wish preview

Coming soon · Interactive sneak peek

A first step for a parent and a little wish.

A gentle, local-only prototype. No account, no data collection, nothing sent.

1northpole.earth / make-a-wish / preview
1NE A little wish, safely shared.⌁ Preview only · nothing leaves this page

Preview step 1 of 4: Welcome.

“A wish does not need to be perfect to deserve a thoughtful home.”

Designed for parentsClear choices, kind language, and privacy from the very first step.

Welcome to the preview

A calm space to imagine what would make them smile.

A parent or guardian guides every step. Children never create accounts.

Parent-ledYou remain in control.
Kind by designSimple language and gentle pacing.
Private by defaultNo preview data is sent or saved.
See the safety blueprint

✦A prototype. What you type stays in this page.

A quick parent check-in

Who is guiding this wish?

Enough to show how it could feel. No profile, no account.

Step 2 of 4
Your relationship to the child
Where will this family celebrate?

Region would shape language, consent, and delivery — not marketing.

A little wish

What would make them smile?

A nickname is enough. The real service would review privacy before saving anything child-linked.

Step 3 of 4

For example: “Milo”, “Little Star”, or “our curious inventor”.

0/280 characters in this page only.

A moment to review

Small details. Big care.

Clear, warm, and easy to change before anything is shared.

✦In the real service, this is where consent, child-data choices, and the parent’s final review would be made clear.
Preview summary

Your family’s little wish

Nothing here is collected or submitted.

Guided byParent
Celebrating inA snowy town
Child’s nicknameNot added yet
Wish ideas0 in this preview
  • A wish will appear here when you add one.
What would make the live service safe?

Verified consent, data minimisation, accessible journeys, human support, and a traceable operating model.

Where would this preview data go?

Nowhere. It lives in this page until you reload.

For the elves and engineers — the safety thread behind this preview

1 · Requirements → 2 · Development → 3 · QA → 4 · Release → The screen it builds → 5 · Observability

Closing the loop

This is the product the control thread protects.

The Labs follow one story — NP-AUTH-321 — from a sentence to approved code. This is the screen it builds.

PRIV-CHILD-001Visible here. Consent and minimisation — why this asks for a nickname rather than a real name, and a coarse region rather than an address.
A11Y-BASE-001Visible here. Accessible behaviour — why every step is keyboard-operable and announced to a screen reader.
AUTH-PASS-016Upstream. Credential policy for the parent account that precedes this flow. No account step appears in this preview.
AUTH-PASS-017Upstream. One-way password storage for that same account step. Nothing here collects or stores a credential.

See how the story was written See how it was built

Why this is still a preview. The Blueprint comes first. The family service follows when consent, safety, support, and evidence controls are ready.