The PA is a Digital Operator that runs inside Claude Code on your laptop: it runs work, keeps its own knowledge and delegates tasks, and learns your judgement as you correct it.

## What it does for you day to day

- Give it work to handle through one point of contact, with substantive tasks delegated to agents.
- Get prose drafted using your own voice guide and writing rules.
- Keep track of projects, tasks and progress between sessions.
- Ask it to install, configure and debug tools, services and your local environment.
- Run scheduled tasks through your laptop's scheduler.
- Expect reasoned push-back, followed by your decision when you override it.

## How it learns you

- It captures observations in staging as you work, treating corrections as its strongest training input.
- A journal records its reflections on how it is working.
- The librarian distils staged observations into the knowledge library, rewriting relevant documents and archiving the source notes.
- An autonomy envelope records approval by agent and task type, from full supervision to checks before committing or full approval.

## Knowledge it keeps

- The knowledge library lives in your local repository by default.
- Use `pa knowledge search`, `pa knowledge related` and `pa knowledge domain` to retrieve material.
- Its buckets cover your working interface, work management, delegation, knowledge, engineering discipline, content and voice, and platform tooling.
- A shared banned-tells baseline supplies writing rules that your own rules extend.

## Research

- Choose light research within the conversation, a normal research workflow or deep research.
- Research sessions are kept so you can list and inspect them later.
- Results can be a short answer, an article or structured output.
- Marking normal or deep research done adds its answer to your knowledge library.

## Keeping track of work

- Create work items with `pa work create`, with a category and priority.
- Statuses cover draft, planned, in progress, blocked, done and archived.
- Projects group documents and workstreams.
- Each project has a progress tracker with the newest entries first.
- `desk overview` and `desk today` give you read-only views of work and projects.
- A spawn log records agent dispatches when they happen.

## Delegating work to agents

- The dispatch-briefer analyses your request and writes an eight-section brief in fresh context, covering boundaries, outputs and completion criteria.
- Work can go to a single agent or a task group with a coordinator and workers, or stay in the current conversation.
- Parallel workers use separate git worktrees in the operator's own repositories; writes to downstream project repositories run sequentially.
- A coordinator hook enforces tool-use policy inside Claude Code.

## The roles it comes with

- `pa` is your point of contact for answers, delegation and tracking.
- `dispatch-briefer` prepares briefs for delegated work.
- `librarian` synthesises and indexes the knowledge library.
- `writer` reads your voice guide and banned-tells rules for each writing task.
- `tool-developer` builds shared internal command-line tools in Node.js.
- `system-admin` installs, configures and debugs your operating system, services and network.
- `agent-ops` manages the agent roster and approval settings, and drafts new roles.
- `agentic-workflow-designer` produces a ruled workflow design: a flowchart diagram, a Meta Agents Rule of Two mapping, and the operator rulings that settled its open questions.

## The workspace in your browser

- A local site runs on port 4200, opened with `pa workspace open`.
- Pages include home, projects, project details, tasks, notes, knowledge and a knowledge map.
- Other pages cover secrets, schedules, repositories, delegations, staging, your profile and onboarding.
- A viewer displays long notes and other content that runs beyond a few paragraphs.

## What it needs on your machine

- Node.js 24 or later.
- pnpm and git.
- The Claude Code CLI available from your terminal.
- Your Claude Code subscription login, with model calls using your account and no API keys required.

## What is not included in this version

- Solo use is the shipped setup; team lead and member modes are not implemented.
- The remote library is dormant in the default local mode.
- Specialised roles and the session-boot context injections used on the first-party estate are not part of the shipped package.
- Connections to services through MCP need your own Claude Code configuration.
- You supply your voice guide, personal writing rules, principles and profile knowledge; the starter content is structure and placeholders.
- Sharing repositories or memory across machines needs a remote and coordination that you set up.

## How to start

Open [docs/onboarding-solo.md](./onboarding-solo.md).
Follow it to set up your Digital Operator on your laptop.