Polpo Projects

Treat the checked-out project and the installed CLI as authoritative. Do not recreate legacy .polpo/polpo.json or .polpo/agents.json layouts except when explicitly migrating them.

Workflow

1. Inspect the repository, .polpo/, package.json, and the installed polpo CLI version.
2. Preserve an existing linked project. Create or link only when the user requests it or no project exists.
3. Author resources in layout v2: project metadata, one directory per agent, project Loop definitions, teams, skills, and the skill lockfile.
4. Validate locally before deployment. Resolve unknown references and packaging failures rather than relying on a second identical deploy.
5. Deploy through the CLI or supported workflow. Never place provider secrets in project files.
6. Report the project, resources changed, validation performed, and whether anything still requires Cloud provisioning or rollout.

Project Boundaries