orrery/manifest-bind

Bind caller-supplied file digests into a stable manifest_digest receipt.

/resolve?name=orrery/manifest-bind

Use this when

You have path/sha256/size rows and need a sealed manifest digest
You want admitted/excluded counts without Orrery opening a repo

Not for

Reading the caller's repository from disk
Mutating or writing files
Policy evaluation (use manifest-preflight)

Inputs / Outputs

Inputs

Name	Type	Notes
`files` required	array	[{path, sha256, size}]

Outputs

Name	Type	Notes
`manifest_digest`	string	—
`admitted_count`	integer	—
`excluded_count`	integer	—
`envelope`	signed-envelope	—

Example

{
  "method": "tools/call",
  "params": {
    "name": "bind",
    "arguments": {
      "files": []
    }
  }
}

Tools

bind Bind a caller-supplied file list into a stable manifest_digest with admitted and excluded counts · schema

{
  "type": "object",
  "properties": {
    "files": {
      "type": "array",
      "maxItems": 10000,
      "items": {
        "type": "object",
        "properties": {
          "path": {
            "type": "string",
            "minLength": 1,
            "maxLength": 512
          },
          "sha256": {
            "type": "string",
            "minLength": 64,
            "maxLength": 64
          },
          "size": {
            "type": "integer",
            "minimum": 0
          }
        },
        "required": [
          "path",
          "sha256",
          "size"
        ],
        "additionalProperties": false
      }
    }
  },
  "required": [
    "files"
  ],
  "additionalProperties": false
}

In constellations

orrery/authorized-content-patchGoverned content edit path: readiness → write-authority → patch-capture → sealed composite (never applies patches)↗orrery/content-readinessAssess a caller content bundle: manifest, structure, bounded links → sealed disposition↗orrery/ship-checkSeal ship-check evidence: metadata release+UTC or content-bundle readiness stages↗