| A-01 |
Claude chat, Claude Code and the desktop app share one usage allowance (5-hour window plus weekly cap); scheduled cloud sessions are assumed to count too |
Secondary source (chudi.dev, 8 Oct), quoting Anthropic help; cloud sessions unconfirmed |
S |
Monthly |
MCL §7 credit protection; vacation plan (cloud reviews) |
| A-02 |
Claude API credits are a separate allowance under commercial terms (no training; 30-day retention) |
Claude Code data-usage docs, 11 Oct |
V |
Monthly |
MCL S4 on API credits; vendor data note §5 |
| A-03 |
Claude consumer plans train only if the setting is on (5-year retention if on, 30 days if off) |
Claude Code data-usage docs, 11 Oct |
V |
Quarterly |
Capacity classes (vendor data note §4) |
| A-04 |
Claude's consumer terms bar scripted access except via an API key or permitted routes; claude setup-token (one year) is documented for scripts and CI |
Anthropic consumer terms; Claude Code authentication docs, 11 Oct |
V |
Quarterly |
Terminal mode on a VM; MCL S4 |
| A-05 |
GitHub Actions minutes are charged to the repository owner; Free (personal or organisation) gets 2,000 private-repo minutes a month; public repos free; self-hosted runners free per GitHub's billing page (a secondary report says a fee applies) |
GitHub billing docs, 11 Oct; heise; merginit |
V (fee: conflicting) |
Monthly |
MCL runner choice; organisation layout |
| A-06 |
GitHub Free can't enforce branch protection on private repos (rulesets need Pro) |
GitHub API responses on 3 repos, 10 Oct |
V |
On plan change |
R1; "GitLab for code" |
| A-07 |
GitHub allows one free personal account per person plus at most one free machine account |
GitHub Terms of Service, 11 Oct |
V |
Yearly |
Account layout |
| A-08 |
GitLab Free: protected branches available; compute minutes 400 a month per top-level group; 5 users per top-level group |
GitLab docs, 10 Oct; secondary source for minutes |
V / S |
Quarterly |
"GitLab for code"; group layout; MCL not running on GitLab CI |
| A-09 |
Changed 11 Oct: GitLab mirroring has restrictions (Atul). Claude's read-only code view comes instead from our own scheduled mirror job (tools box or GitHub Actions: fetch from GitLab with a read token, push to a private GitHub mirror) |
Atul, 11 Oct |
Atul |
Before use |
"GitLab for code, GitHub for work" |
| A-10 |
Gemini: once one API project has billing enabled, prompts get paid terms; the unpaid tier uses content for improvement with human review |
Google billing page and API terms, 10–11 Oct |
V |
Monthly |
Gemini USD 10 plan; routine-only rule for free use |
| A-11 |
Spreading one workload across several free Gemini projects can be treated as quota circumvention |
Google forum case, Jul 2026 |
S |
Quarterly |
Account layout (paid projects per vertical) |
| A-12 |
ChatGPT consumer plans train by default unless switched off; the API isn't trained on by default; the Terms bar programmatic extraction of Output and circumventing limits |
OpenAI help and Terms of Use, 11 Oct |
V |
Quarterly |
Withdrawn read-back relay; prompt-push automation (to examine); Codex with an API key |
| A-13 |
ChatGPT scheduler and connectors are available on free accounts |
Atul, 11 Oct |
Atul |
Before use |
Which account runs ChatGPT schedules |
| A-14 |
Lightsail Linux 4 GB = USD 24, 8 GB = USD 44; Windows 4 GB = USD 44, 8 GB = USD 74 a month (before GST) |
AWS pricing page, 11 Oct |
V |
Before purchase |
VM option L1/L2/L3 |
| A-15 |
Codex unattended use: an API key is recommended (per-token billing) |
OpenAI auth docs, 11 Oct |
V |
Quarterly |
Terminal mode; budgets |
| A-16 |
Antigravity can run open models locally (Gemma 4 26B needs more than 24 GB); open models only |
Secondary sources, 24 Sep |
S |
When hardware is planned |
Local-model deferral |
| A-17 |
Atul's laptop travels during 16–30 Oct, is checked twice a day, and can't be woken remotely |
Atul, 10 Oct |
Atul |
— |
Vacation plan; GitLab-through-Chrome is best effort |
| A-18 |
Revenue comes first from the website and MCRM |
Atul, 10 Oct |
Atul |
Each iteration |
Re-phasing (first real project) |
| A-19 |
MCRM's PR backlog waits for an independent reviewer, not for Atul's time alone |
Atul, 10 Oct |
Atul |
— |
MCRM review session; AC-1 |
| A-20 |
The team is 4 people plus the operations head's account; durable ownership comes from company-owned organisations, groups and projects |
Atul, 11 Oct |
Atul |
On team change |
Account layout |
| A-21 |
Copilot is not retained |
Atul, 10 Oct |
Atul |
— |
DR-002 role table |
| A-22 |
The laptop's memory can't run local models |
Earlier MMDEP findings |
V |
When hardware changes |
Local models deferred |
| A-23 |
One 2 GB Lightsail server hosts production, staging and development WordPress, API production and staging, Mautic, SuiteCRM and MM-Cron |
TEA master index (reconciled 20 Sep) |
V (dated) |
After TEA #24 |
Cloud terminal and estate proposal §2, §5 |
| A-24 |
Bluehost is shared cPanel hosting (prepaid, 2 years left) running MMCLONE and WPDev |
Governance #29; local register; Atul |
V / Atul |
At renewal |
Estate proposal option B; §15B phase 2 |
| A-25 |
GitLab pipelines can run on our own runners (laptop or server) without using GitLab's compute minutes; runners are light, jobs are what load the machine |
Atul checked independently, 11 Oct; GitLab docs |
V (Atul) |
Before setup |
Tools box GitLab runner; runner controls |
| A-26 |
Oracle's free tier was cut in June 2026 and can change without notice |
InfoQ, Jul 2026 |
S |
If reconsidered |
Oracle option rejected |
| A-27 |
Staging has its own database; it may depend on the API database (found when copying production to MMCLONE) |
Atul, 11 Oct |
Atul |
Before the staging move |
Tools box scope; staging move to Bluehost |
| A-28 |
Bluehost costs ≈ ₹21,198 per 3-year term (rupees, confirmed by Atul); renewed Jun 2026, so ≈ 2.75 years are paid and should be used |
Bluehost India billing page; Atul, 11 Oct |
V |
At renewal (≈ Jun 2029) |
Estate proposal: keep Bluehost; staging WordPress move |
| A-29 |
MM-Cron jobs run from root cron on the production server; NAV persistence stopped at 19 Aug 2026 without an alert (state since then unknown) |
TEA audit, Sep 2026; mm-crons repo |
V (dated) |
This week |
MM-Cron augmentation |
| A-30 |
AMFI, AMC and NSE source files are public data (free model tiers acceptable for the files; not for our code) |
Nature of the sources |
V |
— |
MM-Cron repair agent engine choice |
| A-31 |
A GitLab project can be transferred to another group without data loss, and its pipelines then use that group's minutes (done in September) |
Atul, 11 Oct |
Atul |
— |
Fallback only; own runners make it unnecessary |
| A-32 |
A persistent browser desktop in a container (web-streamed, profile in a volume) needs ≈ 0.5–0.7 GB idle and ≈ 1.5–3 GB with 5–10 tabs; extensions work in headed mode on a virtual display |
Image documentation (linuxserver/chromium, Selenium); Atul's checks; resource figures are estimates |
S |
Measure in the first week |
Box size (4 GB vs 8 GB); server browser |
| A-33 |
The production AWS account was opened 22 Feb 2023, so it qualifies for Lightsail's 3-month offer on paper (Lightsail first used after 8 Jul 2021); the offer covers the first eligible bundle and was most likely used by the WordPress server in 2023 |
Atul, 11 Oct; Lightsail offer terms |
Atul / inferred |
Check the Feb–May 2023 bills |
Trial-first plan (new free-plan account remains the recommendation) |
| A-34 |
Bluehost also hosts the company email (in addition to WPDev and MMCLONE) |
Atul, 11 Oct |
Atul |
At Bluehost renewal; before any DNS change |
Keep Bluehost; staging move must not disturb mail (shared resources, DNS/MX records); any retirement needs a mail migration plan |
| A-35 |
A ChatGPT account allows 3 scheduled tasks; all 3 are used (MMDEP triage, MCRM, MWMC); Portfolio Engine's needs ride in the MMDEP triage prompt |
Atul, 11 Oct |
Atul |
When a ChatGPT plan changes or a slot frees |
The triage prompt must keep PE's section; schedulers are a PM channel to instruct agents alongside AGENTS.md; scheduler prompts are versioned in the facts sheet §5 |
| A-36 |
Google AI Studio: once one billing account is active, every project's API use is under paid terms (no training on content); each project has its own free quota. Plan: project "MMDEP Reserve" (billed, minimum prepay), a separate project and key for cloud; the existing MoneyMarche key stays on the laptop |
Atul, 12 Oct (verified by Atul) |
Atul |
On any Google terms change; when billing lapses |
Gemini can process internal (non-client) content in cloud scripts; separate keys per place limit blast radius; using extra projects to multiply free quota stays within honest use (no circumvention) |
| A-37 |
ChatGPT scheduled (unattended) runs cannot write content: safety checks blocked issue creation (GitHub 12 Oct 09:00; GitLab 12 Oct 15:51) and file creation; only an empty branch was created; no approval prompt was offered. Interactive chats can write |
Test, 12 Oct 15:51 IST (evidence: former PM chat report) |
Atul |
When OpenAI changes task tools, or a plan with different task capabilities is used |
ChatGPT schedulers read and plan only; writes happen in attended chats or through other executors (Gemini CLI on the runner, Claude Code cloud sessions); decision D13 |