Programme milestones and priorities¶
First rule: nobody waits. Mission: legacy first. Each milestone is something a user can see, with exit criteria; scope cuts need Atul.
1. Projects, roles and milestones¶
| # | Project | Role in the programme | M1 | M2 | M3 |
|---|---|---|---|---|---|
| 1 | API / MM-Cron (ChatGPT, account A) | Upstream: production route on main; stgapi on branches; MM-Cron writes data |
Release 1: security batch (!162, !132) in production through the fast lane | Data you can trust: staging DB loaded from production; housekeeping and cleansing scripts; NAV/NIFTY gaps closed; read-only DB user; Adminer restricted | Consumer contract: /category flags fixed; PE's gate list answered (scheme identity, NAV semantics, freshness); admin write endpoints on stgapi |
| 2 | MWMC (ChatGPT, account A) | First customer of API; owns the production website; first proposal for every API need | MMCLONE ready: plan and owner notes in the sandbox, CI green, SSL | First production fix release: missing legacy features (factsheets), SEO basics | API requirements pack v1 handed to API; later: staging-website recovery inventory |
| 3 | MCRM (ChatGPT, account A) | Multi-vertical CRM; catalogue is one vertical; domain expert for categories, catalogue, non-MF products | Stream I: category tree approved (WP1) | Stream I: first catalogue family served (MF/Health/Term/Motor per MC-0) | Stream L: CRM Wave 0–1 design frozen (Party/Identity/KYC); Stream I: catalogue through the API |
| 4 | WPDev (ChatGPT, account C) | Next-generation website (live code, wpdev.moneymarche.com); domain expert for WordPress, front end, SEO | MMDEP way of working adopted (rules block, question issues, answers relay) | Next milestone of its existing plan | First stgapi feature tested before MWMC needs it |
| 5 | Portfolio Engine (executor to be chosen) | Research and portfolio engine; domain expert for MF analytics, factsheet figures, NAV quality | Knowledge audit done and design baseline restored | Objective-based selection (#321) merged; reports from code, not Excel | Gateway live on stgapi (3 endpoints) once API M2 loads staging data |
| 6 | MMDEP (Claude chat + Gemini controller) | Orchestrator: routes, unblocks, learns, reports | Phase 1–2 of DR-006: collector inside mmdep; hub holds items, achievements, milestones; panel synced |
Phase 3: mmdep control on Gemini (triage, routing, summary) |
Phase 4: web inbox (GitHub issues for MMDEP + collector output for other projects + panel features) |
2. Value, effort and dependencies (recalibrated 14 Oct, 11:30)¶
Scores are judgement, not measurement: Revenue = effect on leads and sales through the website, CRM or advisory; Saving = Atul's time, Claude quota or rework avoided; Risk = security, data or regulatory exposure removed; Effort = agent and person work. H / M / L. To be replaced by numbers once traffic, lead and conversion figures are available.
| ID | Milestone | Revenue | Saving | Risk | Effort | Depends on |
|---|---|---|---|---|---|---|
| A1 | API release 1: security batch (!162, !132) in production | L | M (proves the process) | H | L | Atul: SEC-2 secret rotation, production approval |
| W2a | MWMC SEO basics: page-specific canonicals and titles on product/AMC pages, product/AMC/category sitemaps, sitemap clean-up, breadcrumb | H (every fund and AMC page becomes indexable) | L | L | L–M | MMCLONE ready (done); support-release for production |
| W-RC | MWMC route crawler as an on-request job, run after each major release (test coverage + SEO) | M | H (replaces manual discovery) | L | L | !42 merged (done) |
| D1 | MMDEP phase 1–2: collector inside mmdep, hub, mmdep jobs |
L | H (cuts Atul's relay work and Claude quota; lets PE and others run jobs) | L | M | DR-6 approval |
| A3a | API /category returns stored status and show-in-menu flags |
M (category pages and sitemap) | L | L | L | — (pulled forward from A3) |
| C1 | MCRM category tree approved (Stream I) | M | M (one tree for site, API, CRM) | L | L–M | A3a for implementation; proposal can start now |
| P1 | PE knowledge audit and design baseline | L now, H later (advisory product) | H (stops wasted PE work) | L | L | Atul: 15 minutes to tick the concept list |
| A2 | API data trust: staging DB loaded from production, housekeeping scripts, NAV/NIFTY gaps, read-only DB user, Adminer restricted | M (correct fund data builds trust) | M | H | H | Ajay or Atul: DB access steps (support-release) |
| W2b | MWMC legacy features: factsheets and other missing pages | H | L | L | M–H | A2 (data), W2a |
| D2 | MMDEP Gemini controller (mmdep control) |
L | H | L | M | D1; Gemini key decision (paid project) |
| C2 | MCRM first catalogue family served (MF/Health/Term/Motor) | H (insurance and MF product pages) | M | L | H | C1, A3 contract |
| P2–P3 | PE objective selection, reports from code, Gateway on stgapi | H (portfolio review service) | M | L | M–H | P1; A2 for stgapi data |
| WD1–3 | WPDev adoption and next-generation site | M (long term) | L | L | M | A2 for stgapi features |
| CL | MCRM Stream L: CRM Wave 0–1 design | H long term (conversion, retention) | M | M (KYC) | H | C1; one third of MCRM effort |
| D3 | MMDEP web inbox | L | M | L | M | D2 |
3. Recalibrated order¶
Highest value for lowest effort first, never ahead of an unmet dependency:
- A1 release 1 — in flight; removes a security exposure.
- W2a SEO basics — highest revenue per unit of effort; no blocking dependency.
- W-RC route crawler (on request and after major releases) — keeps W2a honest and feeds test coverage; dependency just cleared.
- D1 MMDEP phase 1–2 — the effort-saving engine for every other project.
- A3a
/categoryflags — small fix that unlocks C1 and category sitemaps. - C1 category tree — in parallel with A3a.
- P1 PE knowledge audit — cheap, protects the biggest long-term revenue line.
- A2 data trust — heavy, and needs DB access steps; start the access request now so it is not on the critical path later.
- W2b legacy features — after A2 provides the data.
- D2 Gemini controller.
- C2, P2–P3, CL, WD1–3, D3 — the next-generation wave, gated by A2/A3.
Critical path: A2 (staging data and data hygiene) gates W2b, C2, P3 and WPDev's stgapi work. Its person steps (DB access, read-only user) should be raised this week even though A2 itself is eighth.
Person steps that gate milestones: SEC-2 rotation and production approval (A1); SSL #26 (MMCLONE); DB access for A2 (Ajay/Atul); DR-6 approval (D1); Gemini paid key (D2); 15 minutes on the PE concept list (P1).
4. Claude's role per project¶
| Project | Claude's role |
|---|---|
| MMDEP | Architect and developer (codes in the repo, runs on the desktop), programme manager |
| API / MM-Cron | Reviewer of security and data MRs; release manager for release 1 |
| MWMC | Reviewer of plan and API requirement packs |
| MCRM | Two-stream check; reviewer of category tree and catalogue contract |
| WPDev | Study (iterative), reviewer when asked |
| PE | Knowledge audit; weekly milestone check |
5. Cross-project help (who unblocks whom)¶
- MWMC → API: first proposal for every API need.
- WPDev, MCRM, PE → MWMC: answers and next-level proposals in their domains (
ask-mwmc/ask-<project>issues). - WPDev, MCRM, PE → API: stgapi requirements, and testing features before MWMC needs them.
- MM-Cron → everyone: staging data (API M2) is the key unblocker for all stgapi testing.