Mission 1: domain to live AI website

00:00Result first

Your first result in this course is not another account or API key. It is a website that another person can open on a real HTTPS domain.

This walkthrough shows the complete path. We start in the Sell.Systems managed workspace dashboard, attach a website domain to the correct running instance, copy the instance-aware handoff, brief Codex, publish the site, and verify the result. The recording hides credentials and private learner data.

00:24Attach a managed domain

Begin by selecting the running practice instance that belongs to this workspace. Open Domains. For a public website, enter a unique first label and choose agenthost.link. Use agentenv.link only when the project is primarily an environment or API surface.

Choose Plan domain before making a change. Read the proposed hostname, target instance, and routing plan. This review step prevents a domain from being attached to the wrong environment. When the plan is correct, choose Add domain and confirm the requested addition inside the confirmation window.

The platform now handles public DNS, routing, and TLS. Do not edit public DNS manually. Wait until the domain state becomes active before asking the instance agent to publish the application.

01:03Copy the instance handoff

Next, open Agent and choose Instance Agent Handoff. Copy the complete handoff. It gives the implementation agent the instance-specific context it needs without asking you to reconstruct host details from memory.

Paste that handoff first. Under it, paste the website brief from the mission page and replace every bracketed field. Define the real purpose, audience, primary action, required sections, visual direction, supported facts, languages, and supplied assets. For this demonstration, we are building Mission One Studio: a clearly labelled fictional course example with no customer claims or fabricated metrics.

01:35Brief Codex and build

The agent reads the website delivery repository before changing files. That contract requires semantic HTML, responsive behavior, accessible interaction, factual metadata, narrow structured data, asset provenance, reduced motion, and a public release check. It also prevents generated imagery from being presented as customer proof or a product screenshot.

The visual used here was generated with Nano Banana 2 and reviewed before publication. A rejected draft contained interface-like text, so it was not used. The accepted image contains no screen, logo, writing, or fake dashboard, and its provenance manifest travels with the website.

Codex inspects the current runtime, builds the site, configures only the local web service described by the handoff, and leaves platform-owned DNS and TLS untouched. It then tests the public route instead of stopping after a local preview.

02:25Verify and submit proof

Verification is part of the build. Open the exact public URL and confirm a valid secure connection. Check desktop and mobile layouts for overlap, clipping, text containment, and horizontal overflow. Use the keyboard and inspect visible focus. Test reduced motion. Review the browser console and network requests. Confirm that the visible content agrees with the title, description, canonical URL, Open Graph metadata, Schema.org data, robots file, and sitemap.

Capture one desktop screenshot and one mobile screenshot of the same live site. Record the public URL, the main files or service changed, one implementation decision, the validation results, and the asset provenance. Never include passwords, tokens, private keys, cookies, or the full instance handoff.

Mark the mission page complete, then open Mission 1 Proof and submit that evidence package. Submission alone does not unlock the next activity. A human mentor reviews the result, and the next step opens only after a score of at least ninety-four out of one hundred.

You now have a repeatable operator path: connect the domain, copy the handoff, brief the agent, launch the website, and prove the public result.

This transcript describes the published production walkthrough. Chapter timecodes are synchronized to the final 03:26 narrated master.