Per-container requests distributed by 7d p95 (requests only, no new limits): api 5m/96Mi, worker 5m/176Mi, event-router 5m/80Mi (k8s/gitops and the 20-runtime copy), statehub-edge-relay 50m/128Mi -> 10m/96Mi, temporal 35m/240Mi, temporal-ui 5m/16Mi, nats 5m/16Mi, app-db 50m/256Mi -> 10m/48Mi, temporal-db 50m/256Mi -> 15m/128Mi. llm-connect (5m/48Mi) is in the llm-connect repo. The app-db/temporal-db source requests and 1Gi memory limits were never applied live. Evidence: resource-control 2026-10-21 node budget (3d9b1bd). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 276069@bnt-lap001 Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| .kaizen | ||
| activity-definitions | ||
| agents | ||
| declarations/backup-daily | ||
| docs | ||
| dynamicconfig | ||
| e2e | ||
| event-types | ||
| history | ||
| k8s | ||
| migrations | ||
| registry | ||
| schemas | ||
| scripts | ||
| src/activity_core | ||
| tasks | ||
| tests | ||
| wiki | ||
| workplans | ||
| .dockerignore | ||
| .env.example | ||
| .generated-work-records.json | ||
| .generated-work-records.mk | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| alembic.ini | ||
| CLAUDE.md | ||
| cron_expression | ||
| docker-compose.dev.yml | ||
| docker-compose.railiance.yml | ||
| Dockerfile | ||
| Dockerfile.frontend-patterns | ||
| Dockerfile.pqrst | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| misfire_policy | ||
| pyproject.toml | ||
| README.md | ||
| SCOPE.md | ||
| timezone | ||
| uv.lock | ||
| WORK-RECORDS.md | ||
activity-core
activity-core is Coulomb's durable automation factory. It answers when an automation fires (Temporal Schedules, NATS, webhooks, or manual triggers), what should be emitted (deterministic rules or optional validated LLM instructions), and where the result goes (task, report, evidence, or runtime-delivery sinks).
It is not a project tracker, a general shell runner, or a task executor. A small code-owned registry permits three bounded platform operations: controlled SBOM ingest, Forgejo package pruning, and CNPG Option A backup.
Start here
- INTENT.md — product purpose and hard boundaries
- SCOPE.md — implemented capability and current gaps
- docs/runbook.md — local and production operations
- docs/api.md — API surface
- docs/adr/adr-007-bounded-operations.md — admitted mutation contract
Definitions are authored in activity-definitions/*.md and synchronized into
Postgres and Temporal. The /activity-definitions/ REST endpoints provide
basic row administration only; they do not round-trip the full markdown
rules/instructions contract.
For local setup and verification, follow the runbook. The installed activity
CLI is the operator review surface; run uv run activity --help for commands.