Skip to content

Decisions log

Date Item Decision (Atul) Effect
2026-10-12 D3 The PM sorts the API and MM-Cron blocked list; Ajay gets only what needs him Ajay's doc cut to 4 questions plus a runbook template
2026-10-12 D5 Daily Claude review session, once the collector works Collector first (no Claude credits); scheduled session after
2026-10-12 D8 Claude commits its own documents (docs/ only) straight to main; code and specs still need approval No more PRs for PM documents. This log is the first such commit
2026-10-12 D9 Google Docs connector turned on Ajay's doc edited in place
2026-10-12 a1 Gemini billing active (reserve project, key unused); free key stays on the laptop All projects on paid terms (A-36)
2026-10-12 a4 One onboarding pack for all ChatGPT agents after the framework decisions PE PR #321 note goes into the pack
2026-10-12 D2 One ChatGPT project per role Onboarding pack
2026-10-12 D4 Work-package MRs adopted; per-project policy line can vary by phase Shared AGENTS.md section
2026-10-12 D6 No extra account: 3 schedule slots per account, 9 across three accounts Chrome profile per account
2026-10-12 D7 Triage re-enabled after tests, retired once the collector covers it —
2026-10-12 D1 Write test run: unattended ChatGPT writes blocked (A-37) D13 opened
2026-10-12 Collector Running hourly on the laptop; 236 open MRs across 10 repos at 15:45 D11, D12 opened
2026-10-12 Focus Portfolio Engine, MCRM and WPDev slow down; maximum focus on MWMC and API/MM-Cron. WPDev and MCRM return later only to support those two Panel: paused groups closed; critical path only blocks
2026-10-12 Accounts Account A runs three schedules: MWMC, API/MM-Cron, MMDEP. Old API project (account B) and old PM chat kept as history Onboarding pack (Claude doc)
2026-10-12 Top 5 Each agent keeps a pinned "Top 5" issue: the five issues that unblock most of its pipeline; works only on those Shared rules
2026-10-12 CI use Agents never trigger CI; they file support-test or support-release issues; the collector queues them for the terminal agent Collector support queue
2026-10-12 Streams Atul's actions kept in three streams: online; browser and laptop; terminal and servers Panel groups

| 2026-10-13 | Plan first | API/MM-Cron agent consolidates all work into one plan (API !167, phases A staging, B data integrity, C security, D consumers) with PE, WPDev, MCRM and MWMC consumer appendices; no new issues until approved | Panel Plan-0 to Plan-3 | | 2026-10-13 | Data architecture | The target database follows the API architecture. MCRM's catalogue JSONs (MCRM research/catalogue/2026-10/: extended category tree, 12-entity model for motor, term, health) are the structure for the proposed database for non-MF products; the MF structure is standardised onto it once the API agent is operational (Atul). Current state per API !153, !157, !166; per-table writers to confirm with Ajay. Atul's earlier verbal explanation was not retained by the old agent | Plan !167 "Data architecture" section | | 2026-10-13 | MWMC role | MWMC is the API's main consumer: reviews website-side calls and behaviour only, never API/MM-Cron internals; questions via the relay | MWMC setup 13 Oct |

