Start here

One canonical first run.

Install Port Daddy, verify daemon truth, open the app, and create one named session before branching into lifecycle, role, or reference docs.

Whitepaper Get started

Common jobs

Pick the question, then the surface.

Install Understand primitives Coordinate work Choose an architecture Integrate SDK/MCP Reference

System map

Model, layout, app, agent, reference.

Read this path when the new Primitives and Reference Architectures pages need to line up with the Mac app, Skill + MCP, and exact reference surfaces.

Primitives

Name the small runtime facts: identity, ownership, messaging, recovery, verification, and human control.

Reference Architectures

Arrange those primitives into local control planes, automation loops, and delegation surfaces.

Mac Preview

See FleetBar and Fleet Control Center as the human inspection surface for the same state.

Skill + MCP

Install the agent operating guide and expose the same coordination primitives through MCP tools.

Reference

Jump from the model to exact CLI commands, SDK calls, MCP tools, HTTP routes, and capability scopes.

Reference

Jump straight to the exact interface.

When you know what you want — a command, an SDK method, an MCP tool, or an HTTP endpoint.

CLI reference

40+ commands for sessions, locks, messaging, harbors, and fleet.

SDK reference

TypeScript SDK for embedding Port Daddy in your own tools.

MCP tools

Tools an MCP agent (Claude, Cursor, Windsurf) can call directly.

REST API

HTTP endpoints for direct integration without a SDK.

Decisions

ADRs — architectural decisions, why they were made, and what was traded off.

By role

Reader lanes

First-timers, CLI operators, SDK/MCP builders, Mac operators, leads, and security owners have different first questions.

Lifecycle

Move by stage.

These stages route the main developer lifecycle before the reader dives into exact commands or API calls.

Overview

Sections

Deeper docs families.

Use these when the job lane is clear and you need the system model, practices, tutorials, architectures, or exact interfaces.

Get Started Concepts Best Practices Tutorials Reference Architectures Reference

Main site

The rest of the website stays live.

Use the docs shell for deep reading, then jump back to the Mac preview, runnable examples, agent templates, Skill + MCP, or agent catalog when the broader public site is the right place.

Mac Preview Runnable examples Templates Skill + MCP Agents

CLI/pd guard <command>

CLI command · v3.30.6

pd guard <command>

Install, enable, disable, status-check, or enforce session plus file-claim discipline.

Syntax

Run pd guard <command> like this

pd guard status

API spec

Command contract

Canonical command

pd guard <command>

Reference route

/docs/cli/guard

Reference group

Governance, Scope, Semantics, And Signal Layers

Runtime path

daemon-backed CLI command

Source

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

Aliases

none

Output mode

human display with command-specific state changes

Page type

generated API spec from the source-backed catalog

See the command surfaces this reference keeps in play

Usage patterns

Common ways this command shows up in practice

pd guard <command> belongs to Governance, Scope, Semantics, And Signal Layers. Coordinate scarce surfaces, protected work areas, budgets, bonds, roadmap memory, and low-friction signals.

daemon-backed CLI command. Validate live behavior from the daemon and handler source when changing this command.

Use this page as the stable public contract for pd guard <command>; aliases resolve to the same contract.

Flags

Options that change command behavior

status

Print the current status for this command family.

check

check is accepted by this command family; see the handler source for command-specific validation and side effects.

enable

enable is accepted by this command family; see the handler source for command-specific validation and side effects.

disable

disable is accepted by this command family; see the handler source for command-specific validation and side effects.

install

Install the local integration or guard.

--staged

Check only staged files.

--mode

Select advisory or enforcement behavior.

Examples

Example 01

Run pd guard <command> from a coordinated checkout

CLI

pd guard status

Output

Runs the pd guard <command> command family and prints the resulting Port Daddy state, ids, or readiness/error details.

Example 02

Find this command from the full CLI reference

CLI

pd help guard
open /docs/cli/guard

Output

The help topic and docs route both describe pd guard <command>, including aliases, flags, and source provenance.

Nearby command surfaces

pd advise [files...]pd add [path...]pd lock <name>pd unlock <name>pd locks

All commands SDK reference