Development Plan

Development Plan

Agile, milestone-based. Full detail (per-commit breakdown, dependency matrix, traps): .cache/commit-plan.md (v5).

Process

• Branches: main ← staging ← feature/<group>. One PR per feature group into staging. Milestone PR staging → main, tagged.
• Issues: one GitHub issue per feature group, tracked on project board https://github.com/users/SuperElectron/projects/4/views/1, closed by its PR.
• Gate per PR: cargo fmt --check && cargo clippy -- -D warnings && cargo test green.
• Review: code-reviewer pass on every PR before merge (correctness + design rules).
• Design rules: no code comments; files <400 lines (500 cap); I/O behind traits; thiserror per module; conventional commits.
• Never: direct commits to staging/main; red merges; group started before prerequisites merged.

Milestones (sprints)

Milestone	Tag	Feature groups	Outcome
M1 Foundation	v0.1.0	FG-01 bootstrap, FG-02 domain, FG-03 config, FG-04 db, FG-05 llm, FG-06 memory	binary boots, migrations run, LLM + Mem0 reachable
M2 Connectors	v0.2.0	FG-07 api-clients (Apollo/Tavily), FG-08 connectors-email (slack, gmail, sendgrid, hubspot, health/metrics), FG-09 connector-linkedin (HeyReach)	all outbound channels + data clients tested
M3 Workflows	v0.3.0	FG-10 sync, FG-11 discovery, FG-12 research, FG-13 accounts, FG-14 generation, FG-15 analysis	full business logic, dry-run capable
M4 Runtime	v0.4.0	FG-16 runtime-core, FG-17 jobs-sync, FG-18 jobs-outreach, FG-19 jobs-inbound, FG-20 reporting	system fully operational locally
M5 Release	v1.0.0	FG-21 integration-tests, FG-22 seed-data (Austin TX), FG-23 docs+assets+agents-skills, FG-24 release	shippable

~90 commits total across 24 groups.

Key ordering constraints (why groups can't shuffle)

• health/metrics need gmail connector → live in FG-08, not foundation
• job error-notify needs slack → runtime (FG-16) after connectors (FG-08)
• webhook router ships FG-16; handlers register in FG-19 (registry pattern)
• tasks::execute needs generation → FG-15 after FG-14
• signal_detection has widest fan-out → last job commit
• reply monitoring = Gmail API polling primitives land with gmail connector (c37)

Backlog (post-v1)

• jentic-one credential broker transport + OpenClaw pairing
• Mem0 on shared Postgres pgvector; local embedding model on DGX

See Home, Architecture.