| 2026-10-13 | Plan-0 to Plan-3 | API/MM-Cron plan !167 approved as written; C's security fixes run alongside A; the agent checks each documentation MR for unique evidence before closing; read-only database access: ask Ajay whether a user exists, otherwise create it over SSH; evaluate the Adminer install | API agent prompt 13 Oct | | 2026-10-13 | Docs merge | Documentation-only MRs are merged directly by the agent after its own check; superseded docs MRs closed (API-1) | Agent rules §1 | | 2026-10-13 | Owner notes | Agents record what Atul or Ajay tell them in docs/notes/owner-notes.md the same session | Agent rules §10 | | 2026-10-13 | CI route (D17) | GitLab runner on Atul's laptop (Docker), not GitHub Actions | Runner setup item | | 2026-10-13 | Attended sessions (W3, D15) | No fixed times; when Atul has been inactive for long, the collector alerts him to open a session. Claude sends commands to agent chats via Chrome only on a go-ahead given in the Claude chat for that round | Collector alert (to build) | | 2026-10-13 | GitLab identity (W2) | Atul's own account (or Ajay's) for API work; the old API agent's account is retired; group membership to be rationalised for CI minutes | — | | 2026-10-13 | Factsheet data (owner, r6) | Fund data other than NAV comes from monthly AMC factsheets; Ajay wrote parsers for 10 AMCs, few work today; about 40 more AMCs to plan | Plan !167 MM-Cron section | | 2026-10-13 | PE gateway (owner, r4) | Portfolio Engine's data gateway (fills API gaps, client-supplied data) is on hold | — | | 2026-10-13 | Mission (MWMC, API/MM-Cron) | First job: build knowledge, fix bugs, complete missing legacy features (e.g. factsheet pulling, then showing that data on the website) so users keep using the site and SEO/ad traffic is not lost. Innovation belongs to WPDev, MCRM and PE | Agent rules §00 | | 2026-10-13 | Commands | PROCEED = act without waiting (Atul not reading); CONTINUE = Atul has a few minutes. Questions always go to question-atul issues; the collector feeds them to the panel; answers come back in docs/relay/answers.md | Agent rules §6 | | 2026-10-13 | One project per agent | Agents ignore instructions addressed to another project; cross-project needs go through repos and MMDEP | Agent rules §11 | | 2026-10-13 | Security fast lane (sec2) | Security fixes: MR with tests, runner tests, review, staging/MMCLONE check, weekly batched production release approved by Atul in one answer; rotation by script | Agent rules §12 | | 2026-10-13 | Runner | Laptop GitLab runner (Docker) online for group moneymarche; agents may start one pipeline at a time for MRs with a support-test issue; releases stay with a person | Agent rules §5 | | 2026-10-13 | MCRM (MC-0, MC-1) | MCRM onboarded in account A (third schedule slot; MMDEP assistant not needed). Plan PR #102 approved: API database is the catalogue SoR; MCRM owns Catalogue Manager design and CRM as separate modules; release one MF, Health, Term, Motor | Agent rules §0 register | | 2026-10-13 | CI quota rule withdrawn | The no-CI rule (GitLab minutes exhausted) is withdrawn for the moneymarche group: jobs run only on the laptop group runner (tags laptop, docker; no GitLab minutes); deploy/release stay manual; the CI-blocking test/flag is disabled for now and reviewed after the runner trial | answers relay; rules §5 | | 2026-10-13 | CI live | API !169 and MM-Cron !82 merged: automatic tagged test jobs on the laptop runner, MM_CI_MODE gate removed, deploy/data-load jobs manual. Security tests for API !132 and !162 passed (pipelines 2943446146, 2943448559). Full API suite: 2 failures, 14 errors, not yet rerun | SEC-1 in panel | | 2026-10-14 | GOV-1 governance MR clean-up | MMDEP governance repo: 7 MRs merged as reference (!28, !44, !45, !51, !52, !53, and !43 after its accidental .gitlab-ci.yml deletion was reverted), 23 closed as superseded with comments, issue #32 closed. No governance MRs left open | governance issue #32 | | 2026-10-14 | Scheduler hours widened | ChatGPT scheduled runs (3 agents: API/MM-Cron, MWMC, MCRM) work 07:00–23:00 IST instead of 09:00–21:00 | rules §7; answers relay | | 2026-10-14 | Staging website vs stgapi | Staging website = legacy code with unreleased earlier work, to be preserved; it does not use stgapi. stgapi = new API development, currently unused (its outage went unreported). Lower priority than production | owner record §15 | | 2026-10-14 | MW-U | MWMC loop broken: public-source route inventory, MR clean-up to 5, CI on laptop runner, M2 started (#29) | answers relay | | 2026-10-15 | Scheduled ChatGPT runs: read yes, write no | First test (MMDEP #12) was an attended run. The real scheduled run (16:11 IST) read GitHub, GitLab and the control snapshot, but its comment writes were blocked by connector safety checks. No Gmail tool on account A. Next: e-mail bridge (task notification → Apps Script → MMDEP issue) | rules §7; owner notes 33, 38 | | 2026-10-15 | Scheduled runs save reports as files | WPDev's scheduled run committed a report file to GitLab (branch reports/wpdev-daily-review); MMDEP assistant's scheduled comments were blocked. Rule: scheduled runs commit one report file per run to a reports branch (MMDEP branch reports, path reports//YYYY-MM-DD-HHMM.md); comments only in attended runs | rules §7 | | 2026-10-15 | Scheduled runs cannot write (correction) | Atul's tests of all agents: automatic scheduled runs are blocked from every write route (commit, comment, append); the WPDev write earlier was a Run-now. Rule: scheduled runs only read and put a complete result in the run output; attended runs / Run-now apply and commit. Unattended work resumes via attended PROCEED from phone, Claude check-ins (TRV-1) and the Gemini controller (sprint 2) | rules §7 | | 2026-10-15 | Offline Google Docs for travel | MMDEP Actions: https://docs.google.com/document/d/13LP5pkwABVXtw6nbwvGBweB-EZ_hykzJtqPFNxLsDvY/edit ; MMDEP Documentation: https://docs.google.com/document/d/1OkMh9dbhogp3taDrufF9GcSQdUkPxSeXCZ3YepmHXEw/edit (snapshots 15 Oct 22:20 IST; panel stays the place to answer) | owner notes 10, 34 |

Open: D10 (share Ajay's doc), D11 (reduce mode), D12 (hold AWS), D13 (who acts).

Code awaiting approval: branch iter-04/collector (read-only collector, stdlib only, 3 tests passing).