Long-Term Campaigns

Treat /Users/igor/work/long-term-campaigns as the durable source of truth. Agent sessions, workspaces, and VMs are disposable workers around it.

Campaign isolation

• Create one new subfolder for every new objective: <ticket-or-system>-<short-slug>.
• Reuse a folder only when the new request continues the same objective and completion criteria.
• Never place campaign state directly in the root and never mix unrelated campaigns.
• Inspect existing subfolders before creating one. Do not modify sibling campaigns.

Access from an agent session

• In a local Conductor workspace, read and update the folder directly.
• In a cloud workspace, use Conductor's Mac command bridge. Explain that the durable files exist only on the user's Mac.
• Never copy credentials, tokens, cookies, or raw secrets into a campaign folder, prompt, snapshot, log, or report.

Required tool and credential policy