agent-company
137cdb3b01
Validate Flux manifests / kustomize-build (pull_request) Failing after 23s
Add flux/{zip-enrichment,holidays,air-quality}/servicemonitor.yaml so
Prometheus (kube-prometheus-stack) can auto-discover and scrape each
API service once deployed.
Each ServiceMonitor:
- Selects pods via app.kubernetes.io/name label
- Scrapes /metrics on the http port every 30s
- Uses release: kube-prometheus-stack label to match Prometheus selector
- Lives in the same namespace as the API service
Add each servicemonitor.yaml to its kustomization.yaml resources list.
kustomize build flux/ passes with no errors.
Closes leeworks-agents/api-company#110
api-company
Meta-repo for the leeworks-apis recursive build loop. This repo holds cross-cutting concerns; the actual APIs each live in their own repo.
Sibling repos
| Repo | Purpose | Status |
|---|---|---|
| leeworks-agents/zip-enrichment | US ZIP code enrichment (Census ACS + HUD-USPS) | Phase 1 |
| leeworks-agents/holidays | Public holidays and business days | Phase 1 |
| leeworks-agents/air-quality | AQI + pollen + forecast | Phase 1 |
What lives here
MASTER_BUILD_PROMPT.md— the prime directive driving the build loopROADMAP.md— cross-repo milestones (Phase 0–6)STATUS.md— living revenue + infra scorecardSESSION_LOG.md— append-only log of agent work sessionsresearch/RESEARCH_LOG.md— market research findings, candidate API ideasflux/— cluster-level Flux manifests (registry, runner, monitoring, docs-site)monitoring/— Prometheus, Grafana, Gatus configsdocs-site/— Astro + Redoc site atdocs.leeworks.dev
How this gets worked on
The agent-company Kubernetes deployment in 0xWheatyz/Talos runs three crons every 5 hours:
/managerdiscoversagent-readyissues here and in each API repo, fans out@repo-managersubagents/sprintreadsROADMAP.mdand breaks down the next phase into new issues/shipmerges approved PRs and creates upstream PRs to0xWheatyzforks
Goal: $100/mo net revenue via RapidAPI marketplace listings.