Claude Project Tracker

What's pending across every project

7 open · sorted by priority then due-date

kind all blockers todos decisions notes

priority all urgent high low

Filtered by tag infra clear

todo urgent

Close Cloud SQL to the internet: remove 0.0.0.0 authorized network and require SSL

Instance crypto-track-321e8b45 has a public IP (34.57.238.28), requireSsl=false (ALLOW_UNENCRYPTED_AND_ENCRYPTED), and an authorized network "for EV Connection" = 0.0.0.0 — effectively open to the internet with only the postgres password protecting it. Instance is shared with AdaptiveSAT, Vajra, CitrineOS, tracker. Coordinate with Vajra before removing the EV entry; prefer Cloud SQL connector/Auth Proxy for all clients.

security db infra

gcloud sql instances describe crypto-track-321e8b45

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: The database is effectively open to the internet: public IP, SSL optional, authorized network 0.0.0.0. saravanan: create cointrends in tracker and push these items there

10d ago
10-16 19:08

todo urgent

Lock down core service: require auth, especially /db/execStoredProc, /deletefile, /uploadfile, /purgeStageData, /insertdb

crypto538-core-service is deployed --allow-unauthenticated. Options: make it private (IAM invoker = web-service SA + Scheduler SA) and have the webapp go through web-service only; or add an API-key/OIDC check on admin/write routes. Ties to the item about the webapp calling core directly.

security core-service infra

crypto538-core-service/main.go:486-532crypto538-core-service/cloudbuild.yaml

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: The core service needs no authentication, including /db/execStoredProc, /insertdb, /uploadfile, /deletefile. saravanan: create cointrends in tracker and push these items there

10d ago
10-16 19:08

todo high

Move model training to cloud and retrain — prediction models last trained 2025-10-30

Inference runs every 5 min (Scheduler prediction_calls → ml /run_prediction) on 120 DARNN models in gs://nlp_ml_files/prediction_files last written 2025-10-30. Training lives in CoinTrends_Python (local Windows GPU box, localhost Flask chain :17000 → :5000). Target: Cloud Run Job or Vertex AI custom job with GPU, parameterised by asset + minute offset, triggered by Scheduler, creds from Secret Manager, metadata write-back to cryptopredictionslicemaster.

ml training infra

CoinTrends_Python/master_create_update_latest.pyCoinTrends_Python/api_latest.pyCoinTrends_Python/ModelCreation_latest.pygs://nlp_ml_files/prediction_files/

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: Predictions run on year-old models — the 120 model files were last trained 30 Oct 2025 and nothing retrains them. saravanan: create cointrends in tracker and push these items there

💬 1 comment

10d ago
10-16 19:09

todo high

Training 2/5: Build GPU container image (CUDA PyTorch base) via Cloud Build → Artifact Registry

Dockerfile on a CUDA-enabled PyTorch base, pinned versions, psycopg2 + cloud-sql-python-connector + google-cloud-storage. Push to us-central1-docker.pkg.dev/prj-crypto538-prod-260529/crypto538-container-images/ml-training. Cloud Build config alongside.

ml training infra

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: where is the model training to be moved to CloudRun (GPU based) claude: Step 2: GPU container image built by Cloud Build into Artifact Registry.

10d ago
10-16 19:12

todo high

Training 3/5: Create Cloud Run Job with L4 GPU, dedicated service account, Secret Manager creds, task-index fan-out

gcloud run jobs create ml-training --gpu 1 --gpu-type nvidia-l4 (us-central1; confirm GPU quota/region availability first). Dedicated SA with only: Cloud SQL Client, read/write on gs://nlp_ml_files/prediction_files, secret accessor on the DB secret. --tasks = assets × 12 offsets (120 today), --parallelism capped to quota; CLOUD_RUN_TASK_INDEX → (asset, minute). Codify in crypto538-terraform. Note: #98 — only this SA should be able to write model files.

ml training infra

#98crypto538-terraform/environments/prod/main.tf

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: where is the model training to be moved to CloudRun (GPU based) claude: Step 3: Cloud Run Job with L4 GPU, least-privilege SA, task-index fan-out over asset × minute.

10d ago
10-16 19:12

todo

Consolidate the three LLM backends and cut always-on Ollama cost

crypto538-askgenie-service (Ollama llama3, 16 GB, 4 CPU, min-instances=1, no CPU throttling — billed 24/7) plus a separate llama-cpu Cloud Run service plus OpenAI calls from core. Pick one backend for Genie/recommendations and scale the rest to zero or delete.

cost llm infra

crypto538-askgenie-service/cloudbuild.yamlcrypto538-core-service/main.go::llamaCompletion

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: Three LLM backends run side by side; Ollama runs at 16 GB with min-instances=1 and is billed around the clock. saravanan: create cointrends in tracker and push these items there

10d ago
10-16 19:09

todo low

Final cleanup: remove/confirm everything Claude added to GCP during the review

Footprint so far (none of it changes how prod runs): (1) IAM: Cloud SQL service account p475046183936-kjdopc@gcp-sa-cloud-sql granted objectAdmin on gs://crypto538-prj-crypto538-prod-260529-bucket (needed for schema/query exports) — rollback: gsutil iam ch -d. (2) gs://crypto538-prj-crypto538-prod-260529-bucket/claude-schema-exports/ (2 schema-only .sql files; query CSVs are deleted after each read). (3) Cloud Build 7d835ecf may have pushed ml-training:test-cpu / :test-gpu to Artifact Registry crypto538-container-images — delete if unused. (4) No Cloud Run jobs, no DB writes, no scheduler changes. Local only: ml-training/, ship.sh, commit_razorpay_deprecation.sh, 'Tracker project_id' line in cointrends/CLAUDE.md. Merged code change: PR #70 (comments only).

cleanup infra

gs://crypto538-prj-crypto538-prod-260529-bucket/claude-schema-exports/Cloud Build 7d835ecf-2e1a-430a-bc11-040a85bd4ee6↗ HopewellPartners/crypto538-core-service#70

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: we need a clean up step by step with proper validation and rollback at the end of all our work claude: Listing everything I've added to GCP so the final cleanup can remove or keep it deliberately.

7d ago
10-19 14:19

What's pending across every project

Add an item