Scale Intelligence■ Docs
Docs / Reference / act: make brand design system

act: make brand design system.

The brand, and the site when it is not the brand row's own to the brand's design system as the next version of its name: every colour, face, size, step, radius, shadow and the logo, each measured, inferred by a named rule or never measured, with the artefacts it was read from and the gaps; and the same values in…

Figure 1POST /v1/act/make_brand_design_systemspecified
CALLERyour app or an agentholds the keyAPI GATEWAY/v1/act/make_brand_desig…4 headersCORE: ACTrung brandgrant actRECORDreads or writesCARD, 200body BrandDesignSystemThe input is MakeBrandDesignSystemInput. Every response carries the contract's hash.flows forwardthe result
The caller sends MakeBrandDesignSystemInput to /v1/act/make_brand_design_system. The platform returns a card whose body is BrandDesignSystem.
POST/v1/act/make_brand_design_system

Make a brand’s design system from its pages. The call needs the brand rung under a token with the act grant, and it is served by the platform.

The route takes MakeBrandDesignSystemInput and returns a card whose body is BrandDesignSystem.

Request body#

The request body is MakeBrandDesignSystemInput.

fieldtyperequirednote
brandidyes
websiteaddressnodefaults to the brand row’s own

Response#

The route returns a card whose body is BrandDesignSystem. 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 serves this route.

Example#

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

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

MCP tool#

The MCP tool si.act.make_brand_design_system 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/BrandDesignSystem. The tool’s page describes it.

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

{
  "brand": "…"
}
Without a key, this page shows the request only. The request body is MakeBrandDesignSystemInput, and the route returns a card whose body is BrandDesignSystem.

Claims#

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