Skip to content

distribution.status

Whether a machine that has never seen this project can install it right now with the advertised one-line command, and when it cannot, which link in the chain is missing and what changes it. Derived from the distribution model and the release records alone: it reaches no network, so it is as fast as any other local query and answers offline. The served bytes are proved by the release pipeline's smoke phase, not guessed at here.

Whether a machine that has never seen this project can install it right now with the advertised one-line command, and when it cannot, which link in the chain is missing and what changes it. Derived from the distribution model and the release records alone: it reaches no network, so it is as fast as any other local query and answers offline. The served bytes are proved by the release pipeline's smoke phase, not guessed at here.

Exposure

Where this one definition is reachable. Absence is explicit: a surface not listed does not carry it.

surfaceas
MCPtool majordomus_install_status
HTTPGET /api/v1/distribution/status operationId distribution.status
command linemajordomus distribution status

Schemas

The canonical input and output, from the Rust types; the MCP tool schema and the OpenAPI parameters and responses are derived from these.

input · Empty

No input.

No properties: the capability takes no input.

JSON Schema 
{
  "additionalProperties": false,
  "description": "No input.",
  "title": "Empty",
  "type": "object"
}

output · InstallabilityReport

Whether the advertised one-line installation works right now, and if not, what is missing. This answers the operator's actual question — *can a machine that has never seen this project install it with the published command?* — from local state alone. It performs no network access: a repository can be offline and this still answers, because everything it needs is the distribution model and the release records the repository itself carries. What it cannot see it reports as `unknown` rather than guessing; the public half of the question is answered by the release workflow's smoke phase, which installs from the published URL on every native runner and is the only thing that proves the public path.

propertytyperequireddescription
checks array yes Every check, in the order they are worth reading.
install_command string yes The command a person would run, whether or not it currently works.
installable boolean yes True when every check holds: a stable release is recorded and complete.
installer_url string yes Where the installer is served.
latest_url string yes Where the stable pointer is served.
local_version string yes The version this tree would release.
published_artifacts integer yes How many of them the stable release actually publishes.
required_targets integer yes How many targets a release must publish for that release to be complete.
stable_tag string | null no The tag an unpinned installation resolves to, when a stable release is recorded.
summary string yes One line for a person: what the state is, in the project's own terms.
JSON Schema 
{
  "$defs": {
    "CheckState": {
      "description": "The state of one check in the installability report. Three states and no more: a check\neither holds, does not, or could not be made from what this process can see.",
      "oneOf": [
        {
          "const": "ok",
          "description": "The check holds.",
          "type": "string"
        },
        {
          "const": "failed",
          "description": "The check does not hold, and the public installation is affected.",
          "type": "string"
        },
        {
          "const": "unknown",
          "description": "The check could not be made here; it says nothing either way.",
          "type": "string"
        }
      ]
    },
    "InstallCheck": {
      "description": "One check: what was asked, what was seen, and — when it does not hold — why, and the\ncommand that changes it. The `cause` and `next` fields exist so that a report is\nactionable without a second document; a check that fails without naming its remedy is\na diagnostic nobody can act on.",
      "properties": {
        "cause": {
          "description": "Why it does not hold. Absent when it does.",
          "type": [
            "string",
            "null"
          ]
        },
        "id": {
          "description": "A short stable name: `model`, `version`, `targets`, `release`, `artifacts`, `metadata`.",
          "type": "string"
        },
        "next": {
          "description": "The command or action that would change it. Absent when there is nothing to do.",
          "type": [
            "string",
            "null"
          ]
        },
        "observed": {
          "description": "What was observed, in one line.",
          "type": "string"
        },
        "state": {
          "$ref": "#/$defs/CheckState",
          "description": "Whether it holds."
        }
      },
      "required": [
        "id",
        "state",
        "observed"
      ],
      "type": "object"
    }
  },
  "description": "Whether the advertised one-line installation works right now, and if not, what is missing.\n\nThis answers the operator's actual question — *can a machine that has never seen this\nproject install it with the published command?* — from local state alone. It performs no\nnetwork access: a repository can be offline and this still answers, because everything it\nneeds is the distribution model and the release records the repository itself carries.\nWhat it cannot see it reports as `unknown` rather than guessing; the public half of the\nquestion is answered by the release workflow's smoke phase, which installs from the\npublished URL on every native runner and is the only thing that proves the public path.",
  "properties": {
    "checks": {
      "description": "Every check, in the order they are worth reading.",
      "items": {
        "$ref": "#/$defs/InstallCheck"
      },
      "type": "array"
    },
    "install_command": {
      "description": "The command a person would run, whether or not it currently works.",
      "type": "string"
    },
    "installable": {
      "description": "True when every check holds: a stable release is recorded and complete.",
      "type": "boolean"
    },
    "installer_url": {
      "description": "Where the installer is served.",
      "type": "string"
    },
    "latest_url": {
      "description": "Where the stable pointer is served.",
      "type": "string"
    },
    "local_version": {
      "description": "The version this tree would release.",
      "type": "string"
    },
    "published_artifacts": {
      "description": "How many of them the stable release actually publishes.",
      "format": "uint",
      "minimum": 0,
      "type": "integer"
    },
    "required_targets": {
      "description": "How many targets a release must publish for that release to be complete.",
      "format": "uint",
      "minimum": 0,
      "type": "integer"
    },
    "stable_tag": {
      "description": "The tag an unpinned installation resolves to, when a stable release is recorded.",
      "type": [
        "string",
        "null"
      ]
    },
    "summary": {
      "description": "One line for a person: what the state is, in the project's own terms.",
      "type": "string"
    }
  },
  "required": [
    "installable",
    "summary",
    "local_version",
    "required_targets",
    "published_artifacts",
    "install_command",
    "installer_url",
    "latest_url",
    "checks"
  ],
  "title": "InstallabilityReport",
  "type": "object"
}

Policies

benchmark
required — a target on every transport the exposure declares; the cases are the input type's
cache
disabled — every call runs the handler

Benchmark targets

Derived from the registry for this repository: one requirement per transport, and the cases the input type provides. The whole matrix is on the benchmarks page.

transportstatecasestargets
directcovered1default
mcpcovered1default
httpcovered1default