Atomic / Evolution Deck
Capability map / traceability first

Every promise has a path.

Atomic is easiest to understand as a set of executable contracts. These cards name the contract, describe the observed behavior, and link directly to the source files that own it.

Improvement plan traceability

These are intentionally plans, not unimplemented claims. Each one is anchored to exact current Atomic files so an Atomic++ implementation can be reviewed against the runtime it extends.

PlanCurrent Atomic anchorsAtomic++ direction
Transport adapterspackages/coding-agent/src/modes/rpc/rpc-types.ts packages/coding-agent/src/modes/rpc/rpc-command-handler.ts packages/intercom/types.tsNormalize Telegram, Slack, GitHub events into a versioned envelope, then route to a workflow or stage without coupling transport code to the executor.
Durable deliverypackages/workflows/src/durable/backend.ts packages/workflows/src/durable/dbos-envelope.ts packages/workflows/src/shared/persistence-session-entries.tsPersist inbound event IDs, delivery attempts, run IDs, and response receipts beside workflow checkpoints; replay is explicit and idempotent.
Human controlpackages/workflows/src/extension/workflow-run-control-command.ts packages/workflows/src/runs/background/quit.ts packages/workflows/src/durable/resume-runtime.tsExpose status, pause, resume, interrupt, and quit as authenticated adapter actions with the same state transition rules as the CLI.
Grok compatibilitypackages/intercom/broker/client-message-validation.ts packages/intercom/broker/supervisor-channel.ts packages/coding-agent/src/core/agent-session-message-queue.tsKeep useful bridge patterns—polling, concise routing, thread/reply context, retries, and safe action parsing—while replacing process-local assumptions with signed, durable, transport-neutral events.

Usage & cost in the capability map

The coding-agent session layer already exposes provider usage and configured cost totals; workflow model-attempt metadata only permits optional usage today, and the foreground controller does not populate it. A future ledger should attach reported metrics to the stage attempt without turning compaction estimates or model-rate configuration into provider claims.

Open Usage & cost →