Processes, triggers, and automation

CORA turns recurring business responsibilities into constrained, reviewable processes. A business user describes the work in normal language; CORA asks for missing rules, builds the process, and shows what will happen.

Event-driven, not continuously thinking

Processes do not keep an LLM running all day. Software triggers, connector events, schedules, and explicit waits wake the process. Postgres stores the durable state and the queue wakes the next step only when work is ready.

Examples include:

• When a salesperson emails an order and license plate, extract the plate and propose the guarded ERP update.
• When an ERP order receives its first license plate, prepare the customer's upcoming-car email.

CORA Flow is the trust view

CORA stores a constrained typed process graph as executable truth and projects it into business-readable CORA Flow cards. The Flow helps a normal business user understand triggers, decisions, approvals, Agent work, waits, exceptions, and outcomes while the selected step stays inspectable. Card positions are presentation only; the governed typed graph remains the versioned runtime contract.

Safe rollout

A process can be simulated, shadowed, supervised, and later granted narrow autonomy. Executable steps create normal CORA tasks, so plan approvals, exact action previews, executor trust, audit receipts, metering, and exception handling still apply.

For a supervised write, CORA reads the current value, shows the exact before/after diff, waits for approval, re-checks the precondition, writes idempotently, and verifies the stored result. A reversal is a separate guarded action rather than an invisible undo.