`adopt_look`

Take a look as the brand. Make one of the six looks the company's brand: its colours, fonts and email frame, with the company's own name and logo kept. It asks the owner's yes (one card for the colours and fonts, one for the emails unless they made their own); nothing changes before, and the next site build and email use it. Use it after the owner picks from looks; their own brand.json always wins otherwise.

Where it is

In the online area (your website: pages, forms, sign-ups, the member area, selling, classes and calls, going live; its look; payment links; course progress; giving or taking away member access): open it with tools_for { area: "online" }, then call it with use_tool { name: "adopt_look", args }.

Does it need a yes?

Needs the owner's yes: it makes a yes card, and nothing happens until the owner taps yes. Here: the brand's look waits for its yes.

Inputs

Input	Type	Needed	About
`look`	"journal" \| "signal" \| "hearth" \| "gallery" \| "onyx" \| "market"	yes	The look the owner picked from looks.
`task`	integer	yes	The task number, e.g. 12. · 1 or more
`run_id`	string	yes	The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "adopt_look",
  "arguments": {
    "look": "journal",
    "task": 12,
    "run_id": "the run_id from start"
  }
}

When it is refused

invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.
not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.
not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.
taken: Someone else holds it (another AI on that task). Pick another task.
stale: It changed since you read it. Read it again and use the new version.
failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.