Scale Intelligence■ Docs
Docs / Reference / act: decide brand design

act: decide brand design.

The brand, the value's path, the decision (accepted, declined, changed) and, when changed, the tenant's own value, with the reason to the decision as a fact at brand scope: the brand's memory, read by the merge, so a changed value stands as stated by the tenant until the site changes and a declined one is never…

Figure 1POST /v1/act/decide_brand_designspecified
CALLERyour app or an agentholds the keyAPI GATEWAY/v1/act/decide_brand_des…4 headersCORE: ACTrung brandgrant actRECORDreads or writesCARD, 200body BrandDecisionThe input is DecideBrandDesignInput. Every response carries the contract's hash.flows forwardthe result
The caller sends DecideBrandDesignInput to /v1/act/decide_brand_design. The platform returns a card whose body is BrandDecision.
POST/v1/act/decide_brand_design

Record a decision on a brand’s design system. The call needs the brand rung under a token with the act grant, and it is served by either, by the size bound.

The route takes DecideBrandDesignInput and returns a card whose body is BrandDecision.

Request body#

The request body is DecideBrandDesignInput.

fieldtyperequirednote
brandidyes
pathtextyes
decisionone of accepted | declined | changedyes
valuejsonnothe tenant’s own value, when changed
whytextno

Response#

The route returns a card whose body is BrandDecision. Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true.

Headers#

headerrequiredmeaning
Scale-Scopeyesthe scope the call runs in: tenant/, then /brand/, then /strategy/
Scale-As-True-Onnothe date the facts must have been true on; defaults to now
Scale-As-Known-Onnothe date the facts must have been known on; defaults to now
Scale-Keynofor a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing

A caller needs the brand rung and a token with the act grant. The platform or the desktop app serves this route.

Example#

The example sends the smallest body that DecideBrandDesignInput allows. The build validates it against the schema of DecideBrandDesignInput.

Example
curl -X POST https://api.scaleintelligence.co/v1/act/decide_brand_design \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "brand": "…", "path": "…", "decision": "accepted" }'
import { client } from "@scale/sdk";
const answer = await client.act.decide_brand_design({
    "brand": "…",
    "path": "…",
    "decision": "accepted"
  });
// answer.body is a BrandDecision. answer.foot holds the basis, the scope and the time.
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/decide_brand_design",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "brand": "…",
      "path": "…",
      "decision": "accepted"
    }).json()
let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/decide_brand_design")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&DecideBrandDesignInput { /* the fields of the page */ }).send().await?.json().await?;

MCP tool#

The MCP tool si.act.decide_brand_design takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from ui://scale-intelligence/cards/BrandDecision. The tool’s page describes it.

POST /v1/act/decide_brand_design
Scale-Scope: …
Scale-As-True-On: …
Scale-As-Known-On: …
Scale-Key: …
content-type: application/json

{
  "brand": "…",
  "path": "…",
  "decision": "accepted"
}
Without a key, this page shows the request only. The request body is DecideBrandDesignInput, and the route returns a card whose body is BrandDecision.

Claims#

claimstateroute or tool
The platform serves the route /v1/act/decide_brand_design at contract 0476e35e6e275db5.target/v1/act/decide_brand_design