Seed AgentOS architecture repository

[junaidahmed361]

Summary

• Updates the architecture to the v3 package: Hermes is the primary Phase 0 dogfooding interface, Campaign Kernel remains the system of record, and Hermes stays a thin MCP/REST client with no business logic
• Replaces open-source Wallet terminology with Resource Manager / Execution Policy / ResourceReservation; Wallet/Billing are now documented as Cloud-only modules
• Adds the user-amended architecture package under docs/agentos/v3 after reading CODING_AGENT_PROMPT.md first
• Adds thin Hermes adapter and minimal AgentOS MCP stdio server scaffold exposing create/list/status/approve/reject/artifacts/receipts/execution-policy tools
• Keeps the minimal dashboard as secondary views for campaign list, timeline, resources, pending approvals, artifacts, receipts, and credentials
• Adds Resource Manager tests, Hermes/MCP boundary tests, and updates dogfood examples/onboarding

Verification

• pytest -q
• PYTHONPATH=src python3 -m campaigns.mcp_server with tools/list and tools/call create_campaign
• PYTHONPATH=src python3 -m campaigns.cli dogfood-exec --goal 'Ship an evaluated backend API for immutable campaign receipts' --budget 25 --reserve 2.50 --constraint 'no payment wallet in the open-source core' --constraint 'provider choice stays hidden behind CLI drivers' --quality 'provider response artifact is captured' --quality 'immutable receipt is produced' --driver-command "printf 'PROVIDER_RESPONSE: resource-managed dogfood artifact accepted'" --json
• ./.venv/bin/python -m build

How to dogfood with Hermes

Configure Hermes to consume the AgentOS MCP server as a thin tool client:

hermes mcp add agentos --command "/Users/junaidahmed/Downloads/campaigns/.venv/bin/agentos-mcp"
hermes mcp test agentos
hermes mcp configure agentos

Then ask Hermes: "Create an AgentOS campaign to ship an evaluated backend API with a 5 resource ceiling, local/subscription providers preferred, no open-source payment wallet, and immutable receipts required." Hermes should call the MCP tool; Campaign Kernel owns state and business logic.

Local provider-auth note

• Codex and Claude CLI binaries are available, but this shell still receives 401 auth errors from the real provider CLIs. The Resource Manager + driver path is implemented and verified with a diagnostic command driver, but the actual provider response path still requires refreshing local Claude/Codex auth.