Docs / Reference / act: move strategy

act: move strategy.

A strategy, the place to move it to and the reason (`StrategyMoveInput`): drafted, simulated, rolled out in part, running, paused, ended to the `Strategy` in its new place, with who moved it

Figure 1POST /v1/act/move_strategyspecified

The caller sends StrategyMoveInput to /v1/act/move_strategy. The platform returns a card whose body is Strategy.

POST/v1/act/move_strategy

Move a strategy. The call needs the strategy rung under a token with the act grant, and it is served by the platform.

The route takes StrategyMoveInput and returns a card whose body is Strategy.

Request body#

The request body is StrategyMoveInput.

field	type	required
`strategy`	`id`	yes
`to`	`one of drafted \| simulated \| rolled out in part \| running \| paused \| ended`	yes
`reason`	`text`	yes

Response#

The route returns a card whose body is Strategy. 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#

header	required	meaning
`Scale-Scope`	yes	the scope the call runs in: tenant/, then /brand/, then /strategy/
`Scale-As-True-On`	no	the date the facts must have been true on; defaults to now
`Scale-As-Known-On`	no	the date the facts must have been known on; defaults to now
`Scale-Key`	no	for 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 strategy rung and a token with the act grant. The platform serves this route.

Example#

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

Example

curl -X POST https://api.scaleintelligence.co/v1/act/move_strategy \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "strategy": "…", "to": "drafted", "reason": "…" }'

import { client } from "@scale/sdk";
const answer = await client.act.move_strategy({
    "strategy": "…",
    "to": "drafted",
    "reason": "…"
  });
// answer.body is a Strategy. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/move_strategy",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "strategy": "…",
      "to": "drafted",
      "reason": "…"
    }).json()

let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/move_strategy")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&StrategyMoveInput { /* the fields of the page */ }).send().await?.json().await?;

MCP tool#

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

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

{
  "strategy": "…",
  "to": "drafted",
  "reason": "…"
}

Without a key, this page shows the request only. The request body is StrategyMoveInput, and the route returns a card whose body is Strategy.

Claims#

claim	state	route or tool
The platform serves the route /v1/act/move_strategy at contract 0476e35e6e275db5.	target	`/v1/act/move_strategy`