SAME INFORMATION. A DIFFERENT WAY TO SHARE IT.

Harbor pilot: the remaining launch condition

A launch brief connects support readiness to approval and communication.

Fictional worked example · Not a published customer artifact.

Make this with my agent See the complete result ↓

Your agent can use your own context or help you try the fictional sample. Review a draft first; nothing is published without your approval.

01 / The familiar format

You could send this as an email.

A fictional email with the same underlying facts. Read it here, then compare how the HTML version presents the information.

Email · Fictional example

Harbor export pilot — September 7 readiness update

Team,

The export pilot is for invited teams only, to let them try the workflow. Broad availability is excluded, and no adoption or revenue target is set. Planned export tests passed September 7, 2026, but that establishes test completion, not launch permission or support readiness. No issue counts or readiness score are supplied.

The support guide is drafted but has not passed review. Morgan owns review, targeting September 10 without a guaranteed completion date. Guide acceptance is a required launch condition. Casey can decide on launch only after that acceptance; no approval is recorded. September 14 remains a proposed date, not a commitment.

Hold the customer announcement until Casey’s approval is recorded, and check the record before sending. The announcement draft is not included here. Morgan should update the support review log; Casey should use the launch approval record. The scope note, test record, review log and approval record are authoritative; their URLs are not supplied.

This snapshot does not deploy, approve, send or grant access. A wider launch, revised date or additional audience needs a separate decision. No customer-impact claim is supported.

02 / The HTML version

Same information. See what needs your attention.

This is the complete static HTML example, not a screenshot. Scroll inside the preview to read it all. It has no live data, scripts, forms, or external resources.

Inspect the complete HTML source

This is the authored source for the example. The preview above passes through our HTML sanitizer before rendering in an isolated frame.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Harbor pilot: the remaining launch condition</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f6f8f5;color:#20352f;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.14 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.3 Georgia,serif;overflow-wrap:anywhere}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.6 system-ui,sans-serif;letter-spacing:.08em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#174b40;color:white;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,230px),1fr));gap:20px;margin:24px 0}.card{background:white;border:1px solid #bbc5c4;padding:24px}.metric{font:500 38px/1.2 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px}.warning{border-left:5px solid #956118;padding-left:20px}a{color:inherit;text-underline-offset:4px}a:focus-visible,summary:focus-visible{outline:3px solid #956118;outline-offset:4px}table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:15px}th,td{text-align:left;vertical-align:top;border-bottom:1px solid #bbc5c4;padding:12px 8px;overflow-wrap:anywhere}caption{text-align:left;font-weight:700;padding:12px 0}pre,code{white-space:pre-wrap;overflow-wrap:anywhere}footer{border-top:1px solid #bbc5c4;padding-top:24px;margin-top:40px;font-size:14px}@media(max-width:480px){th,td{padding:10px 4px;font-size:14px}}@media print{body{background:white}.card,.lead{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main><header><p class="label">Harbor / Invited-team pilot / September 7, 2026</p><h1>Keep the announcement held.</h1><p class="intro">Export tests passed. Support-guide acceptance and launch approval are still outstanding.</p></header><aside class="lead"><p class="label">Decision state · not approved</p><h2>Casey decides after the support guide is accepted.</h2><p>September 14 is a proposed date, not a commitment. No launch approval is recorded.</p></aside><section><h2>The release in scope</h2><p>A reporting-export pilot for invited teams to try the workflow. Broad customer availability is excluded. No adoption or revenue target is supplied.</p><p class="note">Source S1.</p></section><section><h2>Conditions, not a readiness score</h2><h3>Recorded state at this snapshot</h3><table><thead><tr><th scope="col">Condition</th><th scope="col">Evidence and next action</th></tr></thead><tbody><tr><th scope="row">Export tests · complete</th><td>Passed September 7. Test completion is not launch approval. Source E1.</td></tr><tr><th scope="row">Support guide · pending</th><td>Draft exists; review is not accepted. Morgan owns review, targeting September 10. Source S2.</td></tr><tr><th scope="row">Launch approval · absent</th><td>Casey decides only after guide acceptance. Record the decision in the existing approval record. Source D1.</td></tr></tbody></table></section><section><h2>What happens to the announcement?</h2><ol><li>Morgan updates the support review log with the actual review outcome.</li><li>After guide acceptance, Casey records the launch decision.</li><li>Communications checks that record before sending the announcement.</li></ol><p class="warning">The announcement is held now. This sequence is not advance permission to send it.</p><p class="note">Sources S2, D1 and C1. The announcement draft is outside this bundle.</p></section><section><h2>Records to verify</h2><p>Scope note, test record, support review log and launch approval record. Their URLs were not supplied. No issue count, readiness percentage or customer-impact result is supported.</p><p>Sharing this brief does not deploy code, approve the release, grant access or expand the pilot audience.</p></section><footer>Fictional worked example by share/artifacts. Names, dates, figures and records are invented for demonstration. Static snapshot; no live data or automatic updates.</footer></main></body></html>

Make the next one about your work.

Take the task to your agent. We provide a request with the goal, example, and checks. Copy it into the conversation where your context lives.
Supply only what is missing. Use material your agent is authorized to access. Don’t substitute the example’s invented facts for your own.
Review a draft before sharing. Check facts, readability, and sensitive information. Publishing and choosing who can open it are separate, explicit decisions.

Make this with my agent

No publishing connection is needed for an initial local draft. Your agent needs to be able to create an HTML file; preview and connection support vary by client.