Collibra reference agent

Collibra reference agent

What it does: First worked example agent — partner-facing repo demonstrating governance of an agent with read-write access to a Collibra catalog.

1. Vision context

This is the first concrete instance of the architecture. Demonstrates governance of an agent that adds tables, modifies columns, deletes assets — operations a customer's data steward would otherwise have to trust the agent to do unattended.

The repo is the partner artifact for the conversation in email-collibra.md (Spoor 1 — technical validation with Nick at Collibra). End-to-end runnable today via a mock Collibra MCP server. Real Collibra adapter is a follow-up once Nick confirms Collibra's MCP roadmap.

This component being a "concrete instance of the architecture" is the productive consequence of every other component: shipping a new governed agent is a reference repo, not a TapPass platform change.

2. Functional specification

Repo layout, mock MCP, demo script — all in architecture §15.1.

3. Technical design

LangChain ReAct agent with Collibra-specific task definitions. tappass-agent SDK is the only TapPass dependency. Mock Collibra MCP is a small WebSocket server in mock_collibra_mcp/.

4. Definition of done

• Repo created on GitHub.
• Demo runs end-to-end on a clean machine in <5 minutes from git clone.
• All 10 demo moments from architecture §15.1 fire correctly.
• Stijn / Nick demo completed (closing Spoor 1 of the partnership).

5. Coordination notes

With every architectural-spine component: we are the integration test for the whole stack. If something doesn't compose, this repo is where it shows.

With Compliance team: seed policies/ are seed only — operator overrides them by applying the live ones via tappass policy apply at demo time.

6. Out of scope

• Production-ready Collibra adapter (replaces the mock; follow-up).
• Subsequent agents (support emailer, code reviewer, refund processor) — separate repos when customer pull surfaces.