Corey's Logos Modules

Personal Logos Basecamp module catalog by @corpetty — browse it at modules.bayesianpersuasion.com.

Install in Basecamp

Basecamp → Package Manager → Add repository:

https://modules.bayesianpersuasion.com/logos-repo.json

Then install any module below with one click — Basecamp resolves versions and dependencies for you.

Modules

Module	Package	Source	Description
Workflow Registry	workflow_registry	logos-workflow-registry	Discovers installed Logos modules and turns their method signatures into workflow node types.
Workflow Engine	workflow_engine	logos-workflow-engine	DAG-based execution engine — control flow, transforms, error recovery. Needs workflow_registry.
Workflow Scheduler	workflow_scheduler	logos-workflow-scheduler	Deployment, cron/interval scheduling, webhook triggers, execution history. Needs workflow_engine.
Workflow Canvas	workflow_canvas	logos-workflow-canvas	Visual editor — drag, drop and wire module operations into pipelines. Needs workflow_registry + workflow_engine + workflow_scheduler.
Logos MCP	logos_mcp	logos_mcp	Logos-to-MCP bridge: exposes Logos module methods as MCP tools for AI tooling.
Muster	muster_module (core), muster_ui	muster	Local-first client for coordinating multi-party transactions inside conversations.
Netgraph	netgraph_module	netgraph-module	Live observer of every network connection the Logos process tree holds, grouped by service and network. Local only, off until turned on.

The four workflow modules install as a set: registry → engine → scheduler, with canvas as the UI on top. To build and test all four inside a local basecamp checkout, see docs/basecamp-workflow-suite-runbook.md.

Muster depends on delivery_module, which this catalog does not publish — add a repository that carries it (or install it first) or Basecamp's dependency resolution will fail.

How it works

Built on logos-co/logos-modules-release-base: GitHub Actions build each module's .lgx from its Nix flake (.#lgx-portable), sign it (Ed25519 — the public DID is in logos-repo.json under trustedSigners), publish it as a <module>-v<version> release, and roll everything into the index release that clients read.

Each module is a git submodule under submodules/; its metadata.json is the source of truth for name and version. Add one with scripts/add-module.sh, which registers the submodule and generates the matching Release <module> workflow. The pipeline builds one module per metadata.json directory, so a repo holding several works too — muster is wired that way (submodules/muster/module and submodules/muster/ui, released by release-muster-core.yml and release-muster-ui.yml). release-all.yml discovers those subdirectories on its own.

Externally published modules

A module released from a repo whose build this catalog can't run has to publish its own signed .lgx (with the same key, so trustedSigners still matches); the catalog then folds those release assets into the index by URL. Sources go in external-modules.txt, and the Augment index workflow runs after every Rebuild index to add them on top. That file is currently empty — everything here is built in this repo.

Releasing

Cut a release from the Actions tab (Release …) or with scripts/catalog.sh:

./scripts/catalog.sh release logos-workflow-registry --watch
./scripts/catalog.sh release-all --watch
./scripts/catalog.sh rebuild-index

A new release happens when you bump a submodule pointer (and thereby its metadata.json#version) and re-run its workflow. The site at modules.bayesianpersuasion.com is regenerated by CI from the index after every release.

Signing

Releases are signed inline in CI with the LOGOS_SIGNING_KEY Actions secret (an Ed25519 JWK); the matching public DID is the one listed in logos-repo.json. The mode is configured in one place — _release-module.yml — for both the per-module and the umbrella workflows.

Working copy

After cloning, materialise the submodules:

git submodule update --init --recursive