Prerequisites — Human Setup Before Phase 0

These are things that require human action (account creation, credentials, billing decisions) before agent work can begin. Check each off as completed.

AWS

• Dev account (or sub-account) provisioned
• IAM credentials with sufficient permissions for Pulumi (VPC, Lambda, EFS, DynamoDB, API Gateway, S3, CloudFront, Route 53, ACM, CloudWatch, WAF, Budgets)
• Credentials available as environment variables or AWS profile
• Budget alarm threshold: $50/mo for dev
• Region decided (suggested: us-east-1 for cheapest Lambda + API Gateway)

Pulumi

• Pulumi account created (or self-managed state backend chosen)
• pulumi CLI installed
• State backend configured (Pulumi Cloud free tier, or S3 bucket)

WorkOS

• WorkOS account created
• Google OAuth provider configured
• GitHub OAuth provider configured
• Apple OAuth provider configured
• API keys available as environment variables

DNS

• wikibot.io domain registered (or dev subdomain chosen)
• DNS hosted in Route 53 (or delegation configured)

Repositories

• wikibot-io private repo created (GitHub)
• Agent has push access (SSH key or token)

Local Dev Environment

• Docker + docker-compose running (for dev wiki)
• Dev wiki running at localhost:8180
• MCP server running at localhost:8190

Agent Container (packnplay)

Agents run inside packnplay containers with --dangerously-skip-permissions. packnplay mounts ~/.claude, handles credentials, creates worktrees, and preserves host paths.

• packnplay installed (brew install obra/tap/packnplay)
• packnplay configured (packnplay configure — enable git, ssh, gh, aws credentials)
• Dev wiki MCP accessible from container — configure MCP endpoint as http://host.docker.internal:8190/mcp (not localhost) since container localhost is the container itself
• Verify: packnplay run --aws-creds claude launches and can reach the wiki MCP
• Agent launch command documented: packnplay run --aws-creds --worktree=<phase> claude --dangerously-skip-permissions