Skip to content

MMDEP Assistant — current knowledge

Last reviewed: 2026-10-25 (PROCEED).

Operating mode

A bare PROCEED is Flow P. Do not ask questions in chat; work the approved queue, queue laptop-dependent tasks, and reply briefly. Follow docs/agents/mmdep-agent-rules.md, docs/adr/0012-three-process-flows.md, and docs/registers/flags.md. Each run records its reply and actions in docs/sessions/YYYY-MM-DD.md; assistant cursor lives on reports.

Latest evidence inspected

  • Collector snapshot control/latest.md: 2026-10-21T14:53Z; heartbeat active until 22:53 IST, runner online. Check-in-late flag remains: last check-in 2026-10-20T15:39:18Z.
  • Queue: webapp-sakai 6 MRs (5 idle >14 days); website 6; API 23 (last pipeline failed, 8 idle >14 days); MM-Cron 22 (last pipeline failed, 6 idle >14 days); MCRM 56 (46 idle >14 days); Portfolio Engine 5; sandbox 4 (last pipeline canceled); MMDEP 0 MRs and 23 issues.
  • API production: /api/health 404; /api/schemes 10,008 records; scheme 120245 NAV has 3 duplicate dates and a 10-day gap; NIFTY 50 index NAV has 10 duplicate dates.
  • Staging: health 200; /api/schemes reports 1 record; scheme 120245 NAV last date 2026-08-19; index NAV 404; active NFOs 500; category and top performers 200.
  • TLS/DNS: dev.moneymarche.com hostname mismatch; wpdev, portfolio-engine-dev, mail, dashboard DNS/TLS failures. MMCLONE expires 2026-12-10 (49 days); main certificates expire 2027-01-13 (83 days).
  • Harness snapshot 2026-10-21T14:56Z: US$0.1918 MTD; eight listed items, seven skipped by mode/state/scope and #24 blocked. No new execution pass recorded.
  • PE #376 inspection passed at head 700f65a6; CSV exports and visual review still required before #309/#310 acceptance.
  • Relay resolves WPDev #123 and sandbox #27 as technical choices for WPDev/MWMC; do not re-raise as Atul business questions. PE #329/#330/#375 and MCRM #118 instructions remain as recorded in answers.md.
  • Sprint 1 completion across all five projects is not proven by the five control sources; design → issues → preflight status remains UNKNOWN pending repository-level verification.

Next

Read the five control sources, this knowledge file, today's session log, and the assistant cursor each run. Process only new evidence; do not duplicate completed work without changed heads or a stated need. Treat collector results as evidence, not proof of remediation. Do not trigger pipelines or production probes unless authorized by the relevant queued issue.

Latest evidence inspected (25 Oct PROCEED)

  • Control heartbeat (snapshot 24 Oct 23:46 IST): laptop reported active until 25 Oct 02:16 IST; runner online; check-in late since 21 Oct 15:40Z; checkout behind main by 7.
  • Collector: S1, S2, S4, S6–S9 timed out; S3 returned 404; S5 returned 200. Production /api/health 404; schemes 10,008; scheme 120245 has 3 duplicate NAV dates and a 10-day gap; NIFTY 50 index NAV has 10 duplicate dates. Staging health 200, schemes 1 record, index NAV 404, active NFO route 500; scheme NAV last date 2026-08-19.
  • Harness snapshot: MTD $0.1918; queued issues are skipped because state is review or blocked; no new execution pass established.
  • Queue watch: added docs/status/queues.md. No runs/S<n>.md or matching Sonnet step result was found in indexed MMDEP content; absence from index is not proof of absence in owning repositories. Nudges recorded in docs/relay/answers.md.
  • Inbox: no new business question was evidenced in accessible run-result files. Existing WPDev #123 and sandbox #27 are technical decisions already addressed in relay answers; do not re-raise.
  • Hygiene/coding: no safe issue cleanup or coding issue was verified as eligible. Harness issues remain review/blocked, so no issue claimed and no PR created.
  • Digest: reports/mmdep-assistant/2026-10-25-0015.md (control branch).
  • Limitations: reports/ACTIONS.md and some expected queue/status paths were not present on control/main when queried. No GitLab write, production probe, server action, or pipeline trigger performed.

Next

  • Resume queue T0 (#155): verify merged PRs and close matching issues; seed ready low-risk issues with complete routing blocks.
  • API Lane S: inspect owning-repo MR state and publish docs/relay/api-lane-s/runs/S1.md; do not act on production-lane MRs.
  • When collector refresh arrives, compare failures and queue state against this snapshot.

Latest evidence inspected (25 Oct 2026, 00:52 IST)

  • Control heartbeat and collector are unchanged since the 00:15 digest: laptop reported active until 02:16 IST, runner online, but the expected 00:46 collector refresh has not appeared. No live laptop probe was performed.
  • Data/API failures remain as recorded in the 00:52 digest: source S1/S2/S4/S6–S9 timeouts, S3 404; production health 404 and NAV duplicate/gap flags; staging catalogue one record, index NAV 404 and active NFO 500.
  • Hygiene: verified PRs #105, #107, #113, #115, #117, #128, #134, #138 and #144 are merged into integration/sprint-2; closed corresponding issues #104, #106, #112, #114, #116, #127, #133, #137 and #143. Re-readied #47 by changing only its routing block from state review to ready.
  • F5: claimed issue #158 and opened docs-only PR #159 adding docs/agents/README.md; PR remains open and mergeability/CI is not yet confirmed.
  • Queue watch now covers Sonnet, API Lane P, API Lane S and MWMC. PR #160 carries the queue, nudge, backlog, knowledge and session updates and remains open pending CI. No matching step-result files were found in indexed MMDEP content; owning-repository result files remain unverified.
  • Digest: reports/mmdep-assistant/2026-10-25-0052.md on control. No GitLab writes, production probes, server actions, or pipeline triggers.

Next

  • Check PR #159 CI and merge only if green and low risk.
  • Complete the queue-status/nudges/backlog docs PR and merge only if CI is green.
  • Finish T0 by seeding ready low-risk work; API Lane S publishes S1; MWMC starts M1; API Lane P starts P1 on 26 Oct.