spatialbridge

The protocol SCIMAP Pro (analysis) and Plexora (viewer, image processing) speak to share one dataset. Either application can hand work to the other, with or without an AI agent in between, and a third tool can join later without either package changing.

Neither application imports the other. Both depend on this package, which defines:

There is no daemon. The shared state is a directory: $SPATIAL_WORKSPACE_DIR if set, otherwise the platform user-data directory (.../nirmallab/spatialbridge/workspaces).

Development

The repository lives in a Dropbox-synced folder, and a virtual environment inside it gets corrupted. Keep the environment outside the folder:

export UV_PROJECT_ENVIRONMENT=$HOME/.venvs/spatialbridge
uv sync --all-groups
$UV_PROJECT_ENVIRONMENT/bin/python -m pytest

After changing a model in schema/, regenerate the committed JSON Schemas:

$UV_PROJECT_ENVIRONMENT/bin/python -m spatialbridge.schema export schema

A third tool joins by

1. depending on spatialbridge;
2. subclassing spatialbridge.adapter.Adapter (the capabilities with roles, plus invoke, bind, collect, on_event);
3. calling spatialbridge.tools.mount(server, adapter) on its MCP server;
4. passing pytest --peer "<its mcp command>" --pyargs spatialbridge.conformance.