JSPM

@loomfsm/loader

0.3.8
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 36
  • Score
    100M100P100Q88144F
  • License Apache-2.0

loom's build-time assembly layer — discovers and reconciles extensions, validates a bundle's declarative shape, and assembles the Registry the kernel ticks. Runs once at start-up, off the replay hot path; the kernel needs none of it to tick.

Package Exports

  • @loomfsm/loader
  • @loomfsm/loader/package.json

Readme

@loomfsm/loader

loom's build-time assembly layer. The loader discovers bundles, providers, and extensions, validates them against the kernel's plugin contracts, and assembles the registry the runtime boots from — so the kernel never performs dynamic discovery at tick time.

What's inside

  • Bundle loading — manifest validation with specific failure codes; a static import-scope check refuses bundles that reach past the plugin contract.
  • Extension reconciliation — fail-soft: a broken extension records a failed row with an audit entry instead of taking the runtime down.
  • Provider routing — builds the per-agent dispatch table from the config's model map.

Part of loom

loom drives multi-step LLM agent work — code review, implementation, any review-gated task — as a replay-deterministic state machine: safety invariants enforced at commit time, human gates where they matter, and a complete, replayable audit trail in a local SQLite file.

Most users should install @loomfsm/pipeline (npm i -g @loomfsm/pipeline), which pulls the whole runtime in one step. Install this package directly only if you are assembling your own runtime.

Website · Quickstart · Why loom · GitHub

License

Apache-2.0