Skip to content

Start

First Pod

The recommended order for turning a blank workspace into a useful pod.

  1. Define the operating job: one team or process, one domain, one primary unit of work.
  2. Create the pod and inspect what the starter gave you.
  3. Create or refine collaborative tables for shared business records.
  4. Add one function only if a write needs validation, coordinated records, or an external operation.
  5. Add an agent for one judgment-heavy step, with explicit input and output schemas.
  6. Create a workflow only when there is real orchestration: branching, waits, schedules, or handoffs.
  7. Build the app last, against verified resources, while keeping the first screen focused on real work.

CLI rhythm

lemma pod create support-triage --with-starter --description "Triage and route inbound support work"
lemma pods select support-triage --save-default
lemma pod describe

lemma table create --pod-id <pod-id> --payload-file ./payloads/tickets-table.json
lemma function create --pod-id <pod-id> --payload-file ./payloads/escalate-ticket-function.json
lemma agent create --pod-id <pod-id> --payload-file ./payloads/ticket-triage-agent.json
lemma workflow create --pod-id <pod-id> --payload-file ./payloads/ticket-triage-workflow.json
lemma pod describe <pod-id>

Do not skip verification

Before wiring an app or workflow node, run the underlying function, inspect agent output, and verify table records with realistic sample data.