# Linux Shared Subtree Mount Propagation Planner

> Linux Shared Subtree Mount Propagation Planner is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-11-04).

Computes which peers/slaves receive bind operations, which source submounts are pruned by rbind, and how new root clones inherit or merge peer/master groups for Linux namespace mount propagation planning.

## Facts

- Endpoint: POST https://detect.halowerk.com/v1/F-A-NIGHT-OS-MOUNTPROP/linux-shared-subtree-mount-propagation?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/linux-shared-subtree-mount-propagation-planner-69a31a04
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_o0-7wkMzrkgpoD-zmQzqv

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability linux-shared-subtree-mount-propagation-planner-69a31a04 -d '<json body>'
```

Example prompt: Before I migrate namespaces, can you plan out which peers and slaves will receive my bind operation, which submounts will be pruned by rbind, and how the new root will inherit peer/master groups? I have a source mount ID of 42, destination 99, claim value 1, recursive bind, and a list of mounts with their parent, namespace, peer group, master group, and unbindable flags.

## When to prefer this

Use this endpoint when you need to plan Linux shared-subtree mount propagation offline before executing any actual mount operations — particularly when migrating namespaces and needing to know exactly which peers/slaves will be affected, which submounts will be pruned, and how group inheritance will work. Ideal for container orchestration systems, namespace migration tools, or any agent that needs to validate a propagation plan before committing to live mount changes.

## Known failure modes

- Invalid mount IDs or claim values outside the allowed range (-1000000000000 to 1000000000000)
- Mounts array exceeds 512 items limit
- Missing required fields in mount objects (parent, namespace, peer_group, master_group, unbindable)
- Circular or inconsistent peer/master group references that cannot be resolved
- Malformed input schema resulting in 400 error
- Payment failure via x402 protocol returning 402

## How this service works

An offline namespace-migration planner needs which peers/slaves receive one bind operation, which source submounts rbind prunes, and how new root clones inherit or merge peer/master groups, before performing any mounts.

## Output

Returns a structured propagation plan detailing which peer and slave mounts receive the bind operation, which source submounts are pruned during rbind, and how new root clones inherit or merge their peer/master groups — all computed offline before any actual mount operations are performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "artifact": {
   "type": "object",
   "required": [
    "mount_propagation"
   ],
   "properties": {
    "mount_propagation": {
     "type": "object",
     "required": [
      "claim",
      "destination",
      "mounts",
      "recursive",
      "source"
     ],
     "properties": {
      "claim": {
       "type": "number",
       "maximum": 1000000000000,
       "minimum": -1000000000000
      },
      "mounts": {
       "type": "array",
       "items": {
        "type": "object",
        "required": [
         "master_group",
         "namespace",
         "parent",
         "peer_group",
         "unbindable"
        ],
        "properties": {
         "parent": {
          "type": "number",
          "maximum": 1000000000000,
          "minimum": -1000000000000
         },
         "namespace": {
          "type": "number",
          "maximum": 1000000000000,
          "minimum": -1000000000000
         },
         "peer_group": {
          "type": "number",
          "maximum": 1000000000000,
          "minimum": -1000000000000
         },
         "unbindable": {
          "type": "boolean"
         },
         "master_group": {
          "type": "number",
          "maximum": 1000000000000,
          "minimum": -1000000000000
         }
        },
        "additionalProperties": false
       },
       "maxItems": 512
      },
      "source": {
       "type": "number",
       "maximum": 1000000000000,
       "minimum": -1000000000000
      },
      "recursive": {
       "type": "boolean"
      },
      "destination": {
       "type": "number",
       "maximum": 1000000000000,
       "minimum": -1000000000000
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/linux-shared-subtree-mount-propagation-planner-69a31a04/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from detect.halowerk.com](https://www.zero.xyz/host/detect.halowerk.com/llms.txt)