# mcp.policy.SocketProvenance

- **Module:** mcp.policy
- **Package:** tmux-mcp
- **Language:** Rust
- **Kind:** enum
- **Source:** https://github.com/libtmux/libtmux-rs/blob/f0e37052c232636b61d095817046e6bfc8f2ca40/crates/tmux-mcp/src/policy.rs#L273
- **Page:** https://libtmux.org/en/rs/latest/mcp/reference/mcp-policy-socketprovenance/

What startup can honestly claim about the selected tmux daemon.

## Members

- `DedicatedMinimal` (constant): A product socket this process can create with minimal configuration.
- `DedicatedExisting` (constant): The product socket already existed, so its configuration is unknown.
- `OperatorSelected` (constant): The operator selected a socket, whose daemon configuration is unknown.
- `OperatorSelectedAbsent` (constant): The operator selected a socket where no daemon answered at startup.
- `UserConfigured` (constant): The operator selected an explicit tmux configuration for an absent daemon.
- `UserConfiguredExisting` (constant): A daemon already answered, so an explicit config was not its provenance.
- `Unknown` (constant): A programmatic builder did not provide provenance.
- `defaults_to_teardown` (method): Whether absent toolset configuration may include teardown.