# 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](INTENT.md) — product purpose and hard boundaries
- [SCOPE.md](SCOPE.md) — implemented capability and current gaps
- [docs/runbook.md](docs/runbook.md) — local and production operations
- [docs/api.md](docs/api.md) — API surface
- [docs/adr/adr-007-bounded-operations.md](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.