docs/README.md
Let'em Cook
Unhinged, Accelerated DevOps for Agents & Users LEMC turns versioned recipes into discoverable, bounded actions that people click and agents run with
lemcli.
Key pages
- Home — Product overview, sheriff field notes, and the human/agent action model.
- Documentation — This clickable HTML field guide.
- Releases — First-party amd64/arm64 lemcli builds and digest-pinned AMD64 LEMC web and runner images.
1. Start here
- What is Let'em Cook? — Cookbooks, pages, recipes, steps, and shared execution.
- Publish a cookbook and grant the team — Maintained source examples, managed images, separate secret binding, app deployment, and run-only ACL workflow.
- Operational use cases — BYOK WordPress migrations, corporate Nmap PDF reports, timed infrastructure, Terraform labs, restore drills, and Day-2 self-service.
- Deterministic computational units — The boundary, its limits, and why it helps agents.
2. Humans and agents
- MCP integration vs LEMC's operating model — Governed supply chain, dynamic authority, isolation, human/agent usability, and durable evidence.
- lemcli field guide — Discover, submit, follow, inspect, and retrieve.
3. Runtime and output
- Architecture — Server-owned execution, isolation, event fanout, and storage.
- Themes — Operator-installed bundles, account-admin selection, agent authority, and the current no-upload boundary.
- Recipe state and LEMC verbs — Injected context, durable workspaces, step handoffs, artifacts, and visible output.
Agent quick path
- Authenticate with the target LEMC server.
- List authorized apps, then inspect an action surface with
lemcli jobs surface ... --format=json. - Choose a returned action ID and supply only its declared form values.
- Run it with
lemcli jobs run ... --action <action-id> --follow --render html. - Confirm task ID, terminal reason, steps, logs, and artifacts.
Execution mode, runner selection, and isolation policy are server/operator decisions. Clients do not choose them per request.