@elaraai/east-codex-plugin 1.0.100 → 1.0.101

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "east-codex-plugin",
3
- "version": "1.0.100",
3
+ "version": "1.0.101",
4
4
  "description": "East programming language ecosystem - a statically typed, expression-based language for business logic, data processing, UI definitions, and durable execution",
5
5
  "author": {
6
6
  "name": "Elara AI",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@elaraai/east-codex-plugin",
3
- "version": "1.0.100",
3
+ "version": "1.0.101",
4
4
  "description": "East programming language ecosystem - a statically typed, expression-based language for business logic, data processing, UI definitions, and durable execution",
5
5
  "license": "AGPL-3.0-or-later",
6
6
  "type": "module",
@@ -1,12 +1,8 @@
1
1
  ---
2
2
  name: e3
3
- description: "East Execution Engine (e3) - durable, content-addressed dataflow for East programs. Use when: (1) authoring a package with @elaraai/e3 (e3.input, e3.task, e3.streamTask with e3.output and e3.partition for bounded memory and work split over an input, e3.customTask, e3.function, e3.package, e3.export, East.importFunction), (2) records - audited state written only through mutations, declared whole in one e3.record(name, type, { initial, indexes, mutations, migrations }) call: mutation.reduce/edit/patch; index.on/key/keys, index.interval / index.area for reads by a time window or a 2D window, index.series / index.summary for a block of keys over a span of time tiles and their totals, and index.nested for what a record's rows nest — jobs, a value a day, child rows, trees — filed item by item, with totals and parents' subtotals; and migrated between versions (migration.value/rows/rekey, in order), (3) the e3 CLI (repo, package,… See the detailed scope below."
3
+ description: "East Execution Engine (e3): durable, content-addressed dataflow for East programs. Use when (1) authoring a package with @elaraai/e3 — e3.input, e3.task, e3.streamTask with e3.output and e3.partition (bounded memory, work split over an input), e3.customTask, e3.function, e3.package, e3.export, East.importFunction; (2) records — audited state written only through mutations (e3.record with mutation.reduce/edit/patch), their indexes (index.on/key/keys, interval, area, series, summary, nested) and migrations (migration.value/rows/rekey); (3) the e3 CLI — repo, package, workspace, dataset, task, dataflow run, run, call, mutate, seed, history, watch, convert, auth, and the cores and memory a run may use; (4) driving e3 from code (@elaraai/e3-api-client, @elaraai/e3-core, e3-api-server); (5) caching, reactive re-runs and garbage collection; (6) delegating task bodies to a rack (e3 rack); (7) e3 in a browser with @elaraai/e3-web. UI tasks are e3-ui's ui()."
4
4
  ---
5
5
 
6
- ## Detailed skill scope
7
-
8
- East Execution Engine (e3) - durable, content-addressed dataflow for East programs. Use when: (1) authoring a package with @elaraai/e3 (e3.input, e3.task, e3.streamTask with e3.output and e3.partition for bounded memory and work split over an input, e3.customTask, e3.function, e3.package, e3.export, East.importFunction), (2) records - audited state written only through mutations, declared whole in one e3.record(name, type, { initial, indexes, mutations, migrations }) call: mutation.reduce/edit/patch; index.on/key/keys, index.interval / index.area for reads by a time window or a 2D window, index.series / index.summary for a block of keys over a span of time tiles and their totals, and index.nested for what a record's rows nest — jobs, a value a day, child rows, trees — filed item by item, with totals and parents' subtotals; and migrated between versions (migration.value/rows/rekey, in order), (3) the e3 CLI (repo, package, workspace, dataset, task, dataflow run, run, call, mutate, seed, history, reindex, compact, watch, convert, auth) and the cores and memory a run may use (-j, --memory), (4) driving e3 from code: @elaraai/e3-api-client against a server, @elaraai/e3-core on a local repository, e3-api-server, (5) caching, reactive re-runs and garbage collection, (6) delegating local task bodies to a rack: e3 rack enroll/policy, dataflow run --rack, watch --start --rack, optional e3-api-server --rack, (7) e3 in a browser, no server: @elaraai/e3-web (serveUnits, serveE3, createWebE3) and what a browser cannot do. UI tasks are e3-ui's ui().
9
-
10
6
  # East Execution Engine (e3)
11
7
 
12
8
  e3 runs East programs as a durable dataflow over content-addressed data: every
@@ -295,8 +291,13 @@ Wrap a stream task's input in `e3.partition` and the body runs once per
295
291
  **piece** of it: each piece is a unit of its own — cached on its own, run in
296
292
  parallel under the budget — typed as the whole dataset (a key range of a Set or
297
293
  Dict, a position range of an Array), and the pieces' outputs combine as the
298
- output kind says. Pieces are cut by content, most holding 64 to 100 MiB of
299
- stored bytes, so an append or an insertion re-runs only the pieces it reaches.
294
+ output kind says. Pieces are cut by content, at sizes that follow what the
295
+ input weighs — one piece within 16 MiB, tens of pieces for mid-size data, and
296
+ most holding 64 to 100 MiB from 2 GiB — so an append or an insertion re-runs
297
+ only the pieces it reaches. Under the local budget's guard (Linux, macOS) a
298
+ stage starts all its units at once, each reserving the task's last peak, or the
299
+ first time what the largest piece holds of its rows decoded, as its program
300
+ reads them.
300
301
  An input not wrapped reaches every piece whole, opened lazily as every input is
301
302
  (a keyed get reads only its segments); a change to it re-runs every piece.
302
303
 
@@ -52,9 +52,12 @@ task or a unit each — and `--memory <size>` (`8G`, `512M`) what they may reser
52
52
  between them. The defaults are `E3_JOBS` and `E3_MEMORY`, else what e3 may use:
53
53
  its CPU affinity capped by a cgroup quota, and the cgroup's `memory.max` or
54
54
  physical memory, less a reserve. A unit of a split task reserves the largest
55
- peak a unit of its stage has reached in the run, so a stage runs its first unit
56
- alone and then fans out; on Linux and macOS a guard stops the newest unit when
57
- the runners together pass the budget, and runs it again once it fits. A deploy
55
+ peak a unit of its stage has reached in the run. On Linux and macOS a guard
56
+ stops the newest unit when the runners together pass the budget, and runs it
57
+ again once it fits, so there a stage starts all its units at once, each
58
+ reserving the task's last peak or, the first time, what the largest piece
59
+ holds of its rows decoded, as its program reads them; on Windows a stage runs
60
+ its first unit alone and then fans out. A deploy
58
61
  takes its `file` sources in `-j` at a time, their pieces' intake units running
59
62
  under the same budget. A source deploy, or a `watch`, exports the workspace
60
63
  packages its imported functions come from `-j` at a time, a process each, on