# Wildworth — site and agent-ownership plan

## Position

Wildworth sells agent-run websites, digital products, automation, and the design systems that keep them coherent. The site is also the proof: visitors can change its visual direction, inspect live design studies, compose a real project brief, scope an engagement, and see the operating loop behind every build.

The promise is deliberately bounded: agents prepare and verify work; a human approves scope, secrets, spending, legal claims, and production deployment.

## Information architecture

```text
wildworth.com/
├── #work          Design studies with live token presets
├── #services      Launch Site, Agent-Managed Site, Vibe System
├── #lab           Brief Composer and engagement configurator
├── #shop          Product previews with honest availability
├── #agent-loop    Brief → Architect → Design → Build → Review → Ship → Learn
└── #start         Exportable project brief and next-step handoff
```

Future routes are intentionally deferred until each has enough original content: `/work/{study}`, `/services/{service}`, `/lab/{tool}`, `/shop/{product}`, `/journal`, `/changelog`, and `/start`.

## Conversion path

1. Understand the offer in one screen.
2. Change the page’s “vibe” and generate a useful artifact.
3. Inspect the design range.
4. Choose an outcome, not a vague list of capabilities.
5. See exactly what agents own and where humans approve.
6. Copy or download a structured brief.

Primary action: **Build my brief**. Secondary action: **Open the lab**.

## Product surfaces

- **Launch Site** — strategy, visual system, production site, launch checklist.
- **Agent-Managed Site** — ongoing content, experiments, QA, maintenance, and a public change ledger.
- **Vibe System** — reusable tokens, components, prompts, governance, and deployment workflow.
- **Design studies** — speculative work clearly marked “Concept”.
- **Build Lab** — tools execute locally in the browser; they do not pretend to call agents or deploy infrastructure.
- **Product shelf** — Preview or Coming soon until real purchase/download destinations exist.

## Agent operating model

| Stage | Agent responsibility | Human boundary | Artifact |
| --- | --- | --- | --- |
| Brief | structure goals and constraints | approve scope | build brief |
| Architect | map pages, data, and acceptance criteria | approve architecture | site map |
| Design | create tokens, compositions, and interaction rules | select direction | design system |
| Build | implement components and integrations | provide protected access | production candidate |
| Review | run accessibility, security, responsive, and content checks | accept exceptions | QA report |
| Ship | prepare release and rollback plan | approve production deployment | release |
| Learn | read approved analytics and support signals | approve experiments | change proposal |

## Hosting handoff

Before production: initialize a Git remote, confirm the hosting provider, connect DNS for `wildworth.com`, add a real contact destination, configure analytics with consent, and supply server-side integration credentials. Secrets never belong in this static client.

## Quality gate

- no invented customers, metrics, testimonials, or deployment activity;
- usable without JavaScript for core reading and navigation;
- keyboard-operable command palette, menu, filters, forms, and dialog;
- no horizontal overflow at 320, 375, 414, 768, and 1440 px;
- reduced motion support and visible focus states;
- no user content inserted through `innerHTML`;
- valid metadata, canonical URL, and structured data;
- local checker passes before every release.