# Method Research. Learn. Ingest. Execute: Match. Mock. Build. Prove. Ship. The [canonical skill](../skills/website-build-skill/SKILL.md) owns the method. | Stage | Owner | Reviewable result | | --- | --- | --- | | Research | Researcher | Saved library, fourteen-domain coverage, sources and gate receipt | | Learn and ingest | Every role | Reopened library, applied checklist and learning receipt | | Scope | Coordinator | Brief, capabilities and artifact ownership | | Match | Designer | Brand rules, tokens, conflicts and approved inferences | | Mock | Designer with Graphics | Three visual directions and a named human selection | | Choose and build | Builder | Smallest justified stack and selected implementation | | Prove | Builder, Designer, Optimizer | Accessibility, performance and discovery evidence | | Protect | Builder | Headers and exposed-surface checks | | Challenge | Different-family Reviewer | Read-only findings against a fixed candidate | | Ship | Coordinator then Builder | Authorized promotion, live checks and operations document | ASK DATE is the date of the user's request, fixed at engagement start. Researcher establishes it before intake using the [canonical rule](../skills/website-build-skill/playbooks/research-and-memory.md#ask-date-rule). A source publication/update date describes the source. An access date records an actual opening. Revalidation records whether a claim still applies and what was reopened. A freshness window limits reuse. A derived floor is a qualified lower bound, never proof of the actual day or later currency. Missing provenance or current research keeps dependent work BLOCKED. SOLO follows all seven roles sequentially with self-handoffs and a framing reset. TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first. Record seven setup acknowledgements, one writer per artifact, and a saved research gate. Neither mode earns independent review from a second name in the same model family. Use PASS, FAIL, BLOCKED or NOT APPLICABLE with evidence. Never convert absence into a pass. The user owns the resulting library, claim ledger, domain checklists, decisions and handoffs. Keep them with the website project. The skill repository is the method, not storage for client work.