e3
East Execution Engine (e3) - durable dataflow execution for East programs. Use when: (1) Authoring e3 packages with @elaraai/e3 (e3.input, e3.task, e3.package, e3.export), (2) Running e3 CLI commands (e3 repo create, e3 start, e3 watch, e3 get, e3 set), (3) Working with workspaces and packages, (4) Content-addressable caching and dataflow execution.
What this skill does
# East Execution Engine (e3)
e3 is a durable dataflow execution engine for East programs with content-addressable caching.
## Quick Start
```typescript
// src/index.ts
import { East, StringType } from '@elaraai/east';
import e3 from '@elaraai/e3';
// Define an input
const name = e3.input('name', StringType, 'World');
// Define a task
const greet = e3.task(
'greet',
[name],
East.function([StringType], StringType, ($, n) =>
East.str`Hello, ${n}!`
)
);
// Bundle and export
const pkg = e3.package('hello', '1.0.0', greet);
await e3.export(pkg, '/tmp/hello.zip');
export default pkg;
```
```bash
# Create repository
e3 repo create .
# Import and deploy
e3 package import . /tmp/hello.zip
e3 workspace create . dev
e3 workspace deploy . dev [email protected]
# Execute dataflow
e3 start . dev
# Get result
e3 get . dev.tasks.greet.output
```
## SDK Reference (@elaraai/e3)
### e3.input(name, type, defaultValue?)
Define an input dataset at `.inputs.${name}`.
```typescript
const name = e3.input('name', StringType, 'default');
const count = e3.input('count', IntegerType);
```
### e3.task(name, inputs, fn, config?)
Define a task that runs an East function.
```typescript
const greet = e3.task(
'greet',
[name], // dependencies (inputs or other task outputs)
East.function([StringType], StringType, ($, n) =>
East.str`Hello, ${n}!`
)
);
// With custom runner
const pyTask = e3.task(
'py_task',
[input],
East.function([IntegerType], IntegerType, ($, x) => x.multiply(2n)),
{ runner: ['uv', 'run', 'east-py', 'run', '-p', 'east-py-std'] }
);
// Chain tasks via .output
const shout = e3.task(
'shout',
[greet.output],
East.function([StringType], StringType, ($, s) => s.toUpperCase())
);
```
### e3.customTask(name, inputs, outputType, command)
Define a task that runs a shell command.
```typescript
const process = e3.customTask(
'process',
[rawData],
StringType,
($, input_paths, output_path) =>
East.str`python script.py -i ${input_paths.get(0n)} -o ${output_path}`
);
```
### e3.package(name, version, ...items)
Bundle into a package. Dependencies are collected automatically.
```typescript
const pkg = e3.package('myapp', '1.0.0', finalTask);
```
### e3.export(pkg, zipPath)
Export package to a .zip file.
```typescript
await e3.export(pkg, '/tmp/myapp.zip');
```
## CLI Reference
### Repository Commands
```bash
e3 repo create <repo> # Create a new repository
e3 repo status <repo> # Show repository status
e3 repo remove <repo> # Remove a repository
e3 repo gc <repo> [--dry-run] # Garbage collect unreferenced objects
```
### Package Commands
```bash
e3 package import <repo> <zipPath> # Import from .zip
e3 package export <repo> <pkg> <zipPath> # Export to .zip
e3 package list <repo> # List packages
e3 package remove <repo> <pkg> # Remove package
```
### Workspace Commands
```bash
e3 workspace create <repo> <name> # Create workspace
e3 workspace deploy <repo> <ws> <pkg[@ver]> # Deploy package
e3 workspace export <repo> <ws> <zipPath> # Export workspace
e3 workspace import <repo> <ws> <zipPath> # Import package zip into workspace
e3 workspace list <repo> # List workspaces
e3 workspace status <repo> <ws> # Show workspace status
e3 workspace remove <repo> <ws> # Remove workspace
```
### Data Commands
```bash
e3 list <repo> [path] # List tree contents
e3 list <repo> <path> -r # List all dataset paths recursively
e3 list <repo> <path> -l # Immediate children with type/status/size
e3 list <repo> <path> -r -l # All datasets with type/status/size
e3 get <repo> <path> [-f east|json|beast2] # Get dataset value
e3 set <repo> <path> <file> [--type <spec>] # Set dataset from file
```
Path format: `workspace.path.to.dataset`
```bash
e3 get . dev.inputs.name
e3 get . dev.tasks.greet.output
e3 set . dev.inputs.name data.east
```
### Execution Commands
```bash
e3 start <repo> <ws> [--filter] [--concurrency <n>] [--force]
e3 run <repo> <pkg/task> [inputs...] -o <output>
e3 watch <repo> <ws> <source.ts> [--start] [--abort-on-change]
e3 logs <repo> <path> [--follow]
```
### Utility Commands
```bash
e3 convert [input] [--from <fmt>] [--to <fmt>] [-o <output>]
```
### Authentication (for remote servers)
```bash
e3 login <server> # Log in using OAuth2 Device Flow
e3 logout <server> # Log out and clear credentials
e3 auth status # List all saved credentials
e3 auth token <server> # Print access token (for curl/debugging)
e3 auth whoami [server] # Show current identity
```
### Remote URLs
All commands accept HTTP URLs instead of local paths:
```bash
# Start a server
e3-api-server --repos ./repos --port 3000
# Use remote repository
e3 repo create http://localhost:3000/repos/my-repo
e3 workspace list http://localhost:3000/repos/my-repo
e3 package import http://localhost:3000/repos/my-repo ./pkg.zip
```
## Development Workflow
### Watch Mode (recommended)
```bash
e3 watch . dev ./src/index.ts --start
```
Auto-compiles, deploys, and runs on file changes.
### Manual Workflow
```bash
npm run build && npm run main
e3 package import . /tmp/pkg.zip
e3 workspace deploy . dev [email protected]
e3 start . dev
```
## Packages
| Package | Description |
|---------|-------------|
| `@elaraai/e3` | SDK: e3.input, e3.task, e3.package, e3.export |
| `@elaraai/e3-types` | Shared type definitions |
| `@elaraai/e3-core` | Core library (workspaces, execution, caching) |
| `@elaraai/e3-cli` | CLI tool |
| `@elaraai/e3-api-client` | HTTP client for remote servers |
| `@elaraai/e3-api-server` | REST API server |
## Project Structure
```
my-project/
├── package.json
├── tsconfig.json
├── pyproject.toml # For Python runner
├── src/
│ └── index.ts # Package definition
└── repo/ # Repository (created by e3 repo create)
├── objects/ # Content-addressable object store
├── packages/ # Package metadata
└── workspaces/ # Workspace state
```
## Caching
Tasks are cached by content hash. Re-runs only when:
- Task's East function IR changes
- Input values change
Use `--force` to bypass: `e3 start . dev --force`
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.