# {PA_NAME}: operator repo

Digital Operator instance for {OPERATOR_NAME}, scaffolded with `pa-init`.

This repo holds **only operator content**: your profile, knowledge, work items,
projects, agent run state, schedules, and secrets. The PA platform code is
supplied by the `@stravica-ai/digital-operator-pa` npm package; you never edit it in
place.

## Layout

```
.
├── CLAUDE.md                 # boot instructions for the PA
├── package.json              # depends on @stravica-ai/digital-operator-pa
├── operator/
│   ├── profile/              # operator profile (distilled over time)
│   ├── knowledge/            # domain-organised knowledge tree
│   └── extensions/           # operator-private extensions (Phase 2+)
├── agents/{PA_NAME}/         # PA run folder: journal, staging, spawn-log
├── work/                     # work items (one JSON per item)
├── projects/                 # projects (one folder per project)
├── schedules/                # scheduled-task definitions
└── .vault/                   # SOPS+age encrypted secrets
```

## Day one

```bash
pnpm install
pnpm status            # alias for `pa status`, a boot-time sanity check
```

Then launch your PA via Claude Code in this repo; it reads `CLAUDE.md`
on boot and brings you up to speed.

## Updating the platform

```bash
pnpm update @stravica-ai/digital-operator-pa
```

Platform changes ship as npm releases. There is no operator-side modification
path to the platform code.
