Docs / Reference / act: keep ladder

act: keep ladder.

Its ordered rungs, each a predicate over the population, and the rung that qualifies; the rungs' predicates in full where they are not yet kept to the ladder with its version, not ready while a rung's predicate is not kept or does not compile

Figure 1POST /v1/act/keep_ladderspecified

The caller sends KeepLadderInput to /v1/act/keep_ladder. The platform returns a card whose body is Ladder.

POST/v1/act/keep_ladder

Keep a ladder. 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 KeepLadderInput and returns a card whose body is Ladder.

Request body#

The request body is KeepLadderInput.

field	type	required	note
`ladder`	Ladder	yes	the rungs carry their predicates by hash; a rung whose predicate is given in full under `predicates` is kept first
`predicates`	Predicate	no	the rungs’ predicates in full, kept by their hashes before the ladder

Response#

The route returns a card whose body is Ladder. 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 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 KeepLadderInput allows. The build validates it against the schema of KeepLadderInput.

Example

curl -X POST https://api.scaleintelligence.co/v1/act/keep_ladder \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "ladder": { "name": "…", "rungs": [], "qualifying_rung": "…" } }'

import { client } from "@scale/sdk";
const answer = await client.act.keep_ladder({
    "ladder": {
      "name": "…",
      "rungs": [],
      "qualifying_rung": "…"
    }
  });
// answer.body is a Ladder. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/keep_ladder",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "ladder": {
        "name": "…",
        "rungs": [],
        "qualifying_rung": "…"
      }
    }).json()

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

MCP tool#

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

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

{
  "ladder": {
    "name": "…",
    "rungs": [],
    "qualifying_rung": "…"
  }
}

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

Claims#

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