First-party grid asset packs for the_grid — each pack exports domain components + CLI components (the CLI-SDK model):
| Pack | Domain |
|---|---|
packages/grid_assets |
the code asset (agent/verify/land + the code circuit + the git SourceControl) and the compute asset (bounded dispatch over a federation lease) |
packages/dart_grid_assets |
the DART domain (the typed grid.dart envelope + pub dev-time linkage + the exported DartCommand) |
packages/federated_grid_assets |
the federation surface (station server + cross-station asset leasing) |
packages/zero_conf_grid_assets |
zero-conf station discovery (mDNS advertisement/browse) |
packages/analytical_grid_assets |
the ANALYTICAL domain (station health and effectiveness REPORTING over the session-ledger metrics projection: split token distributions + the exported MetricsCommand) |
The butane burn asset (butane_grid_assets) moved to its system's repo —
butane_flutter/packages/butane_grid_assets (grid assets live with their
system; the ADR-0011 placement split).
Extracted from the_grid@17ea50a90d39791e8bad7a16c28a93711b44abf2 at the repo split.
The the_grid framework packages are declared any and resolved via a
machine-local pubspec_overrides.yaml at this root (gitignored) — path deps
into the sibling ../the_grid checkout during dev, hosted/git refs at
stabilization. The dart domain's grid dart link generates it; see
the_grid docs/DESIGN-pub-capability-and-repo-split.md. genesis_tree
stays hosted (^0.1.3).
dart pub get # workspace root (needs the sibling checkout + overrides)
dart run melos run test
dart run melos run analyzeOne command releases the whole workspace: it computes which packages are not on
pub.dev yet, runs every gate, validates the consumers a direct stable wave owes,
then cuts and pushes one <package>-v<version> tag per package in dependency
order — and the tag-triggered publish workflow does the upload.
A release moves on two independent axes: --change is the semver move
(docs/additive/fix/breaking) and --rung is the prerelease rung
(stable/dev/beta/rc), which belongs to each PACKAGE rather than to the
wave — omit it and each package's rung is read off its authored version, so a
mixed dev/beta wave is fine.
dart run melos run release -- --change fix --consumers <manifest.json>
dart run melos run release -- --change fix --consumers <manifest.json> --dry-run
dart run melos run release -- --change breaking --rung dev
dart run melos run release -- --change breaking --rung beta
dart run melos run release -- --change breaking --rung rc --promotion-intentBreaking work enters the ladder at dev and walks to beta unattended;
only a human sets rc, which is why that rung needs --promotion-intent
(--change rc --promotion-intent is the compatibility spelling of the last
line). A stable release still passes every consumer first.
See packages/dart_grid_assets/README.md for the wave's stages, the consumers
manifest shape, and why a breaking STABLE release is refused here.
power_station is one repo of the
memento-engineering org, and its docs
reference siblings by name: the_grid
(the engine these asset packs plug into),
lenny (the debugging harness),
space_station (the org's grid instance — public release to follow), and
houston (not a repo: the id prefix of the station's state store). Gas City
(gc) is the predecessor system the_grid reimplements — not ours; see the
original project at docs.gascityhall.com.
MIT — see LICENSE.