Pin actcore-api and actcore-worker to
git-9a46350bb3e1192b76aab859218f95312e17fdf4
(sha256:08966e8dd976d2e6f50711f33b2ab0abaa650aed998b28d743483999729e7d66),
carrying repository grant v2 (9737577, ACTIVITY-WP-0046) and the ops-run
lease-expiry ceiling (42347da). Founder-approved 2026-10-19. The build of
head 9ef75e0 failed on a transient PyPI timeout; the founder chose the
existing 9a46350 image instead. event-router stays on sha256:cd4e924c.
Image fields only; no migrations. Rollback: Argo revision f9f2640, api/worker
sha256:fdc631d7.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 244572@bnt-lap001
Assistant-Session: 3b235e1a-ae45-4d0f-ae70-17a9bd78ece8
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.
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.