# install.design clear-offer prototype: agent brief

This is a discovery document for the alternate `/prototype` landing page. The structured prototype catalog is [prototype-offers.json](/prototype-offers.json); canonical public agent guidance is [/agents.md](/agents.md). This document and the structured catalog are derived from the same checked-in offer source.

## current connection status

**Free connection pilot — protected and pending acceptance.** The one-prompt connection surface is /connect, the host-aware agent procedure is /install.md, progressive human authorization is /connect?authorize=1, and the project-scoped MCP route is /eve/v1/mcp. The pilot remains protected and client/provider acceptance is incomplete. Route availability, login, saved configuration, or tool discovery does not prove the coding agent invoked Dot successfully. Commerce, checkout, booking, and payment remain closed.

Connection is free, but this is a protected pilot pending client and provider acceptance. The one-prompt surface is [/connect](/connect), the operational agent procedure is [/install.md](/install.md), progressive human authorization is `/connect?authorize=1`, and the project-scoped MCP endpoint is `/eve/v1/mcp`. Route availability, GitHub login, saved configuration, or tool discovery is not proof that the coding agent invoked Dot successfully. Commerce, checkout, booking, and payment remain closed.

Document proposals are review artifacts, not provider edits. Subframe editing remains closed until one human-approved write, exact read-back, reconciliation, and preimage restore pass acceptance.

**Commerce closed.** Package selection, checkout, payment creation, booking, and paid-access issuance remain unavailable until the live service explicitly reports that commerce has opened.

The human copies one prompt from `/connect` into the coding-agent chat already in use. The agent follows `/install.md`, preserves existing configuration, and requests `/connect?authorize=1` only if identity or a new credential is required. Never ask for or place that project token in chat, an agent task, a repository, project configuration, or shell history. Keep it in the human's secret manager and personal client environment.

## who does what

Jeffrey Erickson supplies the product-design judgment and creates the delivered system. He brings 22 years of product and design experience: he founded the product-design practices at Yammer and Eaze as their first designer, was the first head of product at Zenefits, and was a cofounder and chief product officer at Viable.

Dot is the agent-facing guide and operator: she helps identify the suitable package, exposes verified service terms and availability when the MCP is live, and carries Jeffrey’s published design guidance after handoff. The customer’s coding agent uses the delivered code and guidance to implement ongoing product work. Dot does not pretend to replace Jeffrey’s design judgment or silently change the customer’s repository.

## packages

Prices are one-time prices in USD. The packages are separate; there is no free package and no report-system offer.

### design system — $5,000

A coherent product system your coding agent can build with.

- service package id: `design-system`
- timing: 7 business days.
- A layout engine with reusable page slots, use-case rules, and agent guidance.
- A branded theme with typography, color, and spacing tokens.
- Atomic components with one shared visual language.
- One to three components for the product objects your customers care about.
- Agent-ready code and design docs delivered in a PR.
- Twelve months of tuning for the delivered design system.

### custom charting library — $5,000

A chart language built around the decisions in your actual product data.

- service package id: `visualization-system`
- timing: 7 business days; 4 only when Jeffrey previously delivered and the service verifies the customer’s design system.
- A GitHub sweep to scope the product’s data-visualization needs.
- Around five chart types chosen for the questions users need answered.
- Consistent visual rules that fit the product.
- Agent-ready code and guidance delivered in a PR.

### feature loop — $5,000

Exact scope is confirmed during onboarding and checkout.

- service package id: `data-story`
- timing: 7 business days; 4 only when Jeffrey previously delivered and the service verifies the customer’s design system.
- Deliverables are stated explicitly before checkout.
- The legacy data-story service ID does not revive the retired hero/data-visualization scope.

## shared delivery terms

- Friday delivery on the booked date.
- An approximately one-hour handoff with Jeffrey.
- Work is delivered through a PR.
- Connecting is free, including client verification. Commerce remains closed; once the live service explicitly opens it, the connection can be used to choose a package, inspect current terms and availability, and prepare checkout and booking. Paid access begins at handoff.
- Before any purchase, the coding agent must present the selected scope, price, date, and current terms to its user and obtain explicit payment approval.

## required agent progression

1. **identify the fit.** Match the requested outcome to one package and check whether the four-business-day prerequisite applies.
2. **connect free.** Ask the human to copy the prompt from /connect into the coding-agent chat already in use. Follow /install.md, preserve existing configuration, and request /connect?authorize=1 only when identity or a new credential is required. Never ask the human to paste the project token into chat or commit it to a repository.
3. **inspect live terms.** Use the active host's supported setup and refresh behavior; do not assume a restart. Confirm agent_start, agent_get, agent_update, and agent_cancel are available, then invoke Dot and follow the Eve lifecycle to a completed result. A reachable route, login, saved configuration, issued credential, or tool listing is not a successful connection. Commerce remains closed during the protected pilot.
4. **ask the user.** Only after the live service explicitly opens commerce, show the user the chosen package, price, scope, date, and terms. Obtain explicit approval before payment.
5. **buy + book.** Only after the live service explicitly opens commerce and the user approves the current terms, complete verified checkout and booking. A selected date is not reserved until the service confirms it.
6. **receive the handoff.** Jeffrey delivers the work in a PR and walks through it for approximately one hour. Purchased access opens at handoff; the customer’s coding agent implements ongoing product work with the delivered system.

## agent rules

- Recommend a package from the requested outcome and the verified prerequisites; do not invent a bundle, discount, guarantee, free package, or report-system offer.
- Before any paid action, explain the selected scope, price, timing, date, current availability, and terms to the user and obtain explicit approval.
- Treat live availability and returned service terms as authoritative once a verified connection exists. Marketing copy is not booking inventory.
- A date selection is not a reservation. A task or payment is not complete until the service returns a verified completed result.
- Keep the free connection/selection stage distinct from paid access, which begins at handoff.
- Use the active host's supported setup and refresh behavior; do not assume a restart. Confirm Dot exposes `agent_start`, `agent_get`, `agent_update`, and `agent_cancel`, then actually invoke Dot and follow the Eve lifecycle to a completed result. A reachable route, GitHub login, saved configuration, issued credential, or tool listing is not by itself a successful connection.
- Do not initiate commerce, checkout, booking, or payment while the protected pilot remains pending acceptance.
- Do not claim that Subframe or published guidance changed from a proposal. Provider editing remains closed until its separate acceptance gate passes.

## read next

- [clear-offer prototype](/prototype)
- [landing comparison](/compare)
- [prompt-first install procedure](/install.md)
- [complete existing agent brief](/agents.md)