Trellis

Trellis is a uv workspace monorepo consolidating two sibling Egeria tools that were previously developed as separate repositories:

• Resource Explorer (resource-explorer) — discovers, surveys, and catalogs information resources (Git repositories, PostgreSQL databases, filesystems) using Egeria as the catalog of record.
• Egeria Advisor (egeria-advisor) — a RAG-based assistant providing conversational help for Egeria and pyegeria, including literate governance plan generation (LGCI) and report-spec authoring.

Both apps remain independently deployable services — the monorepo is a source-organization and dependency-resolution decision, not a runtime-topology one. They share one uv workspace lockfile so common code can be extracted and consumed with zero version skew, without forcing either app to be built, deployed, or run as part of the other.

Why one repo

Both apps talk to Egeria, both increasingly share infrastructure (pgvector, the same LLM backend, overlapping RAG corpora, perspective/question-driven routing), and — critically — there is a single maintainer across Resource Explorer, Egeria Advisor, Egeria Workspaces, and pyegeria. That combination made a shared workspace a much lower-friction way to keep common patterns (vector store access, intent classification, admin tooling, feedback capture) in sync than maintaining three near-duplicate implementations across separate repos.

Repository layout

trellis/
├── pyproject.toml            # workspace root — declares members, holds shared tooling config
├── uv.lock                   # single shared lockfile for the whole workspace
├── .python-version            # pinned Python version for the workspace
└── packages/
    ├── resource-explorer/     # Resource Explorer — own pyproject.toml, own tests, own CLI/web entry points
    └── egeria-advisor/        # Egeria Advisor — own pyproject.toml, own tests, own CLI/web entry points

Each package keeps its own config/configdata directory inside its own top-level package (resource_explorer/configdata/, advisor/configdata/) rather than as a sibling directory — this was a deliberate cleanup from each app's original repo layout, done when they were imported here, so neither app depends on Path(__file__) escapes reaching outside its own package boundary.

Getting started

git clone https://github.com/dwolfson/trellis.git
cd trellis
uv sync

uv sync resolves and installs dependencies for both workspace members into a single shared .venv at the repo root.

Configuration

Neither app's real config/secrets are committed (both are gitignored). Before running either app against a live Egeria instance or LLM backend, copy the example files and fill them in:

cp packages/resource-explorer/.env.example packages/resource-explorer/.env
cp packages/egeria-advisor/.env.example packages/egeria-advisor/.env
cp packages/egeria-advisor/advisor/configdata/mcp_servers.json.example \
   packages/egeria-advisor/advisor/configdata/mcp_servers.json

Running Resource Explorer

uv run --package resource-explorer resource-explorer --help
uv run --package resource-explorer resource-explorer web        # → http://localhost:8810

Running Egeria Advisor

uv run --package egeria-advisor egeria-advisor --help
uv run --package egeria-advisor egeria-advisor-web               # → http://localhost:8880

Running tests

uv run --package resource-explorer pytest packages/resource-explorer/tests
uv run --package egeria-advisor --extra dev pytest packages/egeria-advisor/tests

(Egeria Advisor's test config requires the dev extra for pytest-cov, which isn't installed by a plain uv sync.)

Notes for contributors

• Independent deployability is a hard constraint. Changes that couple Resource Explorer's and Egeria Advisor's runtime behavior together (as opposed to sharing a library both import) are out of scope for this workspace's design — see each package's own CLAUDE.md for its architecture.
• Shared code should live in its own workspace member, not be duplicated between the two apps. As common patterns get extracted (vector store access, intent/perspective classification, admin tooling, feedback capture), they belong in a new packages/<name>/ member both apps depend on via [tool.uv.sources], not copy-pasted.
• The workspace root's pyproject.toml carries one deliberate dependency override — numba>=0.60.0 — needed because resolving both members' dependencies together otherwise pulls an ancient numba/llvmlite (via beeai-framework[rag] → unstructured) that doesn't build on modern Python. See the comment there before removing it.