ACTIVITY-WP-0048-T01 now has the 2026-10-23 production read. Semantics and the activity-core 410 pointers match the contract. Ops-run history still needs operator auth, and State Hub has not switched yet. ACTIVITY-WP-ADHOC-2026-10-19 is finished because T01–T03 were already done.
Assistant: grok
Assistant-Session: 01a16889-9224-7ec0-bee0-2a46dd3819c4
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.