All nine API/MM-Cron designs now exist. This session added the sprint-2 designs:
API: write security, NAV integrity, ingest routes;
stgapi: isolation proof and data load;
MM-Cron: AMFI jobs.
The API agent's queue steps P1, P2 and P5 now start from these LLDs (check against the code, then build), so the agent doesn't redo design work. Lane S S2 points at the stgapi LLD.
One finding to watch: the security inventory's first job is to check whether any client-data route (customer, KYC, bank) accepts writes without a login. If one does, it comes to you the same day.
Decisions TD-061 to TD-067. Harness issue #200 makes the design gate check these subfolder LLDs.
For you: one approval for the four high-risk API designs (for-atul/design/2026-10-27-approve-api-sprint-2-designs.md). Still open: the adapter framework approval (#193) and AMC download terms (#176).
The GitLab snapshot still isn't in the repository (#191, no reply yet). GitLab is blocked from this workspace, so code facts stay UNVERIFIED.
Read main since 25 Oct; issues #191, #185, #150, #193, #176 (no answers); open agent:claude (none); relay folders for api-lane-p/s (none yet); the 19 Oct write-security brief; data-source register S1–S12; an existing harness issue for the routing-block format.
Tried GitLab directly: blocked by the workspace proxy (403).
Ran the LLD check recursively over docs/design/ before filing #200: only subfolder LLDs exist under api-mmcron, all pass.
Wrote api/LLD-write-route-security.md, api/LLD-nav-integrity.md, api/LLD-ingest-routes.md, api/sprint-2.md, stgapi/LLD-staging-isolation-and-load.md, stgapi/sprint-2.md, mm-cron/LLD-amfi-jobs.md; updated mm-cron/sprint-2.md, the index, Lane P and Lane S queues, the decisions register; wrote the approval request.
Checks: check_lld on all six LLDs → ok; python -m mmdep.design_check → ok; pytest -q (below).