Design study prototype

Connect a domain you already own, without losing your email

Two mirrored portal pages — one customer-facing, one operator-facing — sharing a single simulated service. This is a simulation: it performs no DNS, hosting, email, certificate or backup operation of any kind, contacts no network, and is not connected to any real system. Every name, domain, address and reference in it is invented.

What this prototype will never do. Ayuda cannot read your DNS and cannot see your mail provider's settings. Nothing here asserts that a domain resolves, or that mail is working — only the customer can establish either of those, and the prototype is built so that no Ayuda-side event can be mistaken for that confirmation.

Open the two portals

Open them in two tabs, side by side. They share one event log, so an action in either tab changes the other immediately, without a reload — that is the thing worth watching.

Client portal

Northwind Goods

What the customer sees and does: the mail question, the DNS records, telling us the domain, where it is up to, and the two checks only they can make.

Site overview Connect domain Check it worked My email stopped
Ops portal

Operator console

What the operator sees and does: the typed request queue, the structured payload, the four actions in order, and the certificate job — including when it fails.

Dashboard Client Requests Request CR-4821 Environment #40001

Portal pages are built by other agents. A link that 404s means that page is not written yet — the shared service and the event log below work regardless.

Where the journey is right now

State
Baton
Environment
Primary domain
Certificate
Mail
May say "Live"

Jump to a scenario

Re-running the whole journey to reach one branch is tedious, so every interesting point is reachable directly. Jumping rewrites the event log — both portal tabs follow at once.

The event log

This is the whole source of truth. Both portals derive everything they show from these rows and store nothing of their own, which is why they cannot disagree. Read it top to bottom: who did what, in what order, and — in the fourth column — what that event does not mean. Greyed rows prefixed meta. are stage directions from this page, not things that happened to a customer.