Design backlog¶
Atul (17 Oct): questions like these should be discussed with a Design agent, which is missing today; these sample cases should make our processes robust and well thought out.
| ID | Item | Questions Design must answer | Inputs |
|---|---|---|---|
| DS-1 | Regulatory and market watch | Collector per source, cadence, change detection, summary and routing, compliance flagging, storage | docs/registers/watch-sources.md |
| DS-2 | AMC master reconciliation | Providers API as master; AMFI monthly factsheet link list as the check; how new, closed and merged AMCs flow to MCRM; who approves changes | Owner note 63; API knowledge-check answer |
| DS-3 | Factsheet link resilience | Links are probably hardcoded today (Atul); AMCs move PDFs but must tell AMFI: always resolve links from AMFI each month, never hardcode; alert on dead or moved links | AMFI factsheet page; mm-crons factsheets-parse/ |
| DS-4 | Factsheet format changes | Per-AMC parser contract (fixed JSON schema), layout fingerprint per month, schema validation and range checks, quarantine and alert when a format changes instead of loading bad data; who fixes (open work package) | DR-009 §2 |
| DS-5 | Factsheet economic content | Extract the market and macro commentary sections (currently ignored) into a structured monthly digest | DS-4 parsers |
| DS-6 | ULIP data for ICICI Prudential Life | Product data vs fund data, active and legacy funds, authentic source and cadence | Owner notes 55, 57 |
| DS-7 | Category status, show-in-menu and roll-up rule | Exact production rule from MWMC/WPDev/Ajay findings; API effective-tree contract | Owner note 53 |