Epic: Open-core architecture — OSS core + hosted paid layer

[OkiriGabriel]

Summary

Track the work to adopt an open-core model for Marketing Agent:

• Open (MIT, this repo): agents, tools, prompts, CLI, local JSON storage, BYOK credentials, local scheduler
• Closed (separate repo): web UI, auth, credential vault, managed scheduler, billing, teams/RBAC, analytics

Principles

1. Open the brain (LangGraph agents + tools); charge for the platform (hosting, teams, vault, reliability).
2. Do not gate core agent capabilities (complaints, posting, funnel, content generation) behind a paywall.
3. Paid layer should import/call the OSS core — not fork agent logic.

Proposed OSS boundary refactor

marketing-agent/                 # MIT (public)
├── storage/
│   ├── base.py                  # StorageProtocol
│   └── json_storage.py
├── credentials/
│   ├── base.py                  # CredentialsProtocol
│   └── env_credentials.py
├── core/
│   └── run.py                   # run_agent(message) → response
├── agents/, tools/, prompts/    # unchanged logic
├── main.py                      # CLI → core.run
└── scheduler.py                 # local cron → abstractions

marketing-agent-cloud/           # proprietary (private repo, future)
├── api/, web/, billing/
├── storage/postgres_storage.py
├── credentials/vault.py
└── workers/scheduler_worker.py

OSS prep issues (this repo)

• Extract StorageProtocol + JSON implementation
• Extract CredentialsProtocol + env implementation
• Add shared core/run.py entry point
• Refactor scheduler.py to use abstractions
• Document OSS vs hosted boundary in README

Paid layer roadmap (separate repo)

• Hosted web UI + chat API
• Credential vault + OAuth connect flows
• Managed scheduler worker (queue, retries, alerts)
• Stripe billing + usage metering
• Orgs, seats, RBAC, approval workflows
• Audit log + dashboards

Success criteria

• OSS users can still: clone → .env → python main.py with zero platform dependency
• Hosted product can swap Postgres + vault without duplicating agents/ or tools/

[OkiriGabriel]

Linked issues

OSS prep (this repo)

• Extract StorageProtocol and JSON storage implementation #2 Extract StorageProtocol and JSON storage
• Extract CredentialsProtocol and env-based credentials #3 Extract CredentialsProtocol and env credentials
• Add shared core entry point (core/run.py) #4 Add shared core entry point (core/run.py)
• Refactor scheduler.py to use storage and credentials abstractions #5 Refactor scheduler.py to use abstractions
• Document OSS vs hosted product boundary in README #9 Document OSS vs hosted boundary in README

Paid layer roadmap (separate repo)

• Roadmap: Hosted web UI and chat API (paid layer) #7 Hosted web UI and chat API
• Roadmap: Credential vault and OAuth social connect (paid layer) #6 Credential vault and OAuth social connect
• Roadmap: Managed scheduler worker with retries and alerts (paid layer) #11 Managed scheduler worker (retries + alerts)
• Roadmap: Stripe billing and usage metering (paid layer) #8 Stripe billing and usage metering
• Roadmap: Orgs, RBAC, and post approval workflows (paid layer) #10 Orgs, RBAC, and post approval workflows