Package Exports
- @femtomc/mu-orchestrator
Readme
@femtomc/mu-orchestrator
Long-running execution engine for mu work plans. It dispatches ready work and records outcomes.
Install
After publishing:
npm install @femtomc/mu-orchestrator
# or: bun add @femtomc/mu-orchestratorFrom this repo:
cd mu
bun install
bun run buildUsage
import { FsJsonlStore, fsEventLog, getStorePaths } from "@femtomc/mu-core/node";
import { ForumStore } from "@femtomc/mu-forum";
import { IssueStore } from "@femtomc/mu-issue";
import { DagRunner } from "@femtomc/mu-orchestrator";
const repoRoot = process.cwd();
const paths = getStorePaths(repoRoot);
const events = fsEventLog(paths.eventsPath);
const issues = new IssueStore(new FsJsonlStore(paths.issuesPath), { events });
const forum = new ForumStore(new FsJsonlStore(paths.forumPath), { events });
const runner = new DagRunner(issues, forum, repoRoot);
const result = await runner.run("mu-<root-id>");
console.log(result);Tests / Typecheck
From the mu/ repo root:
bun test packages/orchestrator
bun run typecheckRuntime
- Node-only (uses filesystem + pi SDK in-process).
- Default backend is
PiSdkBackend(from@femtomc/mu-agent). Pass a customBackendRunnerto override.