pd who-owns <path>
Inspect current file ownership and claims for one path.
Run pd who-owns <path> like this
pd who-owns src/app.tsCommand contract
pd who-owns <path>
/docs/cli/who-owns
Governance, Scope, Semantics, And Signal Layers
Daemon client with direct-mode fallback where supported
cli/commands/advisor.ts, cli/commands/guard.ts, cli/commands/harbors.ts, cli/commands/wallet.ts, cli/commands/bond.ts, cli/commands/semantic.ts, cli/commands/ideas.ts, cli/commands/roadmap.ts, cli/commands/feedback.ts, cli/commands/pheromone.ts
none
human display with command-specific state changes
generated API spec from the source-backed catalog
This clip shows the daemon health check, command discovery, and message-loop patterns that recur across the CLI reference. Here it grounds the pd who-owns <path> reference: daemon health, discovery, and message-loop patterns these pages keep pointing back to.
Common ways this command shows up in practice
pd who-owns <path> belongs to Governance, Scope, Semantics, And Signal Layers. Coordinate scarce surfaces, protected work areas, budgets, bonds, roadmap memory, and low-friction signals.
Daemon client with direct-mode fallback where supported. Validate live behavior from the daemon and handler source when changing this command.
Use this page as the stable public contract for pd who-owns <path>; aliases resolve to the same contract.
Examples
Run pd who-owns <path> from a coordinated checkout
pd who-owns src/app.ts
Prints the changed record or lookup result; use --json when you need the exact machine-readable shape.
Find this command from the full CLI reference
pd help who-ownsopen /docs/cli/who-owns
The help topic and docs route both describe pd who-owns <path>, including aliases, flags, and source provenance.